Skip to main content
ECN includes a graph-based automation engine (n8n-style) for reacting to events in your workspace: a contact is created, a deal changes stage, a form is submitted, an owner claims a listing, and more.

​
Model

ConceptWhat it is
WorkflowAn editable graph (DRAFT) that you publish to a frozen, executable version (LIVE).
TriggerWhat starts a workflow — e.g. contact.created, deal.stage_changed, form.submitted, tag.added, schedule.daily.
StepA node: action (send_email, create_task, webhook_post, add_tag…), wait, branch, or merge.
EnrollmentA per-contact run. It pins the published graph at enroll time, so later edits don’t change in-flight runs.
Step runThe execution log for each step of an enrollment.

​
Lifecycle

​
Approval-gated sends

Like the rest of ECN, any step that sends outbound (email, post) respects the approval model — AI-drafted content is seeded and a human approves before it goes out. See Security.

​
API

Workflows are managed under /api/v1/automation/ — list/create workflows, inspect a workflow’s graph, publish, test, and view enrollments and step runs. See the API reference.
Re-synced to the live system each docs iteration. The available trigger and action types track the backend automation app.