Guides

Automations on the pipeline

Your automations and your pipeline work together. A deal moving to Won can start an onboarding email; an automation can put a contact on the pipeline or give a colleague a task to call them; and a follow-up can stop the moment the person writes back. These need your pipeline set up (Pipeline in the menu), and the reply rules need reply tracking.

When a deal enters a stage

An automation can start when a deal enters a stage you pick, Won and Lost included. It runs for the deal's main contact, whether the deal was made in that stage or moved into it, from the board, the list, a reply or another automation.

  • It runs once for each deal that enters the stage. A deal moved out and back in does not start it again.
  • Only deals that enter the stage while the automation is on count, and only if it is still on when we handle the move. Turning it on, or resuming it, never catches up deals moved before, so a deal moved in the minute before you pause it may start nothing.
  • A contact is in an automation once at a time: while their run is still going, another of their deals entering the stage starts nothing for them.
  • A deal with no main contact starts nothing, and nor does a deal moved because its stage was deleted.
  • It usually starts within a minute of the move, and within 5 minutes at the latest. If we were down, we catch up for up to 3 days; a move older than that starts nothing, so nobody gets an email about a deal they closed last week.

When a contact books a meeting

Once meetings can come in, on your booking pages or through Calendly or Cal.com (see meetings from Calendly and Cal.com), an automation can start when one of your contacts books a meeting. Start it from the Prepare for a booked meeting blueprint below; its first card takes every meeting, or only those whose name contains words you choose, with capitals ignored.

  • It runs for the contact with the guest's email address, once for each new meeting booked while the automation is on. Turning it on never catches up meetings booked before.
  • From Calendly or Cal.com, a guest who isn't one of your contacts starts nothing. A booking page makes such a guest a contact who isn't subscribed: their run goes as far as its first email, which goes only to your mailing list, and ends there. A meeting cancelled before we handle it starts nothing, and a new time for a meeting is the same meeting, so it starts nothing new.
  • It usually starts within a minute of the booking, and within 5 minutes at the latest. A booking we received more than 3 days earlier starts nothing.

Any automation can also Stop when they book a meeting, beside the reply rule under its last card: checked before every email and every pipeline step, so someone who booked a meeting after their run started gets nothing more from it. Both need a booking page or a Calendly or Cal.com connection, and the automation can't be turned on without one.

Add to pipeline

The Add to pipeline step gives the contact a deal in the open stage you choose, with an owner if you pick one. It makes nothing when the contact is already on an open deal. The deal is named after the contact's company, or else their name, or else their address, and its history says which automation made it. Nobody is told when a deal is made this way, and a deal made this way can itself start an automation that waits for that stage.

Create a task

The Create a task step gives your team a task about the contact: a title of up to 200 characters, due on the day the step runs or up to 365 days after it (your account's day, in its time zone), and, if you choose, someone it's for. That person is told in the app, and the task is in their daily tasks email when it's due. The task shows on the contact's page and in Pipeline → Tasks. A contact gets one task each time they reach the step, even if the step is tried again.

Stopping on a reply

Two rules read replies to this automation's emails. Both count only replies to emails with Track replies on, and only real ones: an out-of-office or another automatic reply never counts.

  • Stop when they reply to an email from this automation, under the automation's last card: checked before every email and every pipeline step, so someone who wrote back gets nothing more from it.
  • The condition Replied to an earlier email in this automation: yes when they replied to an email sent before the condition, so you can send a different follow-up, or make a task, for those who did.

Inside a condition

A condition's yes and no branches can wait, add a tag, add the contact to the pipeline or create a task. The automation goes on to the next step after the branch. A branch can't send an email: put the email after the condition. Pausing the automation stops a contact before their next email or pipeline step, and before a condition whose branches have pipeline steps; once they are inside a branch, its steps run to its end.

The blueprints

  • Thank them when a deal is won: when a deal enters Won, a thank-you email goes to the contact and your team gets a task to start the work.
  • Follow up on a new deal: when a deal enters your first stage, someone gets a task to call the next day; two days later a short email follows up, with Track replies on; and three days after that, a second task if they still haven't replied. It stops as soon as they reply, so it is offered when reply tracking is open for your account.
  • Prepare for a booked meeting: when a contact books a meeting, someone gets a task to prepare, due that day, and a contact on your mailing list gets a short note on what to expect. It is offered once you have a booking page or have connected Calendly or Cal.com.

They appear when you make an automation once your pipeline is set up. You can change every step, and the stage, before you turn one on.

When a stage or a person goes

If a stage the automation names is deleted, or a deal's owner or a task's person leaves your team, the automation says so where it is set, and can't be turned on or resumed until you pick another. Until then, a running automation on a deleted stage starts nothing, its Add to pipeline step makes no deal, and someone who left is left off the deal or the task.

Test runs

A test run (an event sent with a ps_test_ key, see test mode) makes no deal and no task, as it adds no tag: a test exists to try the automation, and a deal or a task it made would be a real one on your pipeline.