What n8n does
A workflow starts with a trigger, runs a set of steps, and ends with an action. A trigger can be a webhook, a schedule, a new row in a sheet or a new email. Steps can call any API, transform data, branch on a rule or wait for a person to approve.
Each run is logged, so you can see what came in, what each step did and where a run failed.
Good first workflows
- An order email that updates stock and the order sheet, then confirms to the customer.
- A web form that creates a CRM record and notifies the right person on the team.
- A monitoring alert that opens a tracked incident instead of another email.
- A daily report that pulls numbers from two systems into one message.
When n8n is the right tool
Use n8n when the work is a sequence of steps across tools you already own and the rules can be written down. It is quick to change, and people who are not developers can read the workflow.
Write custom code instead when the logic is large, needs its own data model, or has to answer in milliseconds. OQVIAN often uses both: a small service holds the state and n8n handles the connections around it.
A real example
For Jackson Electric Cooperative, OQVIAN built network alert automation with five n8n workflows and a small incident service. One alert opens one incident, repeat alerts join it, and the recovery closes it. It was tested in a lab with LibreNMS and a virtual MikroTik router, and 23 behaviour tests pass.
Have a process in mind?
Tell us the trigger, the tools and who needs to approve. We will say whether n8n fits.