Workflows for recurring processes
When an email arrives from a new contact: create the contact, open a deal, notify the team. Visual workflows handle the routine — every step visible.
When
Email arrives from a new sender
Then
Create contact in CRM
Then
Open deal in pipeline
Then
Notify the team
Why workflows?
Less manual repetition — for processes that already repeat.
Visual builder
Build workflows with drag & drop — clear and versionable.
Practical triggers
React to CRM events, email signals and workspace events.
Workspace actions
Notify, update, kick off emails — for recurring processes.
Workflows for recurring processes
Automate routine — not everything. Triggers from CRM, email and workspace events, without middleware.
- CRM: deal stage, field change, new contact
- Email: opens and related signals
- Workspace: tasks and notifications
Actions that ease the day
A workflow can create and update records, trigger emails or notify the team. For example: deal won → create onboarding project → send welcome email.
- Conditional steps where useful
- Traceable execution
- Templates as a starting point
Templates to start
Begin with simple templates for follow-ups and team alerts.
Workflow · Deal won
When
Deal stage changes to “Won”
Then
Create onboarding project
Then
Send welcome email
Then
Task for customer success
Workflows in the ecosystem
Workflows connect modules for recurring processes — CRM, email and notifications, without overselling.
FAQs about Workflows
No. Workflows are built in the visual builder via drag & drop — if-then logic instead of code.
CRM events like deal stage changes or new contacts, email signals like opens, and workspace events like due tasks.
Starter includes 5,000, Pro includes 15,000 automations per month. More is available flexibly as an add-on.
Yes. Every run is fully documented — you can see which step ran and when.