Automation recipes and examples
Common automation patterns cover client onboarding, project management, financial follow-ups, and team communication. Each recipe below outlines the trigger, the resulting actions, and what the workflow achieves.
Client onboarding workflows
Proposal accepted → project, invoice, and client invitation. When a proposal status changes to "Accepted", the automation creates a project from the proposal data, generates an invoice from the service table pricing, and invites the client to your workspace. The full onboarding sequence fires from a single client signature.
Form submitted → contact, task, and email. When a specific form gets submitted, the automation creates a contact from the form fields (name, email, company), generates a task with the form details mapped to the description, and sends a confirmation email to the submitter. New leads enter your CRM with a follow-up task assigned automatically.
New booking → confirmation and project link. When a booking gets created, a confirmation email sends to the client, a calendar event generates, and the booking details link to the associated project.
Project and task workflows
Task completed → notify and update project. When a task status changes to "Complete", a notification reaches the project owner, and the project status updates if all tasks are finished. Task completions cascade upward so project health stays current.
Project status changed → team notification. When a project status changes, all project members receive a notification. Status updates propagate to the team without anyone sending manual messages.
Time entry logged → budget check. When a time entry gets created, a condition checks whether total logged hours exceed the project budget. When the threshold is crossed, the project owner receives a notification.
Financial and communication workflows
Invoice overdue → reminder and follow-up. When an invoice status changes to "Overdue", a reminder email goes to the client with the invoice amount and due date, and a follow-up task gets assigned to the account manager.
Contact created → group assignment. When a new contact enters your CRM, the automation adds the contact to a specific group for segmentation. Each recipe serves as a starting point that can be extended with additional conditions and actions, so the workflow adapts to your specific process rather than locking the automation to a fixed sequence.
