A complete index
Mechanic supports a variety of event topics, each a classification of an event. This page is a complete index of pre-defined topics, organized by domain.
- mechanic/actions/perform Occurs when an action has been performed, regardless of its success or failure. A task may subscribe to this topic to be notified when each of its actions have been performed, so that the task may then respond to the results.
- mechanic/emails/received Occurs when Mechanic receives an email sent to the store's dedicated email address. (A store at example.myshopify.com can receive email at [email protected])
- mechanic/scheduler/10min Runs every 10 minutes.
- mechanic/scheduler/15min Runs every 15 minutes.
- mechanic/scheduler/20min Runs every 20 minutes. (You see where this is going.)
- mechanic/scheduler/30min Runs every 30 minutes.
- mechanic/scheduler/hourly Runs every hour, on the hour.
- mechanic/scheduler/daily Runs at midnight, in the store's local timezone.
- mechanic/scheduler/monday Runs every Monday at midnight, in the store's local timezone. (Note: this would be at the end of Sunday evening). Each named weekday is supported.
- mechanic/scheduler/monthly Runs at midnight on the 1st of the month, in the store's local timezone.
More specific times can be achieved by subscribing to an event topic with a delay (e.g. "mechanic/scheduler/daily+5.hours"). There is no limit to the length of the delay, including delaying longer than the scheduler interval itself (e.g. "mechanic/scheduler/daily+100.hours"). To learn more, see Subscriptions.
Not to be confused with events in the User domain, the mechanic/user event subject describes ways that the user expresses their intent – to Mechanic – to run the task. Run links are available for these topics.
- mechanic/user/trigger When used, adds a "Run task" button to the task itself. This button generates a new event, to which only this task will respond.
- mechanic/user/text When used, adds a "Run task" button to the task itself. This button prompts the user with a multi-line text box. When submitted, an event is generated, to which only this task will respond. The event contains the user's input in its data, making user's input available in
The following mechanic/user topics are typically used with Shopify admin action links, and are documented there more fully.
- mechanic/user/abandoned_checkout mechanic/user/abandoned_checkoutsOccurs when a user sends one or more abandoned checkouts to Mechanic
- mechanic/user/collection mechanic/user/collections Occurs when a user sends one or more collections to Mechanic
- mechanic/user/customer mechanic/user/customers Occurs when a user sends one or more customers to Mechanic
- mechanic/user/draft_order mechanic/user/draft_orders Occurs when a user sends one or more draft orders to Mechanic
- mechanic/user/order mechanic/user/orders Occurs when a user sends one or more orders to Mechanic
- mechanic/user/variant mechanic/user/variants Occurs when a user sends one or more product variants to Mechanic
- mechanic/user/product mechanic/user/products Occurs when a user sends one or more products to Mechanic
These events are generated by Shopify webhooks, and are automatically configured for you by Mechanic. Tasks subscribing to Shopify events receive Liquid environment variables, containing data from the webhook.
Mechanic does not support Shopify event topics that are scoped to an individual app. For example, Shopify only sends product_listings/add events to the app responsible for the relevant sales channel, and only sends subscription_contracts/create events to the app responsible for the relevant customer subscriptions. This scoping renders topics like these irrelevant for apps like Mechanic.
For a description of each topic's behavior, see Shopify's documentation:
Note that all topics are represented in the WebhookSubscriptionTopic enum documentation, but not all topics are covered in the REST resource documentation.
The User event domain is for custom, user-generated events, having any subject and verb (e.g. "user/foo/bar"). As with all events, a User event topic must use the standard three-part topic form, but only the "user/" prefix is mandatory.
Mechanic allows developers several ways to generate custom User events:
- judgeme/review/created — Occurs when new Judge.me reviews are received. Requires enabling the Mechanic integration within Judge.me; see Judge.me's integration announcement.
- judgeme/review/updated — Occurs when Judge.me reviews are updated. Requires enabling the Mechanic integration within Judge.me; see Judge.me's integration announcement.
Mechanic invites third-party app developers to develop Mechanic integrations, making it easy for developers to use our services together. If you're an app developer interested in this, email [email protected].