githubEdit

Settings

Configure your Mechanic account — contact email, Shopify permissions, outbound email, webhooks, integrations, and more.

The Settings page is organized into tabs. The General and User tabs cover the most common settings — the other tabs are for specific features you can explore as needed.

The Mechanic Settings page showing the General tab

General

  • System contact email — receives Mechanic system notifications, like rate limit alerts or platform maintenance announcements. Supports multiple addresses separated by commas.

  • Read all orders — by default, Mechanic accesses the last 60 days of order history. Enable this if you have tasks that need to search older orders. Learn more in Read all orders.

  • Subscription — your current plan and billing status.

User

  • Use Advanced mode by default — open the task editor in Advanced mode (for editing code) instead of Basic mode (for adjusting settings)

  • Show shop identity banner — display a banner identifying the current shop (helpful when managing multiple stores)

  • Use dark theme for code editor — apply a dark theme to all code editors in the app

Permissions

Mechanic automatically detects the Shopify API permissions your tasks need — you don't need to manage this manually. This tab shows which permissions are currently granted and which are required.

Webhooks

Only needed if external apps need to trigger your tasks. Create webhooks to send events to Mechanic from outside Shopify — for example, when a form is submitted on your website. Each webhook gets a unique URL you can POST data to.

Email

  • Default outbound email — the auto-assigned email address Mechanic uses for sending, with email verification status

  • Custom outbound email — use your own domain, verified via DNS records. See Custom email addresses.

Email templates

Create reusable HTML email templates for use in tasks. Templates support Liquid variables.

Cache endpoints

Only needed if external apps need to read data from your tasks. Create URLs that return cached task data as JSON — useful for dashboards or integrations that need to pull information from Mechanic.

Event filters

Advanced. Liquid code that runs before tasks to decide whether an event should be processed — for example, skipping test orders or pausing processing during maintenance. See Event filters.

Authentication

Only needed if your tasks use Google Sheets, Airtable, or Slack integrations. Connect your accounts here so tasks can interact with those services. Credentials are encrypted and stored securely. See Integrations.

Last updated

Was this helpful?