Skip to main content
All CollectionsAutomating Shopify
Seven Shopify Flow Tips for Non-Developers
Seven Shopify Flow Tips for Non-Developers

Some powerful techniques to help automate common merchant tasks in Shopify Admin

Updated over a week ago

Shopify Flow is a powerful automation tool that allows Shopify merchants to create workflows that automate various tasks across their store. It’s particularly valuable for non-developers, as it offers a no-code solution to handle repetitive or complex tasks. By connecting Shopify Flow with apps like Admin Buttons by Even Better, merchants can build custom workflows that are triggered by specific actions, such as clicking a button on an order or product detail page in Admin.

This guide will walk you through seven essential tips for using Shopify Flow effectively, even if you don’t have a technical background. These tips will help you make the most of Flow’s capabilities to streamline your store’s operations.

1. Always Start with the Log Output Action

When creating a workflow in Shopify Flow, it’s important to understand how data is being passed through each step. The Log Output action is a great way to keep track of the information your workflow is processing:

  • This action logs all variables from the trigger into the run details.

  • By logging your outputs, you can easily debug your workflow and ensure the right data is being used in the next steps. It’s especially useful when you’re building or customizing a flow and need to verify what data is available.

Use it to explore the data available in triggers or to figure out how to parse data with Liquid.

2. Understand What’s in the Trigger

Speaking of triggers, each trigger in Shopify Flow passes through different data, depending on what app or event is connected. Understanding the data your trigger provides is key to building effective workflows.

  • For example, the Even Better Admin Buttons app passes through a combination of button data, form inputs, and relevant object IDs (like order or product IDs).

  • You can view the variables available in a trigger by using the Add Variable step in Shopify Flow, which allows you to inspect and select the data you need for the next steps.

This practice ensures that your automations are connected to the right information, allowing your workflows to be more precise and relevant.

3. Tie the Event and Workflow Together Tightly

For workflows to execute efficiently, it’s crucial to link the trigger event and the actions that follow closely. This can be done by adding conditions that check for specific values before progressing:

  • For instance, you can use custom attributes or form data to confirm that a particular button click or input was the right one to trigger the automation.

  • You can create conditions that compare these custom attributes to expected values before continuing with the workflow.

This method ensures that only the relevant events trigger specific workflows, preventing unwanted or incorrect actions.

4. Parse Inputs with Run Code (Even If You’re Not a Coder)

The Run Code action in Shopify Flow allows you to process data using simple scripts. While it may seem technical, you can easily use it to parse inputs from triggers like form responses:

  • For example, you can write a script that extracts and organizes key variables from form inputs, making them easier to use in the next steps of your workflow.

  • This action saves you from having to use Liquid code, providing a more straightforward way to manage variables.

Even if you’re not a developer, this step allows you to handle data more effectively, making your workflows more robust.

5. A Little Liquid Goes a Long Way

Liquid, Shopify’s templating language, can be a powerful tool within Shopify Flow. It allows you to manipulate data in a more flexible way:

For example, you can use Liquid to filter through product tags or to manage complex sets of data that require sorting or organization.

  • By writing a clean Liquid block in your workflow, you can process inputs or existing data before passing the results to Shopify actions, such as updating a product or order.

This is especially helpful for handling more complex workflows, where simple conditions or actions may not be enough to get the job done.

6. Use the Get Object Data Action for Deeper Access

Sometimes, a trigger provides only a basic piece of data, such as an ID, but you may need additional details to complete your automation. This is where the Get Object Data action comes in:

For example, if your form passes through a collection ID, you can’t directly work with that ID. First, you need to pull the collection data using the Get Collection Data action.

  • Once you have the full collection object, you can use it to perform actions on the individual products within that collection.

The Get Object Data action can be used for other objects as well, such as products or orders, giving you more control and flexibility in your workflows.

7. The Send Admin API Request Action is a Buzzsaw

The Send Admin API Request action is one of the most powerful steps in Shopify Flow, but it requires careful handling. When used incorrectly, it can overwrite important data:

For example, when updating a draft order, if you’re adding or modifying line items, you need to ensure that all line items—including custom ones—are passed through with the draftOrderUpdate API request.

  • Failing to include all the necessary details could result in data loss, such as missing line items in the final order.

This action provides great flexibility for interacting with Shopify’s backend but should be used cautiously to avoid unintended consequences.

By following these seven tips, you can unlock the full potential of Shopify Flow without needing to write complex code. Whether you’re logging outputs, parsing inputs, or working with Liquid, these strategies will help you automate your store’s workflows more efficiently.

To get started, you can explore the Shopify Flow templates available for the Even Better Admin Buttons app and tailor them to suit your store’s specific needs.

Did this answer your question?