About

Summary Build a production-grade pipeline between Shopify and Airtable using Make. Ingest Shopify webhooks into Airtable with HMAC verification and idempotency. Sync back from Airtable to Shopify using metaobjects, metafields, and optional theme JSON assets so the storefront reflects vendors, market occurrences, and product availability per postcode and date. Ship it with logging, alerts, retries, and a short runbook. Objectives Shopify to Airtable ingest via one Make webhook URL with HMAC check and idempotency. Airtable to Shopify sync for Vendor and Market Occurrence metaobjects, plus Product metafields or full product sync. Operational hardening: rate-limit handling, retries, alerts, logs, and easy replay. Scope of work S1 — Webhook ingest in Make using one URL Shopify topics to enable now, all pointing to the same Make webhook URL orders create or orders paid refunds create optional fulfillments create and or fulfillments update optional customers create and customers update optional later if needed products update and or inventory levels update Make flow front end steps common to all topics Webhooks module named orders in Advanced settings enable Get request headers Yes Advanced settings enable JSON pass through Yes Tools Set variable Variable name calculatedHMAC Value uses the Make hmac function as follows hmac left parenthesis double quote sha256 double quote semicolon RAW BODY FROM WEBHOOK semicolon SHOPIFY SIGNING SECRET semicolon double quote base64 double quote right parenthesis Secret rule If webhooks were created in Settings then Notifications then Webhooks use the Signing secret shown on that page. If webhooks were created inside a custom app use that app s API secret key. Filter Verify HMAC Left side the calculatedHMAC variable Operator equals Right side header x shopify hmac sha256 from the webhook module Data store idempotency Create a Make Data store named ofm shopify webhooks seen Structure one field named received at type Date or Text Get a record using key header x shopify webhook id Filter only continue if the returned value is empty Set a record with key header x shopify webhook id and value received at set to Make function now Flow control Router Route by header x shopify topic Example filters orders slash create goes to Orders route refunds slash create goes to Refunds route fulfillments slash create or update goes to Fulfillments route customers slash create or update goes to Customers route Webhook response Successful routes return HTTP 200 with a short OK body Add a failure path for HMAC mismatch that returns HTTP 401 Airtable mapping minimums Orders table order id name created at currency subtotal shipping tax discounts total financial status fulfillment status tags note customer id email phone full shipping and billing addresses webhook topic webhook id received at timestamp Order Line Items table one row per line order id link to Orders line item id product id variant id sku title variant title quantity price vendor reference via product vendor or metafield taxes and discounts if present Customers table customer id email first name last name phone total orders total spent if present Refunds table optional refund id order id created at currency refunded amounts refund line items Fulfillments table optional fulfillment id order id status tracking company number and url affected line items Webhook Logs table webhook id topic success or failure error message if any timestamp S2 — Airtable to Shopify Vendors as metaobjects Trigger Airtable Vendors table on change watch plus nightly sweep Use Shopify Admin API GraphQL over HTTP in Make Ensure metaobject definition for type vendor exists with fields handle name short description location logo categories active markets attended zones served attendance next dates Upsert metaobject entries for each vendor and write the returned metaobject id back to Airtable Handle image upload for logo if stored in Airtable S3 — Airtable to Shopify Market Occurrences as metaobjects Trigger Airtable Market Occurrences generated by your recurrence logic Upsert metaobject entries for each occurrence with market id or name date location open hours list of attending vendor metaobject ids status S4 — Products and availability Choose one pattern; confirm in kickoff. Pattern A Airtable is authoritative Trigger Airtable Products changes Create or update Shopify Products via Admin API Set metafields needed by the frontend ofm dot vendor id ofm dot market occurrence ids list ofm dot zones served Inventory handling per agreement either set levels or use continue selling when out of stock Pattern B Shopify is authoritative Mirror changes into Airtable using products update webhook Only write required metafields or collections for the UI S5 — Optional nightly theme JSON assets for fast UI Build compact JSON files from Airtable such as zones to vendor ids occurrence to vendors or products Upload to theme assets via Admin API Frontend fetches these assets for postcode filtering S6 — Distance and delivery enrichment already prototyped Use Google Distance Matrix to compute closest market and delivery radius Write back to Airtable fields used by UI and routing Note: So that I know you have read the full description. Add the word TIGER to the beginning of your proposal. S7 — Operational hardening Rate limit handling and retries with backoff for HTTP 429 Optional queue pattern acknowledge webhook quickly then process heavy work asynchronously Alerts on failures email or Slack Small runbook for replaying webhooks rotating secrets adding a new topic exporting Make blueprints Technical requirements Strong Make experience Webhooks Data store Routers HTTP and GraphQL modules Airtable modules Shopify Admin API GraphQL preferred Metaobjects Metafields Products and Inventory Airtable schema linking and id handling HMAC verification and idempotency patterns Access I will provide Shopify admin and or custom app access with credentials Make organization access Airtable base access Google Maps key if needed Draft theme id do not touch live theme without approval Acceptance criteria testable HMAC verification rejects tampered payloads 401 path hit confirmed Idempotency same webhook id never processes twice Orders route creates rows in Airtable for Orders Line Items Customer with correct links and totals Refunds Fulfillments Customers routes if enabled create or update rows appropriately Vendor and Market Occurrence metaobjects exist and update in Shopify ids written back to Airtable Products carry required metafields or are created updated per chosen pattern Optional JSON assets available in the theme and readable by the UI Webhook response within five seconds for the ingest path or queue pattern implemented Alerts fire on induced error Runbook delivered Deliverables All Make scenarios built and exported as blueprints Field mapping document Airtable to Shopify and vice versa Secrets and connections noted with rotation steps Runbook SOP for maintenance Optional Postman collection of GraphQL calls used Milestones Webhook ingest live with HMAC idempotency Orders route mapped Refunds Fulfillments Customers routes live if in scope Vendor and Market Occurrence metaobjects upsert live Product metafields or product sync live Optional theme JSON assets plus ops hardening and runbook handover Proposal requirements Two or three similar Shopify Make Airtable projects Your plan for HMAC idempotency router and rate limits Whether you prefer GraphQL for metaobjects and why Any suggested Airtable field tweaks to simplify sync High-level timeline and assumptions Notes Use latest stable Shopify API version Do not expose secrets in screenshots Build and test against a draft theme Keep it modular and documented so I can maintain it after handover