Actions
Actions are the steps in a workflow that do something, such as retrieve data, send messages, update external systems, or perform calculations. You can add any number of actions to a workflow after the trigger. Actions are executed in sequence.
There are two broad categories of actions:
- Data retrieval actions: Retrieve data from your webstore, such as Get baskets, Get shop accounts, Get pending order authorizers. You can receive either a single item at a time or a list of items (in batches of up to 100 items).
- Execution actions: Perform operations based on retrieved or available data, such as Send email, Send HTTP request, Google Sheets - Append row, Google Sheets - Clear rows.
Available actions:
- For Each
- Get Baskets
- Get Pending Order Authorizers
- Get Shop Accounts
- Google Sheets (Clear Rows and Append Row)
- Send Email
- Send HTTP Request
Data Retrieval
Data retrieval actions, such as Get baskets, Get shop accounts, Get pending order authorizers, can return large datasets, sometimes thousands of records. To handle this efficiently without overloading the workflow, data can be retrieved either one item at a time or as a list (in batches of up to 100 items).
Each of these actions provides two output handlers that let you define what happens with each item or list:
-
Single item:
-
For each [item]: Defines the action that runs for each item returned.
-
After all [items]: Defines the action that runs after all items have been processed.
-
-
List of items:
-
For each list of [items]: Defines the action that runs for each list returned.
-
After all [items]: Defines the action that runs after all items have been processed.
-
Use For each item and For each list of [items] to process each item or list (the For each action) as it arrives and check something (Condition). Use After all items to perform some action after all items have been processed, such as sending an e-mail notification to the webstore administrator.