Actions

Use action steps to perform Skedulo operations: create records, dispatch jobs, send notifications, and more.

Overview

An action step executes a built-in Skedulo operation as part of an automation. Actions cover a wide range of operations: creating and updating records, dispatching jobs, sending notifications, making HTTP requests, and more.

Each action step has a set of arguments that configure what it does. Arguments can be set to static values or to JSONata expressions that compute values at runtime from trigger data, previous step outputs, or workflow variables.

When an action step completes, its output is made available to all subsequent steps under a variable named after the action, for example, the output of a Create Record step is accessed as $createRecord.

Available actions

For the full list of actions, their arguments, and their output fields, see the Action Reference.

Referencing action output

Each action exposes its result under a $actionName variable. Use dot notation to access individual fields within the output.

Example: reference the UID of a record created by a Create Record step:

$createRecord.result.data.uid

Example: pass the output of a Get Record step into a subsequent action:

$getRecord.result.data.Name

The exact fields available depend on the action. See the individual action pages in the Action Reference for the full output schema of each action.

Expression examples

Goal Expression
Use a trigger field as an action argument $trigger.current.AccountId
Use the UID returned by a previous Create Record step $createRecord.result.data.uid
Build a string from trigger fields $trigger.current.FirstName & ' ' & $trigger.current.LastName
Use a previously set variable $jobId
Conditionally pass a value $trigger.current.Priority = 'High' ? 1 : 2
Check whether a previous action succeeded (in a Choice condition) $count($createRecord.result.errors) = 0

See also