Skip to content
Outboundrix
Start free

Product · Workflows

When something happens, the next step runs itself.

A workflow starts on an event in your workspace, or when another system posts to its own URL, and runs steps on the person or deal it is about: a sequence, a tag, a stage, a task, a deal, a Slack message or a call to any API whose answer the next steps can use, with branches, waits and waits for a reply.

Start free
The whole product
Workflow · Proposal follow-upexample data · on
  1. ▸When… · A deal moved to a stageOnly for stage: Proposal
  2. 1Create task · Send the proposal to {{trigger.first_name}}Due in 1 day · High
  3. 2Wait · 2 daysThe run waits, then carries on
  4. 3Slack message · Proposal out: {{trigger.deal_name}}If this step fails: carry on with the next step
One run per eventWaits up to 90 daysWebhook URL encrypted
Building blocks

Starts on what happens. Acts on the CRM.

Add a step from a searchable list, set it up in its own dialog, and use values from the event and earlier steps in any text, with a fallback when one is missing.

Starts when

  • A lead replied, opened an email, clicked a link, bounced or unsubscribed
  • The reply agent labelled a reply (interested, objection, out of office …), for the label you pick
  • An email was sent, a lead finished a sequence, or a send failed for good
  • A contact was added, from any source
  • A tag was added or removed, for the tag you pick
  • A deal was opened, moved to a stage, won or lost, for the stage you pick
  • A meeting was booked
  • Another system posted to the workflow’s own URL; a field in the body can name the contact

Then

  • Add to a sequence, or stop one
  • Add or remove a tag; set the contact’s stage
  • Create a task, create a deal, move a deal
  • Post to Slack, or call any API (GET, POST, PUT, PATCH or DELETE) with your own headers and use its answer in the steps after it
  • If / else on the contact’s fields, tags, mail service or the event
  • Wait minutes to days, or wait for a reply
Unattended

Built to run without you watching

Runs that pick up where they stopped

A run keeps the workflow it started with and records each step’s result, so a wait of up to 90 days resumes exactly where it parked.

One run per event

An event starts a workflow once, and a post repeated within a day with the same Idempotency-Key starts it once. Two workflows moving a deal back and forth stop after three hops.

Credentials stay secret

Slack webhook URLs, HTTP URLs and headers are encrypted when saved and only ever shown back masked; a workflow’s own URL is kept only as a hash.

You choose what a failure does

Each step either stops the run or carries on with the next one when it fails.

Test before you switch it on

A test run shows each step’s result, and a workflow with a missing field cannot be switched on until it is fixed.

Every run on the record

Each run shows in Runs as it happens, and step by step in the workflow’s Details.

Plans

Workflows are on every plan: 2 on at once on Free, 10 on Startup, 50 on Teams and 150 on Agency. App actions and the webhook trigger come with Startup, HTTP requests with Teams, and workflows on a reply’s label with the reply agent on Teams.

Compare plans

Not built yet

Credentials are kept per step (a Slack webhook or an API key), not as named connections you reuse, and steps that act inside other apps you connect are not switched on yet. A reply is labelled only by the reply agent, so without it a workflow cannot start on a reply’s intent, and a workflow sends no SMS or LinkedIn messages.

NextProspects People, companies and lists in one place: imports, the lead scraper, email checks and the lead qualifier.

Run the motion, not the stack.

Bring your list, send from mailboxes you own, and let the reply agent work the replies. Start on the free plan: no card, no sales call.

Start freeNo credit card required