Search results for creating scheduled feeds

44 articles found

  • Creating scheduled CSV feeds

    In this tutorial, you'll learn how to create a feed of your shop's data, and make it available on your online store, at a URL like Tip: The data you generate can be

  • Can I send data to Google Sheets?

    Yes! There are two options: One uses the IMPORTDATA function within Google Sheets to pull data from your store into your spreadsheet. The other lets you dynamically push new data to Google Sheets,

  • Can I schedule tasks for the future?

    In Mechanic, the decision to schedule an event is an action all by itself – the "event" action. This means that the flow for scheduling looks like this: Task A is created, subscribing to a user event

  • Can I schedule events for a custom interval?

    Mechanic offers several scheduler event topics (like "mechanic/scheduler/10min"), for performing work on recurring intervals. (For the full list, see the "Scheduler" section of All event topics.) If

  • Can I schedule tasks for a certain time of day?

    Yes! This is configurable via the task's subscriptions (available in each task's advanced settings). You'll want to start with one of Mechanic's scheduler events (see All event topics / Mechanic).

  • Can I schedule a task for a certain day of the month?

    To set up your task to run on a specific day of every month – say, the first of the month – have your task subscribe to mechanic/scheduler/daily, then use logic like this inside your task script: {%

  • The anatomy of a store-to-store sync

    Note: Creating a task for this purpose does involve writing Liquid code. Mechanic has two features that make syncing data possible: Webhooks – read more The "http" action – read more Using these two

  • Writing a high-quality task

    Here are some best practices we've found, as a community, about writing tasks that improve life for everyone. Know how Mechanic uses Liquid. We've extended the language with new tags and filters –

  • The "event" action

    Event actions are powerful. They allow you to invoke other tasks as a response to an incoming event. And, because a single task can subscribe to multiple event topics, it means you can create

  • What's possible with timeline comments?

    What's possible Reading timeline comments, and other events, for orders, draft orders, customers, and inventory transfers. Writing order and customer notes. This is not the same as the timeline

  • All action types

    New to Mechanic? Learn more about actions here. Cache – Allows you to manipulate a simple key/value cache, giving your tasks a short-term memory. Echo – Useful for debugging and logging. Use it to

  • Why can't I access the Shopify API during preview mode?

    If you're reading this, you may be wondering why your task doesn't seem to be able to access the Shopify API, while you work on the task script. Read on! A task is always run in response to an event.

  • Using a custom Shopify API password

    In high-volume scenarios for Shopify Plus accounts, Mechanic's performance can be improved by creating a private Shopify app, having the same permissions that you've granted to Mechanic. Because this

  • Can I send messages to Slack?

    Mechanic's "http" action makes it extremely simple to send data to external webservices. And Slack's incoming webhooks feature makes it easy to turn that data into a Slack message. To get started,

  • Triggering Mechanic tasks with FileMaker

    Creating something purpose-built in FileMaker? You can sent data off to Mechanic for processing, allowing you to tightly integrate your database application with Shopify. 1. Create a Mechanic task,

  • Bulk operations

    This article is a summary of how bulk operations work. To learn more about creating tasks with bulk operations, see Querying Shopify. Mechanic comes with several ways to query Shopify for data (see

  • Parent and child events

    In specific cases, events may be triggered by activity associated with an earlier event. In these scenarios, we describe the subsequent event as a child event, and the preceding event as a parent.

  • Does Mechanic work with third-party APIs?

    Usually! These questions tend to fit into two categories: how to load data into Mechanic, and how to write data to an external service. Loading data into Mechanic Mechanic is an event-driven

  • Why Mechanic?

    "Should I use Mechanic?" Take a look at Mechanic's task library. If your specific need is covered there, install the task, and you'll be good to go. :) If your need isn't covered there, take a look

  • Triggering IFTTT applets

    Start by creating a new IFTTT applet. (Here's a quick link!) Click the "+ this" text to choose your trigger. Type "webhook" to quickly find the "Webhooks" trigger, and click on it to continue: After

  • Triggering tasks with IFTTT

    IFTTT allows you to plug nearly anything into nearly anything else. And, using this guide, you can use it to trigger Mechanic tasks using that same set of nearly anything. This means that you can run

  • Getting started with webhooks

    This content has moved to our new documentation site:

  • If I disable a task, will it catch up on events it missed when I re-enable it?

    For these purposes, disabling a task is essentially the same as deleting it, and re-creating it later. While a task is disabled, all connectivity to the incoming event stream is disabled – as far as

  • The task object

    Only available within a task, the task object contains attributes describing the current task itself. How to access it Use {{ }} in a task script What it contains This object is always a

  • The "ftp" action

    Useful for interacting with vendors, or simply for making logs or submitting backups, you can use Mechanic's "ftp" action to upload arbitrary content to any S/FTP host. And, by using a connecting

  • Can Mechanic interact with Shopify Scripts?

    Yes, but in a very, very limited fashion. The usual methods of integration are off limits: Shopify Scripts cannot make HTTP requests, nor can they read metafields, nor can they be invoked by external

  • Generating sequences of actions

    Mechanic's run system works asynchronously, performing as much work as possible, as quickly as possible. However, there are cases where it's important that actions run in a sequence – one after the

  • Avoiding action loops

    In some cases, it's possible to inadvertently create an action loop – in which a task run produces an action, which creates an event, which results in a task run that produces the same action all

  • The event object

    The event object describes an incoming event. How to access it Use {{ event }} in any task script What it contains event.topic – containing the event topic (e.g. shopify/customers/create)

  • I'm an app developer. Can I send my events to Mechanic?

    Short answer: almost certainly. :) Get in touch with us at Details you should know ahead of time: All event ingress works via POST requests to an endpoint that we supply,

  • Can I trigger a task from my online store?

    You can! While Shopify's online store doesn't allow you to call Mechanic from Liquid itself, you can use JavaScript to remotely create a Mechanic event from the client side, using Mechanic's webhook

  • How can I control run order?

    In general, Mechanic's run system does not guarantee the execution order for runs that have been created at the same time (see Concurrency). This applies to all kinds of runs: events, tasks, and

  • Version history

    Towards the end of a task's options area, you'll find a link labeled "Show version history". Click it to see a summary of how the task has changed over time. Use the "Restore this version" link for a

  • Responding to action results

    Sometimes, you'll want to do more than a single round of generating actions – you may want to check the results of an action, see if they appear the way you expect, and then perform additional

  • The customer object

    How to access it Use {{ customer }} in tasks responding to shopify/customers events Look up specific customers by their ID, using {{ shop.customers[12345678900] }} Look up specific customers by their

  • How can I add extra logging to my tasks?

    While Mechanic will only perform actions for well-formed action definitions, Mechanic records and displays all JSON objects generated by a task. This means that you can create your own logging by

  • Do I need to know code to use Mechanic?

    Mechanic is best in the hands of a developer, in the service of a merchant. You may find a ton of mileage by simply pulling tasks off our library shelf (and many merchants do!) – but it is common for

  • My task added a tag, but now the tag is missing – why?

    In most cases, this comes down to someone else – or something else, like another app – working on the tagged resource simultaneously. Mechanic tasks are more or less additional apps, so also keep an

  • The order_edit object

    How to access it Use {{ order_edit }} in tasks responding to shopify/orders/edited events What it contains The related order object: {{ order_edit.order }} This object contains additional properties,

  • Connecting PayPal to Mechanic

    Open up the "Settings" area of your Mechanic account: Use the "Webhooks" section to create a webhook, named "PayPal", with an event topic of "user/paypal/ipn". ("IPN" stands for "Instant Payment

  • I'm missing edges in my orders query! Why?

    So. You're working on a GraphQL query, involving orders, and you're seeing a response that looks like this: { "data": { "orders": { "pageInfo": { "hasNextPage": true }, "edges": [] } } } Maddeningly,

  • Receiving email

    Every Shopify store that uses Mechanic has its own, dedicated email address, named after the store's subdomain and located at A store at

  • Migrating templates from Shopify to Mechanic

    You can bring your templates over from Shopify's email notifications, or from Shopify's Order Printer app, in order to generate order-related material on-demand in Mechanic. This could look like

  • Task options

    Every task script has access to an options object, which contains all of the merchant-configurable options for a task. This object can be referenced in the task script, and in the task's online store