Actions
Actions are defined by tasks using action objects, which are simple JSON objects specifying an action's type and options. Action objects can be constructed using the action tag.
Actions are performed asynchronously, which means their results are only accessible after the conclusion of the related task and action run (See Responding to action results).
An action type determines the class of operation to be performed. While actions may vary greatly, there are only a few action types.
Action | Purpose |
Performing operations on the store's Mechanic cache | |
Debugging; displays the options that it is provided, with no side-effects | |
Sending transactional email | |
Generating custom user events | |
Generating files of various types, storing them at a temporary Mechanic-provided URL | |
Performing FTP file uploads and downloads | |
Performing HTTP requests |
Mechanic maintains a set of integration actions, offering first-class support for several external services.
Action | Integrated service | Purpose |
|---|---|---|
Shopify Flow | Sending customer, order, product, and general triggers to Shopify Flow | |
Shopify Admin API | Sending requests to the Shopify Admin API, supporting both REST and GraphQL | |
Report Toaster | Requesting reports from Report Toaster, or updating data within Report Toaster |
Last modified 1yr ago