Search results for creating scheduled feeds

45 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 https://example.com/pages/feed. Tip: The data you generate can be

  • Can I send data to Google Sheets?

    There are two options: One uses the IMPORTDATA function to pull in data once, and the other offers a live push using either IFTTT or Zapier. Using IMPORTDATA Use Mechanic to publish a formatted CSV

  • Can I schedule tasks for the future?

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

  • 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

  • The "shopify" action

    Anything that Shopify allows developers to do, Mechanic lets you automate. This means that you can create, update, or delete nearly anything in your Shopify account. Here are some ideas: Tagging

  • 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

  • My task is failing because of a permissions problem. Why?

    If you're creating a new task, and writing a script to go with it, you might see an error like this when you start running it for the first time: Received a Shopify error (403): {"errors":"[API] This

  • 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

  • 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

    Mechanic comes with several ways to query Shopify for data (read more about these), and one of these involves Shopify's "bulk operations" feature. This feature allows apps like Mechanic to send

  • Pricing policy

    Our top priority is to create health for ourselves, and to give you the best tools we can for creating health for you. (We interpret "health" broadly: healthy transactions created in healthy business

  • Parent and child events

    The "event" action can be used to generate new events, to be run now or in the future. Events generated like this are considered children of the event responsible for those actions running in the

  • 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

  • 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 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

  • 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

  • All event topics

    Every task needs at least one event topic to "listen" for – when an event with a matching topic occurs, the task runs. Mechanic has many events that it can work with, giving you many options as you

  • An introduction to runs

    Everything has a run The work that Mechanic does is split into three classes: events, tasks, and actions. When each of these three classes are made ready to be performed, we call this a run. A run

  • 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

  • The task object

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

  • An introduction to tasks

    A Mechanic task is responsible for interpreting the events that occur, setting off any number of actions as a result. Mechanic offers a number of built-in tasks, which you can add to your account

  • Subscriptions

    Subscriptions control what events a task responds to. They have two pieces: The event topic Optionally, a time delay Event topics are plentiful. Time delays can be in minutes, hours, days, weeks,

  • 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. For developers Options "host"

  • The event object

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

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

    Short answer: almost certainly. :) Get in touch with us at team@usemechanic.com, and be prepared to do the following: Send events to Mechanic using a POST request, using a header to establish the

  • An introduction to events

    Everything happens, in e-commerce. Products are listed, customers arrive, orders are placed, everything occurs, and has data to go with it. In Mechanic, we call that whole wash of things events, and

  • Concurrency

    In general, Mechanic will run as many of your events/tasks/actions simultaneously as possible. This means that multiple tasks subscribing to the same event topic are very likely to execute

  • The "action" tag

    Because the ultimate purpose of a task is to generate actions, we offer a specialized Liquid tag as a quick shorthand for composing an action's JSON definition. This article is about composing action

  • 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

  • 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

  • Getting started with webhooks

    Webhooks are the nearly ubiquitous carriers of information to and from services across the internet - services like IFTTT, Zapier, Stripe, PayPal, JotForm, and countlessly more. You can use webhooks

  • Practicing writing tasks

    In our own internal education, we've found that the following exercises work particularly well. They're all in sequence – the task to create for each subsequent exercise modifies the code you wrote

  • 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

  • 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

  • How can I update existing metafields?

    Metafields may be managed using the "shopify" action, whether you use REST or GraphQL. While metafields can be uniquely referenced for a resource, using their namespace and key, any updates to them

  • 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,

  • 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

  • Scripts

    Mechanic turns Liquid from a templating language, into a programming language. By nature, this document is basically wholly for developers. But – and we mean this – we're all about education. If

  • Welcome!

    I'm glad you're here. :) I'm Isaac, and I built Mechanic. My goals here are simple: To let you solve all your automation needs with one tool, instead of having to use a million different apps. To

  • How do I add or remove tags for Shopify resources?

    Merchants commonly use Mechanic for adding or removing tags from customers, orders, products, and other Shopify resources. When writing your task scripts, use a "shopify" action to add or remove tags

  • Preview actions

    Generally speaking, tasks only run in response to events – an order being created, a "Run task" button being pressed, etc. However, Mechanic does preview runs of each task as well, for two purposes:

  • 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