Skip to main content
Automation API

delay

Use this action to pause an automation run for a fixed time before the next action.

Tip

Read the live config shape of each action type from GET /v1/automation/meta/action before you build on it.

In the automation editor, this action is Delay execution in the Flow control family. Its group is action, and it works with every trigger.

Send it in the actions array of Create an automation or Update an automation. An update replaces the whole array, so include the other actions.

Example​

This action waits 30 seconds, for example to give a teammate time to finish editing a task before the next action reads it:

{
"type": "delay",
"config": {
"delay_ms": 30000
}
}

Config​

PropertyTypeDescriptionExample value
delay_msenum (integer)Required. How long the run pauses, in milliseconds. See Delay values.30000

Delay values​

delay_ms takes one of these numbers:

  • 15000: 15 seconds.
  • 30000: 30 seconds.
  • 45000: 45 seconds.
  • 60000: 60 seconds.

General behavior​

  • delay_ms is the only key, and it's required. It has no default.
  • Tape accepts only 15000, 30000, 45000 and 60000. It rejects any other value.
  • The run pauses for the given time, then goes on with the next action.
  • For a longer wait, use the date_field_arrived or periodic trigger.
  • With a trigger that has a record, Tape reloads the current record after the pause. Later actions see its latest field values.

Requirements​

  • To add or change this action through the API, your token needs the automations:edit capability. See Capabilities.
  • You must administer the workspace that the automation's database app belongs to.

Next steps​