Conditional branching logic
Workflows branch on any data point — paid vs unpaid, signed vs unsigned, project stage, client tag. No more linear-only automations.
Build automated workflows with branching logic, approval gates, and scheduled sends. Follow up on proposals, chase overdue invoices, onboard new clients — all without lifting a finger.
Workflow Automation
Workflows branch on any data point — paid vs unpaid, signed vs unsigned, project stage, client tag. No more linear-only automations.
Pause a workflow for team approval before it escalates an invoice reminder, sends a sensitive email, or triggers a legal action.
Fire workflows on a schedule, on record changes, before a date, or on client actions like proposal approved or payment failed.
Multi-step messaging with merge fields and timing control. Onboarding, follow-up, re-engagement — all automated.
Send the same workflow to multiple people at once — co-approvers, team members, or a whole client list. No workarounds required.
Start from proven workflows — collections cadence, proposal follow-up, onboarding sequence — and customize per workspace.
Docs
Compare
Use cases
Common automations include collections sequences for overdue invoices, proposal follow-up cadences, onboarding sequences for new clients, appointment reminders, and payment-failure escalations. Any record event or schedule can trigger a workflow.
Yes. Workflows branch on any data point — paid vs unpaid, signed vs unsigned, project stage, client tag. Linear automations are a subset of what Ratio supports.
Yes. Pause a workflow for team approval before it escalates, sends a sensitive email, or takes a consequential action. Approvals route to specific team members by role.
Dubsado workflows are linear — one action after another, no conditionals, no multi-recipient support. Ratio workflows support branching, approval gates, multi-recipient sends, and record-event triggers.
Yes. Start from proven templates — collections cadence, proposal follow-up, client onboarding — and customize for your workspace. Templates are a starting point, not a rigid framework.