People call me to set up a flow. Email to CRM. Document to a record. A report that is no longer copied by hand.
n8n or Make for the graph. Python or Node when the logic does not fit on the canvas.
Usual stack
- n8n — Flows with control of the environment.
- Make — If the team already lives there.
- Python / Node — When low-code is not enough.
- APIs / webhooks — To connect what has no connector.
What gets set up
- Invoices and documents: extract, validate, create. A human reviews if a field does not fit.
- Sign-up: from the form to accounts and environment, without copying fields between tools.
- Email and CRM: what it may read, what it may write, a log of each step. Note: n8n sobre correo o CRM.
FAQ
What can you automate?
Email, CRM, reports, documents, hand-offs between tools. Any copy-paste that repeats every week.
n8n, Make or code?
n8n and Make for the flow. Python or Node when the logic does not fit on the canvas.
How do you avoid a fragile flow?
Logs, retries, alerts. And a human who reviews when the flow writes or sends.
If the job is a flow, email david@davidtovar.dev.