Action objects

An action object defines work to be performed by an action, after the task is fully finished rendering. Action objects are most easily generated using the action tag.

An action object is a plain JSON object, having the following structure:

{
"action": {
"type": ACTION_TYPE,
"options": ACTION_OPTIONS,
"meta": ACTION_META
}
}

Use the action tag to skip the boilerplate while writing actions.

Defining an action

Type

The action type is always a string, having a value that corresponds to a supported action (e.g. "shopify", or "http").

Options

Action options vary by action type. Depending on the action type, its options may be another complete object, or an array, or a scalar value.

Meta

Actions may optionally include meta information, annotating the action with any JSON value.

This information could be purely for record-keeping, making it easy to determine why an action was rendered, or to add helpful context:

{
"action": {
"type": "shopify",
"options": [
"post",
"/admin/customers/1234567890/send_invite.json",
{}
],
"meta": {
"invite_reason": "alpha"
"customer_email": "[email protected]"
}
}
}

Or, this information could be used to facilitate complex task flows, in concert with a subscription to mechanic/actions/perform (see Responding to action results). An action's meta information can supply followup task runs with information about state, allowing the task to cycle between different phases of operation.

{% if event.topic contains "trigger" %}
{% action %}
{
"type": "cache",
"options": ["set", "foo", "bar"],
"meta": {
"mode": "first"
}
}
{% endaction %}
{% elsif action.meta.mode == "first" %}
{% action %}
{
"type": "cache",
"options": ["set", "foo", "bar"],
"meta": {
"mode": "second"
}
}
{% endaction %}
{% elsif action.meta.mode == "second" %}
{% action "echo", "done" %}
{% endif %}