Mechanic
🧑‍💻 Get Mechanic!🧑‍🔧 Task library🗳 Task requests🦾 Mechanic.dev
Search…
Introduction
💯
status.mechanic.dev
🙋
"I need something custom!"
🤓
Hire a Mechanic developer
Resources
🧑💻
Task library
🚀
Slack community
🤝
Partner directory
Tutorials
Core Concepts
Events
Topics
Parent and child events
Tasks
Actions
Runs
Interacting with Shopify
Platform
🔆
Policies
Cache
Email
Events
GraphQL
Integrations
Liquid
Shopify
Webhooks
Techniques
Writing a high-quality task
Tagging Shopify resources
Debouncing events
Responding to action results
Working with external APIs
Finding a resource ID
Migrating templates from Shopify to Mechanic
Securing Mechanic webhooks
Monitoring Mechanic
FAQ
Powered By GitBook
Events
In Mechanic, an event represents anything that happens. This could be an order being paid, or a customer record being created, or a fulfillment being delivered.
An event always has a topic, and data (even if the data is null/nil). Events may trigger any number of tasks, resulting in any number of actions.
Events are fed into Mechanic by the responsible party – for events that are about things in Shopify, for example, the events come to Mechanic from Shopify itself.
Incoming events may be selectively skipped using event filters.
Previous
Creating scheduled CSV feeds
Next
Topics
Last modified 18d ago
Copy link
Edit on GitHub