Automations overview
A proposal gets accepted and a project kicks off with tasks, an invoice, and a client invitation, all without a single manual step. Automations build these workflows visually, connecting a trigger (the event that starts things), optional conditions (filters that decide whether to continue), and actions (what happens next) into chains that run the moment something happens in your workspace.
The visual builder
Each automation appears as a connected chain of nodes in the visual builder. The flow starts with a trigger node, passes through optional condition nodes, and ends with one or more action nodes. Nodes connect by dragging, so building a workflow reads like a flowchart rather than a script. The entire process runs without code.
What automations connect
Automations tie events to consequences across your entire workspace. A form submission creates a contact and assigns a task to a project. An overdue invoice sends a reminder email and flags a follow-up. A project status change notifies your team. A booking confirmation sends an email, generates a calendar event, and links everything back to the project. Because triggers, conditions, and actions span tasks, projects, invoices, proposals, contracts, forms, contacts, and bookings, a single automation can reach across features that would otherwise need manual coordination.
Real-time execution
Automations fire the moment their trigger event occurs. A proposal gets signed overnight, and the project, invoice, and client invitation are already waiting the next morning. Each execution follows the chain top to bottom, evaluating conditions and running actions in sequence. Because automations react in real time, the gap between an event and its consequences closes instantly, without anyone needing to be online.
