Automations
When/If/Then rules that react to deal events: the five triggers, the step types, who can create and manage a rule, and how run history works.
Updated 2026-07-21
An automation is a When/If/Then rule: When a deal event happens, If its conditions match, Then run a list of steps in order. Automations live at /automations and react to deals — there is no workspace-level toggle, every workspace has the feature.
Triggers
- Deal created
- Deal stage changed
- Deal status changed (open/won/lost)
- Deal field changed — pick a specific field (built-in or custom) to watch
- Before stage change — a synchronous gate that runs while the move is happening, not after; it uses a different pair of step types (see the callout below) and is documented separately
Steps
A rule runs its steps in order once its conditions match. Available step types:
| Step | What it does |
|---|---|
| Send notification | In-app notification to the deal owner or specific members. |
| Post to a channel | Sends a message to a connected Slack or Discord channel or DM, with @-mentions for the deal owner, deal team, contacts, linked client, or a specific member/role. |
| Send email | Sends an email template to the deal contacts, the linked client, or the deal owner. |
| Create task | Creates a next action on the deal, due a set number of days out. |
| Update deal | Changes the deal’s stage, status, owner, or a field. |
| Add note | Logs a note on the deal timeline. |
| Wait | Pauses the rule for up to 30 days before continuing. |
| If / else branch | Splits into two step lists based on a condition. |
The Before stage change trigger offers a different pair of steps — Automatic check and Manual confirmation — used to gate a move rather than react to it. Every other trigger uses the eight steps above.
Who can create and manage automations
Any workspace member can create an automation and see every automation in the workspace — membership alone is the gate for creating and viewing. Editing or deleting a specific automation is restricted to its creator or a workspace owner/admin.
Run history
Every automation keeps a history of its runs, one per matching deal event. Any member can see the run list — status, which deal it ran against, and when. A run for a deal you can’t otherwise see (per your deal visibility) never appears at all.
Step-by-step input and output — the rendered message text, the field values a step wrote — is only visible to the automation’s creator or a workspace owner/admin. Everyone else sees the run’s steps and status, with the payloads hidden.
Test runs
Before publishing, use Test to pick a real deal and dry-run the automation against it: you see whether the conditions matched and what each step would have sent or written, with no external messages sent and no changes saved. Once an automation is published, a second explicit step lets you run it for real against that deal, which goes through the same pipeline as a live trigger and shows up in run history.
Spotted something out of date? Email hello@neokivo.com.