Automations

An automation is a small workflow: one trigger, then any chain of conditions, waits, and actions. Build it visually, test it on a real record, then switch it on.

Triggers

• Record events: deal created, updated, stage changed, won, lost, value or assignee changed; contact or company created or updated; tag added or removed; comment added.
• Project and task events: task created, updated, status changed, completed, reopened, assignees changed, moved, or linked to a record; project created, status changed, completed, archived; comment added to either.
• Docs: a deal, contact, company, project, or task gets @-mentioned in a doc page. Mentions in restricted docs stay private and never fire automations.
• Time-based (checked daily): deal gone stale for N days, close date approaching, close date passed, task due soon, task overdue.
• Integrations: Telegram message received (with an optional cooldown so a busy chat fires once), campaign reply, campaign finished, meeting scheduled.

Attach filters to the trigger so it only fires when it should, for example “stage changed from Negotiation” or “value above 5,000”. Filters can use custom fields too.

On Telegram message triggers, the AI can classify the intent (buying signal, pricing question, complaint, churn risk…) and sentiment of the message, and you can filter on both. Classification uses AI credits.

Conditions, waits, and branching

• Condition nodes check the record’s live state, with AND/OR groups, and branch into true and false paths.
• Wait nodes pause the run for minutes, hours, or days, up to 90 days.

So “deal moved to Proposal → wait 3 days → still in Proposal? → nudge the assignee” is four nodes.

Actions

• Send a Telegram message: to a teammate through the Cavyro bot, or to the contact in their existing conversation.
• Send an email or an in-app notification to teammates, deal assignees, admins, or the contact.
• Send a webhook: generic JSON for your own backend or Zapier/Make/n8n, or preformatted for Slack and Discord.
• Change the record: move a deal to a stage, mark won or lost, update a field, add or remove a tag, add a comment.
• Create a deal from a scheduled meeting, linked to the meeting’s contacts.
• Create a task or a whole project, so a won deal can open its own delivery board.
• Change a task: complete it, reopen it, assign it, or set its workflow status.
• Set a project’s status: active, on hold, completed, or archived.
• Create a doc from a template: copy a template doc, with its whole page tree, into a new doc. Mark any doc as a template first, then pick it in the action.

Messages support {{variables}} like {{deal.title}}, {{contact.first_name}}, and {{deal.url}}, which links back into Cavyro. Project and task triggers add {{project.name}}, {{task.title}}, and their URLs. Doc mention triggers add {{doc.title}}, {{page.title}}, and {{page.url}}.

Recipes

Combinations our own team runs. Each is one trigger and one or two actions, so they take a minute to build.

• Won deal, instant onboarding doc. Deal won → create a doc from your “Onboarding” template, titled Onboarding: {{deal.title}}. Every closed deal starts with the same checklist, filled with the deal’s name.
• Meeting notes that write themselves. Meeting scheduled → create a deal linked to the attendees, then create a doc from your “Meeting notes” template. You walk into the call with the prep page already in the sidebar.
• Know when your deal comes up in writing. Deal mentioned in a doc → notify the deal’s assignees with {{page.title}} and {{page.url}}. Strategy pages stop being a place where decisions hide from the people they affect.
• Buying signals straight to you. Telegram message received, filtered to intent “buying signal” → notify the assignees and add a comment on the contact. The AI reads the chat so you don’t have to.
• Won deal, delivery board ready. Deal won → create a project named after the deal, linked to it and to the company. The handover from sales to delivery stops being a copy-paste job.
• Overdue work nobody owns. Task overdue → notify the assignees, and comment on the task so the trail stays on the record.
• No deal left to rot. Deal stale for 14 days → send the assignee a Telegram nudge with {{deal.url}}. Pair it with “close date passed → move to a Review stage” and your pipeline cleans itself.

Trigger reference

Trigger	Record	Kind
Deal created / updated / stage changed / won / lost	Deal	Event
Deal value changed / assignee changed	Deal	Event
Tag added / removed on a deal	Deal	Event
Comment added to a deal	Deal	Event
Deal mentioned in a doc	Deal	Event
Deal gone stale	Deal	Time-based
Close date approaching / passed	Deal	Time-based
Contact created / updated	Contact	Event
Tag added / removed on a contact	Contact	Event
Comment added to a contact	Contact	Event
Contact mentioned in a doc	Contact	Event
Company created / updated	Company	Event
Tag added / removed on a company	Company	Event
Comment added to a company	Company	Event
Company mentioned in a doc	Company	Event
Task created / updated / status changed	Task	Event
Task completed / reopened	Task	Event
Task assignees changed / moved / linked to a record	Task	Event
Comment added to a task	Task	Event
Task mentioned in a doc	Task	Event
Task due soon / overdue	Task	Time-based
Project created / status changed	Project	Event
Project completed / archived	Project	Event
Comment added to a project	Project	Event
Telegram message received	Contact	Integration
Campaign reply received	Contact	Integration
Campaign finished sending	Campaign	Integration
Meeting scheduled	Meeting	Integration

Action reference

Action	Works with
Send an email	All records
Send a Telegram message	All records
Send an in-app notification	All records
Send a webhook	All records
Move a deal to a stage	Deals
Mark a deal won / lost	Deals
Update a field	Deals, contacts, companies, projects, tasks
Add / remove a tag	Deals, contacts, companies, projects, tasks
Add a comment	Deals, contacts, companies, projects, tasks
Create a deal	Meetings
Create a task	All records
Create a project	All records
Complete / reopen a task	Tasks
Assign a task	Tasks
Set a task’s status	Tasks
Set a project’s status	Projects
Create a doc from a template	Deals, contacts, companies, meetings

Testing and publishing

• Test run: pick a real record and watch the full step log. Conditions evaluate for real, waits resolve instantly, and actions only preview what they would do. Nothing is sent or changed, and tests never count toward your quota.
• Saving is publishing: every edit creates a new version. Runs that are already in flight finish on the version they started with.
• Disabling is a kill switch: it also halts waiting runs, immediately.

Run history

Every run keeps a step-by-step log for 90 days: what fired, what each condition compared, what was sent, and why something failed or was skipped. Transient network errors retry automatically. When your monthly quota runs out, runs are recorded as skipped with the reason shown, so nothing disappears silently.

Limits and permissions

• Monthly runs: 1,000 per seat on Pro and 3,000 per seat on Business, pooled across the workspace, and unlimited on Enterprise. Resets on the 1st. One-time run packs (500 to 10,000) top up the current month on any paid plan.
• You can create unlimited automations; only runs are metered.
• Everyone can view automations and history; admins create, edit, and enable them.
• Changes an automation makes are labeled as the automation in the activity feed, not as a person.