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 → invoice, task, and email. When a proposal status changes to "Accepted", the automation creates an invoice from the proposal data, generates a task to begin the engagement, and sends a welcome email to the client. The full sequence runs 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.
Contract created → notification and follow-up. When a contract is created, the automation sends a notification to the team and creates a follow-up task to ensure the signing process stays on track.
Project and task workflows
Task completed → notify team. When a task status changes to "Complete", a notification reaches the relevant team members. Task completions trigger communication automatically so nobody needs to send manual updates.
Task approaching deadline → reminder. When Task date is due (using the date is due trigger), the automation sends a reminder notification to the assignee and a follow-up email to the project owner to keep deadlines on track.
Invoice due date approaching → early reminder. When Invoice date is due, a reminder email goes to the client, prompting early payment before the invoice becomes overdue.
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.
Recurring invoice upcoming → client notification. When Subscription date is due, the automation sends a heads-up email to the client so they can prepare for the charge. 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.
