Workflows: Wait node

This article explains the Wait node that can be configured as part of Workflows. Learn more about using workflows here.

‍

‍

Help video

‍

Used For

1. Waiting for a fixed amount of time before executing the next set of actions. For example, wait for 30 minutes before sending a welcome email.
2. Generating reminder notifications on Renewal date, Expiration date etc.

‍

Editing the block

Click on the block and start editing on the panel that appears on the right side.

‍

Step name

This is the name that appears in the Workflow on the left side. If there are multiple Wait nodes in the workflow, set different step names like Wait 30 minutes, Wait 1 day etc.

‍

Wait Type

Used to decide between the following two options:

Wait For: Wait for a fixed amount of time.
Wait Till: Wait till some date field variable in the app.

‍

Parent Step

Parent step refers to the function which is just above the wait node. Here, it is the Start function.

‍

Enable this Step

This step is enabled by default. Disable this node to stop this workflow step and all the workflow steps below it.

‍

Wait Type - Wait For

‍

This field takes the number of seconds to wait for. If we want to wait for 5 minutes before proceeding, we can input 5 * 60 in this field.

‍

Wait Type - Wait Till

‍

This field takes a date variable and a time variable from the app. The node will wait until that date and time has reached. For example, if we want to wait till the reminder date before sending a reminder email, we can just put the variable name of the Reminder Date field from the app in the Wait Till Date field. In the Wait Till Time field, we can either put a static time value in HH:mm format or we can use a time variable from the app. Learn more about using variables in workflows here.

‍

‍

Note on Workflows and Bulk Operations

Workflows in Clappia run on individual submissions, such as when a user submits or manually edits a record. However, when using Bulk Upload or Bulk Edit from the Submissions tab, workflows are not triggered, even though new submissions may be added or existing ones updated.

This is because workflows are designed to process one submission at a time. Triggering them for bulk operations can lead to incomplete or inconsistent results, especially for complex workflows.

If you need workflows to run after a bulk operation, currently you will need to open each submission manually and save it. This will count as an edit and trigger the workflow normally.