AccountCraft Journal
Shopify Flow Customer Updates: Triggers and Workarounds
Shopify Flow has no customer-updated trigger. See which customer triggers exist, how to react to profile changes, and when a webhook is the better tool.

Shopify Flow has no “Customer updated” trigger. If you want a workflow to start whenever someone edits their profile, you have to use a nearby trigger, a scheduled check or a webhook. The cleaner route is to design the change so it produces an event Flow can see, and to keep the data it changes in one place inside Shopify. This guide covers which customer triggers exist, how to update customer records from Flow, when to use a webhook, and how customer-editable fields in New Customer Accounts fit in.
TL;DR
- Shopify’s official trigger reference lists no “Customer updated” trigger. Flow can start on customer created, deleted, account enabled or disabled, segment changes, tags added or removed, and a few others.
- To change customer data from Flow, use the Update customer metafield action, or the Send Admin API request action for fields that have no native action.
- For true field-level change detection, developers can subscribe to Shopify’s customer event topic, which reports which fields changed.
- When customers edit their own data in New Customer Accounts, store it in customer metafields so Flow, segments and your admin all read the same values.
Table of Contents
- What Flow can and cannot start from a customer change
- Four ways to react to a customer change
- Updating customer data from Flow
- When a webhook is the better tool
- Protected customer data and what can fail
- Let customers make the change, then let Flow see it
- Consent changes need extra care
- Choosing the right approach
- Perspective
- Build customer-editable accounts with AccountCraft
- FAQ
- Sources
What Flow can and cannot start from a customer change
Flow starts workflows from triggers. For customers, Shopify’s trigger reference lists these:
- Customer created
- Customer deleted
- Customer account enabled and disabled
- Customer joined segment (and the matching left-segment event)
- Customer abandons checkout
- Customer payment method created, revoked or updated
- Customer subscribed to email marketing
- Customer tags added
- Customer tags removed
There is no trigger for “customer changed their phone number” or “customer edited a metafield.” A merchant asking about this in a Shopify community thread got the same answer: the underlying event does not say what changed, so Flow cannot tell that a metafield was edited in the way you would want. Treat that thread as background. The official trigger list above is what you build against.
A common mistake is reaching for Customer created. Per Shopify’s Customer created page, it fires when a new customer places an order or a profile is created manually. Editing an existing profile does not activate it. A workflow built on it will look correct in testing with a new customer and then never run for your existing ones.
Four ways to react to a customer change
You have four practical patterns. Pick the one that matches how precise the reaction needs to be.

1. Use a tag as the signal
The Customer tags added and Customer tags removed triggers are the closest thing Flow has to a change event. If your process already adds a tag when something happens (for example, a customer is flagged as wholesale), you can start a workflow from that tag. The downside is that something has to apply the tag first, so this works for status changes you control, not for free-form profile edits.
2. Use segments
Customer joined segment and Customer left segment fire when someone starts or stops matching a segment you defined. If your trigger condition can be expressed as a segment filter, such as a metafield value or a tag, segments give you an event without any code. Open Shopify admin, go to Customers > Segments, build the filter, then in Apps > Flow start a workflow from the segment trigger.
One timing caveat: some customer statistics are calculated after the fact. A Shopify staff reply in the developer community says fields such as RFM group and predicted spend tier are calculated asynchronously after an order, with latency from 15 minutes to 24 hours. Do not build a workflow that expects those values the instant an order lands.
3. Poll on a schedule
When no trigger exists, Shopify’s documentation on schedules, Get data and looping points to the Scheduled time trigger combined with Get data actions. Scheduled workflows can run as often as every 10 minutes, and Get data returns filtered lists of up to 100 items. That is enough for most stores to find recently changed customers, but it means your reaction runs on a delay rather than the moment of the edit.
4. Subscribe to a webhook
If you need the exact field that changed, the tool is a webhook, not Flow. More on that below.
Updating customer data from Flow
Reacting is half the job. Often you want Flow to write data back.
Update customer metafield. Shopify’s Update customer metafield action adds a metafield to the customer that triggered the workflow, or updates the existing one. It needs a Customer ID, which is set by default, and it works with 15 listed triggers. Use it to stamp a value such as a loyalty tier or a preferred contact method.
Update customer note and tags. The Customer created page lists add and remove tag actions and an Update customer note action as available follow-ups. Tags are the right output when you want another workflow, a segment, or a rule to pick up the change.
Send Admin API request. For anything without a native action, Shopify’s Send Admin API request action can call most GraphQL Admin API mutations, including customerUpdate. The documentation’s examples update a customer’s tax-exempt status and locale using the customer’s GID, which is the global ID Shopify uses for the record. It does not support queries, deprecated mutations or async mutations, and the staff member enabling the workflow needs matching store permissions. Shopify’s changelog announcement from June 2024 shows the same pattern with a locale update.
A practical setup in the admin:
- Go to Apps > Flow > Create workflow.
- Choose a trigger from the list above, for example Customer tags added.
- Add a condition if the workflow should only run for certain tags or customers.
- Add the Update customer metafield action and pick the metafield definition.
- Turn the workflow on, then test it with a real customer record before relying on it.
When a webhook is the better tool
Flow is built for merchants. Webhooks are built for developers who need every change, delivered to their own server. Shopify’s Customer event topic supports create, update and delete actions with field-level triggers. Parent triggers receive all nested field changes, while narrower ones, such as address triggers, let an app limit events to the fields it cares about. Payloads include fields_changed, so you can see what was edited. You subscribe in shopify.app.toml with the actions, triggers, a URI and a GraphQL query that shapes the payload. Deduplicate deliveries with the shopify-webhook-id header.
The older REST topic for customer changes is customers/update. Shopify’s community guidance says REST is legacy with no new functionality, and that subscribing through GraphQL or the app configuration file is the recommended path, as noted in the developer community answer.
If you do run an endpoint, an integration guide from ArcIntegrate documents the habits that keep it reliable:
- Verify the
X-Shopify-Hmac-SHA256header on every request. - Return HTTP 200 quickly, within the 5-second timeout, and process the payload asynchronously.
- Expect Shopify to retry failed deliveries up to 19 times over 48 hours.
If your team has no one to write and maintain that endpoint, hiring a Shopify developer is the usual route. For many stores, though, a tag, a segment or a scheduled workflow gets the same result with no server.
Protected customer data and what can fail
Customer updates touch personal data, so permissions matter. Shopify’s protected customer data guide lists name, address, email and phone as protected fields that an app must request individually. Responses include only approved fields, unapproved fields can be redacted, and a request for an unapproved GraphQL type returns HTTP 200 with an error in the errors hash. In practice, that means a workflow or integration can look successful while returning empty values. Check the response body, not only the status code.
The same page sets out rules for apps handling this data, including processing only the minimum necessary personal data, limiting use to stated purposes, respecting customer consent and opt-outs, and encrypting data in transit and at rest. If your automation passes customer data to another system, keep it to the fields that system needs.
Let customers make the change, then let Flow see it
Here is the gap most merchants hit. Customers change their own details (preferred size, pet name, delivery notes, communication choices), and you want your automations to respond. If those details live in a spreadsheet, a form app or a separate database, Flow cannot reach them. If they live in customer metafields, everything in Shopify can read them: segments, Flow actions, the admin and your storefront logic.
This is what AccountCraft does inside New Customer Accounts. It gives merchants a visual Block Builder with 14 block types, including an update form and single field blocks bound to customer metafields, record lists for repeatable data such as pets or vehicles, a wishlist, and SMS and privacy consent blocks. It uses official Shopify Customer Account UI Extensions, so there is no code and no theme change, and customer data stays in Shopify. There is no separate customer database.
That design suits the patterns above:
- Segments on metafields. Because fields are bound to customer metafields, you can build a segment on a metafield value and use the segment-joined trigger in Flow.
- Conditional rendering. AccountCraft can show or hide blocks by customer tag, metafield, market, B2B status and account age, so a tag your Flow workflow applies can change what the customer sees in their account.
- Scheduled review. A scheduled workflow with Get data can find customers matching a metafield filter and act on them.
For setup detail, see our guides on custom fields in Shopify accounts and on letting customers edit customer metafields. If your goal is collecting preferences directly from customers, our piece on zero-party data in customer accounts shows the fields to start with.
Consent changes need extra care
When the “update” is a consent choice, treat it as a record of what the customer did, not something an automation should rewrite. Shopify’s Customer Privacy API says to record consent only on visitor interaction, such as accepting a cookie banner, using the supported purposes of Preferences, Analytics and Marketing. It also warns developers never to read or modify Shopify cookies directly. Its allowed methods combine merchant settings, visitor location and consent, and in regions configured to require consent, non-essential purposes are not allowed by default.

So a Flow workflow should react to consent, for example by branching on whether a customer subscribed to email marketing, rather than writing consent values on the customer’s behalf. AccountCraft’s privacy consent and SMS consent blocks are designed to help you collect, record and honor customer consent through Shopify’s customer privacy APIs. Compliance remains your responsibility as the merchant, and questions about your legal obligations belong with your lawyer. For the practical side, read our guides on account consent without code, GDPR consent apps and consent expiry for EU stores.
Choosing the right approach
| Goal | Best fit | Notes |
|---|---|---|
| Run something when a tag changes | Customer tags added or removed trigger | Something must apply the tag first |
| Run something when a customer matches a condition | Customer joined segment trigger | Define the condition as a segment filter |
| Catch edits with no native trigger | Scheduled time trigger plus Get data | Delay of at least 10 minutes, up to 100 items per query |
| Write a value back to the customer | Update customer metafield action | Needs a Customer ID from the trigger |
| Change a field with no native action | Send Admin API request | Mutations only, with matching permissions |
| Know exactly which field changed | Customer webhook with fields_changed | Requires a developer and an endpoint |
Perspective
We built AccountCraft around one idea: the data a customer gives you should live where the rest of your store’s logic already lives. Merchants often ask us how to trigger a Flow workflow when a customer updates their profile. Behind that question is usually a data problem. The values sit in a tool Shopify cannot see, so no trigger can ever fire on them.
When fields are bound to customer metafields and edited through New Customer Accounts, there is one source of truth. Segments, Flow, conditional blocks and your admin all read the same value, and nothing is copied into a second database that can drift out of sync. We use official Shopify APIs and Customer Account UI Extensions for that reason: your account pages stay inside the platform, and you stay in control of the data.
Our advice is to design the workflow around the signal Shopify gives you, a tag, a segment or a metafield, and give customers a clear place in their account to maintain it themselves. Fewer manual updates, fewer stale records, and consent handled where the customer can see it.
Ivan Signorile
Build customer-editable accounts with AccountCraft
AccountCraft has a free plan, and the paid Pro and Plus plans are billed through Shopify. Check the Shopify App Store listing for current pricing. With the free plan you can start building account pages with the Block Builder, add editable fields tied to customer metafields, and then point your Flow workflows and segments at those same metafields.

Install AccountCraft free from the Shopify App Store, or see the plans on the AccountCraft site. If you are comparing what is possible, our overview of customer data apps and the 14 blocks lists each block type.
FAQ
Does Shopify Flow have a customer updated trigger?
No. Shopify’s trigger reference lists customer created, deleted, account enabled and disabled, segment, tag and a few other triggers, but not a general customer-updated one. Use tags, segments or a scheduled workflow to approximate it.
Does the Customer created trigger fire when a profile is edited?
No. It fires when a new customer places an order or a profile is created manually. Editing an existing customer does not start the workflow.
How do I get a Shopify webhook for customer updates?
Subscribe to the customer event topic in shopify.app.toml with the update action and the fields you need. Verify the HMAC header, return HTTP 200 quickly and process the payload asynchronously. The payload’s fields_changed shows what was edited.
Can Flow update a customer’s information?
Yes. The Update customer metafield action writes metafields, and the Send Admin API request action can call mutations such as customerUpdate for fields without a native action. The person enabling the workflow needs the matching store permissions.
Sources
- Triggers in Shopify Flow, Shopify Help Center
- Customer created trigger, Shopify Help Center
- Update customer metafield action, Shopify Help Center
- Send Admin API request action, Shopify Help Center
- Flow: New action to Send Admin API request, Shopify changelog
- Schedules, Get data, and looping in Flow, Shopify Help Center
- Customer event topic, shopify.dev
- Connect Shopify with HubSpot, ArcIntegrate
- Could not find the webhook topic customer.tags_added, Shopify community
- Tracking Customer Statistics in GraphQL API, Shopify community
- Work with protected customer data, shopify.dev
- Customer Privacy API, shopify.dev