Workflows
Workflows automate repetitive work directly inside Coco CRM. A workflow is a trigger plus a sequence of steps — no external automation tool required. Build them from the Workflows entry in the sidebar.
Triggers
Every workflow starts with exactly one trigger:
| Trigger | Fires when |
|---|---|
| Record created | A record of a chosen object is created |
| Record updated | A record changes (optionally only specific fields) |
| Record deleted | A record is deleted |
| Manual | A member runs it from a record's action menu or a view |
| Cron / schedule | On a recurring schedule (e.g. every Monday 9:00) |
| Webhook | An external system calls the workflow's URL |
Record triggers pass the record into the workflow, so later steps can read and reference its fields.
Actions
Chain any number of steps after the trigger:
| Action | What it does |
|---|---|
| Create record | Create a record of any object, with fields filled from trigger data |
| Update record | Modify the triggering record or a related one |
| Delete record | Remove a record |
| Send email | Send an email from a connected account |
| Code step | Run a custom TypeScript function for logic the built-ins don't cover |
| HTTP request | Call an external API (Slack, internal services, etc.) |
| AI agent step | Let the AI read context and produce output for later steps |
Steps can use variables from the trigger and from previous steps — e.g. put the deal's name into the task title.
Branches and iterators
- Branch (if/else) — split the flow on a condition, e.g. if Amount > 50,000 take the high-touch path, otherwise the standard one.
- Iterator (loop) — run a group of steps once per item in a list, e.g. create a task for each person related to a company.
Versions and runs
Workflows are versioned:
- Editing creates a draft version; the previously activated version keeps running until you click Activate.
- Past versions are kept, so you can inspect or revert to what was live last month.
- Deactivate stops the trigger without deleting anything.
Every execution is recorded in the workflow's Runs tab: trigger payload, each step's input and output, timing, and success/failure. Failed runs show the exact step and error — the first place to look when an automation misbehaves.
Example: Closed Won → onboarding task
- Create a workflow with trigger Record updated on Deal, watching the Stage field.
- Add a Branch: continue only if Stage is Closed Won.
- Add a Create record step: object Task, title
Kick off onboarding for {{deal.name}}, assignee = deal owner, due date +2 days, linked to the deal. - Optionally add a Send email step to notify the delivery team.
- Click Activate.
From then on, dragging a deal into the Closed Won column of the Deals by Stage board creates the onboarding task automatically.
Permissions
Creating and editing workflows requires a role with workflow access; runs execute with workspace-level data access. See Members and Roles.