Guide · Workflows
Make automation visible and assignable.
A workflow is useful only when its trigger, inputs, owner, outputs, failure path and approval boundary are explicit.
Workflow contract
Every production workflow should define an owner, the event or schedule that starts it, a versioned input shape, the expected artifacts or records, a timeout, a failure destination and whether approval is required before any external action.
Create an n8n workflow
01
Choose the trigger
Use a webhook for an Ekvaar-requested run, a schedule for recurring work, or an app event for a connected-provider event.
02
Validate the request
Reject missing organisation, actor, task and instruction fields before calling a model or third-party service.
03
Map model nodes
Keep model credentials inside their model nodes. Use explicit primary and fallback paths, and return the selected provider and model in the trace.
04
Create artifacts
Write generated text, media or reports to durable storage and return stable artifact references—not temporary UI-only values.
05
Create approval when required
For publishing, payments or other sensitive actions, stop with a reviewable approval item that contains the final artifact and frozen action details.
06
Return structured output
Respond with JSON containing status, run ID, task ID, artifact references, blocked reason and next action.
Assign a workflow to an agent
In the agent workspace, choose the workflow and define whether the agent may trigger it manually, on a schedule or from an event. Grant only the integrations the workflow needs. The assigned agent remains accountable for the run even when n8n performs the steps.
Automation is not permission
A scheduled run does not bypass an approval policy. The publishing or mutation node should receive an approval-bound execution payload, not merely a boolean from the agent.