Shopify Flow
Last updated
Was this helpful?
Last updated
Was this helpful?
Mechanic allows developers to integrate their work with via an official Flow connector, sending triggers to Shopify using Mechanic's , and receiving events from Shopify using custom event topics in .
Flow is Shopify's answer to automation for Plus merchants: a graphical tool that allows for defining automation using flowchart-like structures.
From :
Shopify Flow is an ecommerce automation solution that was purpose-built to help solve the unique challenges that Shopify merchants face. With Flow, you can build workflows to automate tasks, campaigns, and processes within your store and across your apps.
As an automation tool itself, Flow has its own terms for the components of automation.
A package of configuration, containing a trigger, zero or more conditions, and one or more actions. Analogous to a Mechanic task.
An event from Shopify or another connector (like Mechanic), which can be used to set workflows. Analogous to a Mechanic event.
A logical check which evaluates some data (possibly provided by the trigger), and steers the workflow towards specific actions. Loosely analogous to the code in a Mechanic task.
Work to be performed, at the conclusion of a workflow's run. Directly analogous to a Mechanic action.
Mechanic's Flow connector works in both directions: Mechanic â Flow, and Flow â Mechanic.
Beginning on the Mechanic side, the Flow action sends data to Flow, arriving in the form of a trigger, and setting off the Flow workflows configured there.
Beginning on the Flow side, the Mechanic action sends data to Mechanic, arriving in the form of a new event, setting off the Mechanic tasks configured there.
On the Flow side, workflows may be configured to listen for any of these four Mechanic triggers.
General
Send user-defined data to a Shopify Flow workflow.
Customer
Send a customer ID to be pulled up in context in Shopify Flow.
Send user-defined data to a Shopify Flow workflow.
Order
Send a order ID to be pulled up in context in Shopify Flow.
Send user-defined data to a Shopify Flow workflow
Product
Send a product ID to be pulled up in context in Shopify Flow.
Send user-defined data to a Shopify Flow workflow
All four triggers include the following user-defined data variables, given as options to the Flow action. If a variable is omitted from the action's options, Mechanic will still send it to Flow, using a default value.
To choose between trigger types, choose between defining exactly one specific Shopify resource ID (i.e. for a customer, order, or product, resulting in the appropriate resource trigger), or omitting a resource ID entirely (resulting in the General trigger).
On the Flow side, configure workflows to start with the appropriate Mechanic trigger.
The Mechanic action, in Flow, sends new events to Mechanic.
Event topic
Event data
Optional; must be valid JSON.
Task ID
Optional; restricts processing of the resulting event to a single Mechanic task. Note that the task must still subscribe to the event topic for it to receive these events.
If the event data configuration results in invalid JSON, the resulting Mechanic event will contain data reflecting the JSON error encountered. Here's an example:
Shopify Flow workflows are triggered from the Mechanic side, using Mechanic's . There are four triggers to choose from: General, Customer, Order, and Product. Mechanic's Flow action can produce any one of these four triggers, depending on the action options given.
Required; must start with "user/", resulting in an event in .
The resulting Mechanic event will have a topic and data reflecting the Flow action configuration. Event data is available to tasks via event.data, as usual. (For more on how to use event data, see .)
When using Flow's template variables for event data, remember to use as necessary, for making template variables safe for use in event data. Here's an example of event data, using template variables and the json filter:
