Hello Make.com Community,
I’m building a Make.com scenario to automate publishing Wavebid auctions as Shopify products (or updating them if they already exist), and I’m running into a few roadblocks. Any help or advice is hugely appreciated!
- Trigger: Wavebid “Save” action (manual button / webhook / polling)
- Fetch & Parse: Pull full auction JSON, extract title, description, images, dates, location, links, etc.
- Upsert Logic:
- Lookup via GraphQL for existing product by
custom.auction_id
- If found: REST PUT to update core product fields
- If not found: REST POST to create a new product
- Bulk Metafields: Single GraphQL
metafieldsSet
call to write ~15–20 custom fields in one shot
Current Challenges
- Mapping Variables:
- Injecting the real
ownerId
(GraphQL product GID) and each auction field (ID, location, links, dates, etc.) into themetafieldsSet
variables array
- Injecting the real
- Branch Wiring:
- Connecting both the “create” and “update” branches into the one bulk‑metafields module (or duplicating it) without mis‑routing
- GraphQL Errors:
- Fixing 400 responses caused by unmapped placeholders, stray commas, or malformed JSON
- Trigger Setup:
- Best practice for firing the scenario automatically from Wavebid’s “Save” (webhook vs. scheduled polling)
Looking for Help or Advice On
- GraphQL Mapping: Tips or examples for mapping Make.com module outputs into a
metafieldsSet
variables array - Branch Merging: How to best feed both update/create paths into a single GraphQL module (or manage duplicates cleanly)
- Wavebid Trigger: Recommendations for webhook implementation vs. polling for real‑time updates
Thanks in advance for any pointers, code snippets, or best‑practice advice!