Shopify connector

The Shopify connector lets a Neblex workflow or agent treat a store as a source and a destination: push paid orders into an ERP, keep inventory in step with a warehouse system, enrich and route customers, and answer questions about orders.

• Works against production stores and development stores, one connection each
• Uses the Shopify Admin REST API, version 2026-07, with 367 operations
• A Webhook trigger set to Auto Register With Shopify subscribes to the topics you pick when the flow is activated, and removes them when it is turned off
• One connector powers deterministic workflows, agent tool calls, and inventory and order sync jobs, all in the same run history

The three jobs this connector is picked for most often, and what each one gets you.

• Get orders into the ERP cleanly. Each paid order arrives by webhook and becomes a sales order, with the customer matched and the ERP order number stored on the Shopify order.
• Keep inventory honest across channels. A scheduled flow pushes stock levels from the warehouse or ERP to each Shopify location, so the store does not oversell.
• Feed marketing the events it needs. Orders, refunds, and customer changes reach your marketing tools with clean, deduplicated customer records.

A real flow e-commerce ops teams turn on first, with the actual step-level detail.

Paid Shopify order to a NetSuite sales order, with a fraud hold

On orders/paid, Neblex creates or matches the customer, raises the sales order, and sends anything Shopify flags as high risk to a person before it posts.

1. 1
   Trigger: a Webhook trigger with Auto Register With Shopify for orders/paid, carrying the order, line items, customer, and addresses.
2. 2
   Risk check: read the order's risks. If the recommendation is cancel or investigate, a Wait for form step sends a reviewer the order link, and the flow continues only when they release it.
3. 3
   Customer: Upsert by external id on the NetSuite customer, keyed on the Shopify customer ID, mapping customer.email → email, customer.first_name → first name, customer.last_name → last name, shipping_address.country_code → billing country.
4. 4
   Order: Upsert a sales order keyed on the Shopify order ID, mapping order.name → otherRefNum, and each line to an item line with line.sku → item, line.quantity → quantity, line.price → rate, plus a shipping line from total_shipping_price_set.
5. 5
   Guard: if any line.sku does not match an ERP item, send the order to a reviewer rather than creating a partial order.
6. 6
   Close the loop: write the ERP order number to a Shopify order metafield custom.erp_order_number, so support can see it on the order page.

Common patterns other teams start from with this connector.

• Order to ERP. Paid orders become NetSuite sales orders, new shoppers become customers, and fulfillment status flows back to the store. (E-commerce ops)
• Store to email and SMS. Orders, refunds, and customer changes reach Klaviyo with enriched, deduplicated customer records. (Marketing)
• Orders to the books. Daily order and payout totals sync into QuickBooks as sales receipts and deposits, reconciled to the payout. (SMB finance)
• Store data to the warehouse. Order, product, and customer history loads into Snowflake by paging the list operations, then Shopify webhooks keep it current. (Data)

Admin REST API resources are supported for read and write. Metafields extend any of them with your own structured data.

Commonly used resources

Product, Variant, Collection, Order, Draft Order, Customer, Inventory Item, Inventory Level, Location, Fulfillment, Fulfillment Order, Refund, Transaction, Payout, Discount Code, Price Rule, Metafield

Metafields on products, orders, customers, and variants are read and written through the Metafield operations, so a workflow can store an ERP ID or a sync status directly on the Shopify record.

The connection uses an Admin API access token from your store, so it can only read and write the resources that token's scopes allow.

• Admin API access token. The connection holds your store name and the token, stored encrypted. Scopes are granted per resource, for example read_orders, write_inventory.
• Scope-limited access. A token without write_products cannot change the catalog. Grant the narrowest scope set each flow needs.
• Webhook registration. With Auto Register With Shopify, the webhook subscription is created and removed with the flow, so no stale subscriptions are left behind.
• Run history. Every run shows each step's status and errors; record data from successful runs is kept when the flow is set to keep run data for replay.

The shape of Shopify's limits, as published at the time of writing. Verify the exact figures for your plan; they change without notice.

• The REST Admin API allows about 2 requests per second with a 40-request burst, doubled on Shopify Plus
• Rate-limited reads are retried with backoff, honoring Shopify's retry signal; creates are POST calls, so turn on Retry on failure or an idempotency key for those steps
• List endpoints page through results, so read a large catalog or long order history in pages and process it in chunks
• Webhooks are retried over roughly 48 hours across 19 attempts, so a flow must be safe to run twice on the same event
• Order, fulfillment, and inventory writes follow Shopify's own state rules, for example an unpaid order cannot be fulfilled, and the step shows Shopify's rejection rather than forcing it