A workflow action is what you want the workflow to do. For example, this could be sending an email or creating a reminder.

You can even include actions that help you manage the workflow itself to affect how the workflow runs. This article goes in-depth on the various workflow management actions.

Article Shortcuts:

Click on a topic to jump to that section!


Pause Workflow

What it does: prevents the workflow from completing any actions until it is manually un-paused.

When a Pause Workflow action is triggered, the entire workflow will shut down. In order to get the workflow up and running again, you will need to go into the project, head to the workflows tab and click the yellow Paused button. Once the button turns green and reads Active, the workflow is running again.

Common uses: Starting a workflow with a Pause action allows you to make changes to the actions when you need to heavily customize a workflow from project to project. Sometimes you may want a workflow to pause after a client completes a form or books an appointment if you want extra time to prepare for the next steps.


  • When the workflow pauses, you will not get a notification to un-pause the workflow. You will need to remember to manually un-pause the workflow. Once a workflow is paused, it won't even create todo reminders!

  • Use workflow pauses sparingly as a last resort. If you have more than one or two pauses in your workflow, you are probably not using other actions and triggers to their full potential. Why are you pausing the workflow and is there another trigger or action that could create a similar effect?


Hold Actions Until

What it does: prevents future actions in the workflow that are triggered "after all previous actions complete" from running until a certain condition is met.

This can be a tricky action to wrap your head around, but it allows for some powerful customization of timing in your workflow!

Hold Actions Until allows you to tell certain actions to wait to run until a specific condition is met. Once the Hold Actions Until action is triggered, the actions affected by the hold will be "released" to run normally. You can use more than one hold action in a row to require multiple conditions.

For an action to be affected by a hold, it MUST be triggered "after all previous actions complete" AND be positioned below the hold action in the workflow.

Actions with any other trigger (project date, after form is completed, etc.) in the workflow will completely ignore the hold.

Common uses: Requiring multiple conditions to be met before running another action, for example, requiring the invoice to be paid, contract to be signed, and an intake questionnaire to be completed before sending an email.

In the example above, you'll see that we've stacked three hold actions to ensure all three conditions are met, before sending the welcome email. The Send Email action is triggered "after all previous actions complete" so it will be affected by the hold - it will not run until the invoice is paid, the contract is signed, and the form is completed.

Notice the project wrap-up email triggered "1 day before the project end date". This action will NOT be affected by the hold because it is not triggered "after all previous actions complete."


  • Just like pauses, use the hold action sparingly. Try to accomplish the same effect by using specific triggers on your actions first. If it can't be done with triggers alone, you have a good indication that using a hold is the way to go!

  • If there are actions that will not be affected by the hold because of their trigger, you may want to add an approve button to prevent them from running without your approval.


Start a Workflow

What it does: applies and activates a new workflow on the project.

How to set it up:

  1. Select the workflow you would like to start at this step from the Choose a Workflow dropdown.

Common uses: The Start a Workflow action allows you to string multiple workflows together for longer processes with phases. Instead of creating one giant workflow with many actions, consider breaking up the process into logical phases. Shorter workflows are easier to comprehend and maintain.


  • The new workflow will not be added to the project or visible in the Workflows tab until this action is triggered, unlike how forms are pre-loaded in the Forms tab as soon as the workflow is applied.

  • If you want to review the new workflow being applied before it kicks off, you'll need to start the new workflow with a pause action or require approval on the first action. The Start a Workflow action does not have a require approval option.

  • The same workflow cannot be applied to the same project more than once simultaneously, so this action cannot be used to create a recurring workflow. For example, you cannot start Workflow A from within Workflow A. You would need to manually remove Workflow A from the project before applying it again.

  • Workflows running simultaneously on the same project do not communicate with one another. For example, if you send a form in Workflow A, you cannot trigger an email to send when the Form is completed in Workflow B. Each workflow must be structured to be self-contained.

Did this answer your question?