You are paying Zapier to move data between tools you would rather not own.

Multi-step workflows with waits and branching, triggered by what actually happens in your business.

• Triggers: contact created, tag added, deal stage changed, form submitted, message received, call completed, on a schedule, or manually / by webhook
• Steps: send SMS or email, add or remove tags, add to a list, move a pipeline stage, create a task, wait, call a webhook, notify your team
• Voice steps: ringless voicemail, outbound IVR, sales bridge, AI call, enroll in a campaign
• Full run history so you can see what fired and why

Actions are defined in one registry with their fields and the surfaces they're allowed on. Workflows, call dispositions, and bulk actions all render from it.

• Same action, same options, whether you're in a workflow or a bulk selection
• Pickers for numbers, IVR menus, campaigns, sales bridges, AI agents, lists, and stages
• Registry-driven, so the menus can't drift out of sync

Visual flows branch on contact and event data, park safely through timed waits, and retain the node-by-node execution history for every enrolled contact.

• Condition branches and explicit success paths
• Durable waits that resume on a later dispatcher tick
• Manual, bulk, event, schedule, and API enrollment
• Run detail shows what fired, what changed, and what failed

Trigger a workflow from a signed public URL or call an outside API from inside a flow with configurable method, authentication, headers, query parameters, and body.

• Incoming webhook trigger per workflow
• Bearer, basic, and API-key authentication
• JSON, form, raw, or automatic Chirply payloads
• Merge fields work in URLs, headers, queries, and bodies

Every bulk action runs as a job you can watch and steer. Pause it, stop it, move its start time, or slow it down while it is running — the change lands on what has not gone out yet, and never on what already has.

• Pause, resume, cancel, reschedule or re-pace a running job in a single action
• A cursor tracks exactly what has been sent, so re-pacing or stopping only touches the remainder
• Scheduled jobs wait here until their start time, honouring send windows and per-minute, per-hour and per-day throttles
• Covers outbound work — bulk email, SMS, automation enrollment, action runs — and bulk record updates like tags, lifecycle, lists and deletes

Define your own call dispositions (name + color) in Settings, then attach actions to them. Choosing an outcome fires those actions in the background while you're already dialing the next number — and the calls nobody logged are collected into a queue instead of quietly disappearing.

• "Left voicemail" → text them, tag them, and enroll them in a follow-up sequence — automatically
• Any action in the platform is attachable: SMS, email, RVM, tag, list, pipeline stage, task, AI call
• An "awaiting outcome" review queue catches every call no browser saw end — desk phones, the mobile app, sales-bridge legs — with a workspace-wide count and one click to work through them
• Set an outcome on any past call, including calls made before you had outcomes at all; the same actions and automations fire either way

Rule-based audiences over the contact record and everything attached to it, so “booked but never showed, and nobody has called them in two weeks” becomes a saved segment you send to — not a spreadsheet someone exports again every Monday.

• 49 built-in fields grouped as Contact, Address, Consent & safety, Membership, Broadcast email engagement, Website engagement and CRM activity — plus every custom field you have added
• Related-record rules across Bookings, Stripe, Sales, Work, Conversations, Calls and Forms, with 45 more filters underneath them
• Text, number, date, boolean and relation operators — including “is in the last N days” and count rules like “has more than two open tasks”
• Every filter on a related record has to match the same record, so two unrelated appointments can't fake a match