Search results for can i sending values to customer fields

130 articles found

  • Can I send values to Customer Fields?

    To update a customer record in the Customer Fields app, use an "http" action that looks something like this: {% action "http" %} { "method": "put", "url":

  • Can I send events to Klaviyo?

    To send an event to Klaviyo, we use the "http" action. Your task script might look something like this: {% assign klaviyo_data = hash %} {% assign klaviyo_data["token"] =

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

  • Sending email from a custom address

    By default, Mechanic sends your mail from an address built from your Shopify account name. If your store is located at fantastic.myshopify.com, for example, Mechanic will send mail from

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

  • 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

  • Can I use Mechanic to publish or unpublish to different sales channels?

    Shopify has approved Mechanic for publishablePublish and publishableUnpublish, these being the APIs used for adding and removing products to different sales channels. If you've got a need for this,

  • 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

  • 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. Details you should know ahead of time: All event ingress works via POST requests to an endpoint that we supply,

  • The "email" action

    Email runs everything. Mechanic sends email. So long as you're sending transactional email only, you're covered. 👌 Read more: What kind of email can I send with Mechanic? Did you know you can

  • 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

  • How do marketing preferences work with Mechanic?

    Mechanic does not enforce a customer's marketing preferences on your behalf. It is your responsibility to respect their preference, as recorded in Shopify, and to give the customer an opportunity to

  • 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 re-send order confirmation emails with Mechanic?

    As of this writing, Shopify doesn't have a simple API for re-sending order confirmation emails. (If this is important to you, send an email to support@shopify.com and let the folks there know that

  • Can I retry a task? Or an action?

    For task runs, Mechanic will make available a "Retry" button... ... if the task run itself failed (due to a Liquid error, an API error while reading data, or something else) ... or, if the task run

  • Can I dynamically set or change order IDs?

    While Shopify does allow formatting your order IDs, and while you can change that format whenever you wish, the order ID formatting rules apply to all incoming orders. And, once set, an order ID

  • Can I replace Shopify's order emails with Mechanic?

    As of December 2018, only Shopify Plus shop-owners are able to disable Shopify's own order notification emails. You can supplement these with Mechanic emails for confirmation and/or fulfillment, but

  • Where can I see what's changed in Mechanic?

    We record each update to the Mechanic platform in our changelog, available at changelog.usemechanic.com. If you've got questions about a change, just use the chat button in the corner. :)

  • Can I use web fonts with generated PDFs?

    Absolutely! We've put together a demonstration task that allows you to see this in action, using a typeface from Google Fonts: Demonstration: Web fonts in PDFs

  • What kind of email can I send with Mechanic?

    Under the hood, Mechanic uses Postmark to provide email services – both incoming and outgoing. We inherit a requirement of theirs, that you only send transactional messages, directly resulting from

  • How can I control the run order of actions?

    For tasks that generate multiple actions, Mechanic's run system doesn't guarantee the order in which those actions will be run. To control action run order yourself, render one action at a time and

  • Can I run tasks when orders are printed in Order Printer?

    As of this writing, Shopify's Order Printer app doesn't support tagging, or webhooks, or any other method of recording when an order has been printed. This means that apps like Mechanic have no way

  • 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: {%

  • Can I set up a task based on which staff member did something?

    For orders and draft orders, use these tasks: Auto-tag new orders by staff member – allows you to configure certain tags to be applied based on certain staff members Auto-tag orders by originating

  • Add an email template

    Sending email with Mechanic, using the "email" action? Use templates to make sure your emails match your brand. Don't forget, you can also send email from your store's domain! Instructions 1.

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

  • 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

  • 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

  • The "files" action

    The "files" action generates files (see Generating files), and makes them available at a temporary URL. This is most useful in concert with the mechanic/actions/perform topic (see Responding to

  • 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

  • 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. The "shopify" action has three

  • The options object

    Only available within a task, the options object contains all values provided by merchants while configuring the task. Each option value is itself parsed for Liquid. The options variable is not

  • How do I send images with my emails?

    Attaching images The "email" action supports attaching anything that you can express using JSON. (The rest of this article will assume you're familiar with this action.) If you happen to have your

  • 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

  • How long can tasks run?

    Most tasks run very quickly (less than a second, on average), but some tasks take much longer. Naturally, tasks that make many requests to Shopify (or use large volumes of data) can take a while. We

  • Why are my tasks delayed or not running?

    In general, there are two reasons why a task might be delayed, or might not be appearing to run: Shopify† is delayed in sending notifications to Mechanic Your Mechanic account is experiencing a delay

  • Writing a high-quality task

    Isaac here. I've written a lot of tasks. :) Between tasks pulled from our library shelf and tasks created by other developers, we've got thousands of them running at this moment. Here are some best

  • 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 Mechanic work with transfers and incoming inventory?

    As of 2019-03-11, Shopify does not offer third-party apps any access to their Transfers feature, which includes incoming inventory figures. If this is important to you, reach out to Shopify directly

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

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

    This object allows you to iterate through a resource's metafields, or to access a single metafield directly by performing lookups using a namespace and then a key. How to access it To retrieve a list

  • The cache object

    The cache object is used for retrieving values stored in the shop's Mechanic cache. Values are set exclusively via the cache action. How to access it Use {{ cache["cache_key"] }} in any task script

  • 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

  • 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

  • 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

  • An introduction to actions

    If events are where Mechanic begins, actions are where it concludes (with tasks hanging out in the middle). A task can run one action every time it runs, or it might run many actions – it all depends

  • 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

  • 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 "cache" action

    Backed by Redis, Mechanic offers a simple key/value cache store that you can use in your task scripts. This cache is not intended for long-term storage; all values expire a maximum of 60 days from