Skip to content

Trigger Workflows on Deals

The current Create Deal dialog.

The current Create Deal dialog.

The trigger actions below use active workflows for the Deal record type. A contact workflow will not appear in their picker, and if the picker has no options, activate a Deal workflow first. To start a contact workflow, such as a seller drip, for the contacts on a deal or in a pipeline stage, see Start a contact workflow for a deal’s contacts at the end of this article.

  1. Open the deal from a pipeline board or list.

  2. In the deal detail view, open the overflow menu and choose Trigger deal workflow.

  3. Choose one active Deal workflow, then select Trigger.

  4. Goliath confirms when the workflow run has started.

  1. In Pipelines, check the deals you want to include (a deal’s checkbox appears when you point at it).

  2. In the selection bar, choose Trigger workflow.

  3. Choose one or more active Deal workflows, then select Trigger.

  4. Goliath schedules the workflow runs. The confirmation changes when the bulk processing result is available.

Each Kanban column has a stage-level action for the records currently matching that stage.

  1. Filter the pipeline first if you need to limit the deals in scope.

  2. In the stage header, open More actions and choose Run deal workflow.

  3. Choose one or more active Deal workflows, then select Trigger.

Start a contact workflow for a deal’s contacts

Section titled “Start a contact workflow for a deal’s contacts”

Start workflow enrolls the contacts linked to a deal in an active contact workflow. It is separate from the trigger actions above: the workflow it starts is a contact workflow, not a Deal workflow.

  1. Open the deal and find Contacts. Start workflow appears there once the deal has a linked contact, except when its only contact is one you cannot access. On a phone, it is its own row in the deal’s details. Once the deal has a linked contact, its overflow menu also has Start contact workflow, which opens the same window.

  2. In the Start a workflow window, choose one or more active contact workflows. When you choose exactly one, the window may show a notice about your texting registration or credit balance; the notice does not stop you from starting.

  3. When the deal has several contacts, every contact you can access is checked to begin with. Uncheck anyone who should not get the workflow. A contact you do not have access to is shown as No access and is not included, and if none of them is included, Start is unavailable. When the deal has one contact, the window says it starts for that contact, or that you do not have access to them.

  4. Select Start. When the deal has several contacts, the button also says how many are included, for example Start for 3 contacts.

A contact who is already in the workflow you pick, or has already been through it, is not started again, and some contacts, such as one marked do not contact, cannot be enrolled. The exception is a contact whose run of that workflow is paused because a teammate paused it or because the contact replied: Start continues that run where it stopped and counts the contact as enrolled. If the run cannot be continued, the contact counts as already been through the workflow. Once the runs are scheduled, a message reports how many contacts were enrolled, how many had already been through the workflow, and how many could not be enrolled, for example “2 enrolled, 1 already been through”. To run a workflow again for a contact who has already been through it, start it from that contact’s own record; see Trigger a Workflow on Contacts.

To start a contact workflow for a whole pipeline stage, open the stage header’s More actions menu and choose Start workflow. The window says how many contacts it will start for, and the button reads Start for n contacts. It reaches the contacts on every deal in that stage that is not archived, whatever filters are on the board. Each contact is handled as described above. The window says anyone already in the workflow is skipped, but a contact whose run of that workflow is paused, by a teammate or because they replied, has that run continued.