Connect FLUF to Make

Use Make to look up stock, turn approved spreadsheet rows into FLUF drafts, or update listings from another tool. Start with a stock lookup before enabling any changes.

The native FLUF Connect app is published and available through its Make installation link. It has not yet been approved for Make’s public directory. Native event triggers are not included. The HTTP setup below remains available as an alternative.

What you need

  • A Make workspace.
  • A FLUF plan with API access. API access is not included in the trial. Changes need write access on both your plan and your token.
  • A personal access token from FLUF → Developers. Name it Make and start with read-only access for lookups.

Make and other apps in your scenario may charge separately. Keep your token in Make's credential storage, not in a spreadsheet, shared scenario, URL or AI prompt.

Install the native FLUF Connect app

  1. Open the FLUF Connect installation link while signed in to Make.
  2. Choose your Make organisation and install the app.
  3. Create a scenario and add FLUF Connect → Find a listing by SKU.
  4. Add a connection and paste your FLUF personal access token.
  5. Enter an exact SKU, run once and compare the result with FLUF. No matching listing produces no output bundle.

Pro supports read-only lookups; listing changes require Priority and a token with write access. Starter and the trial do not include this access. Make may charge separately.

Make a custom API call

Add FLUF Connect → Make an API call and select your saved connection. Enter /wp-json/fc/external/v1/make/listings as the URL, choose GET, and add sku with your SKU in Query String. The result contains Body, Headers and Status code.

Use relative FLUF automation paths, not full URLs. Authentication comes from your connection. For writes, use Content-Type: application/json and a JSON body; Make’s JSON builder helps escape mapped text correctly. The same plan and token permissions apply.

Alternative: look up a SKU with HTTP

  1. Open a new Make scenario and add HTTP → Make a request.
  2. Choose API key authentication. Store the credential in a header named Authorization, with value Bearer YOUR_TOKEN (one space after Bearer).
  3. Choose GET and enter https://fluf.io/wp-json/fc/external/v1/make/listings.
  4. Add the query parameter sku and enter an exact SKU from your FLUF inventory. Enable response parsing.
  5. Run once. FLUF returns an array: a matching listing, or an empty array if no match exists. Use an Iterator if the next module needs one bundle per listing.
  6. Compare the listing ID, price and quantity against FLUF. A quantity of zero is different from an unknown quantity.

Create a draft from an approved row

Add an approval filter before the request. Use a unique SKU and check FLUF for an existing match first. With a write-enabled token, send POST to https://fluf.io/wp-json/fc/external/v1/make/listings with a JSON body:

{"title":"Blue denim jacket","sku":"STOCK-001","price":25,"quantity":0}

Map the row's real values using Make's JSON body builder. The price uses your store currency. This creates a draft, not a marketplace listing. Save its returned id back to your sheet. If the request times out, look up the SKU before retrying. Review photos, marketplace details and quantity in FLUF before crosslisting.

Other actions

All paths below follow https://fluf.io/wp-json/fc/external/v1/make.

ActionMethod and pathInputs
Connected storesGET /channelsNone; each store includes a target
Update listingPATCH /listings/{id}JSON containing only changed title, description, price or quantity
CrosslistPOST /listings/{id}/crosslist{"channels":["ebay:123"]} using your own connected-store target
DelistPOST /listings/{id}/delist{"channels":["ebay"]}; keeps the FLUF record
Find orderGET /orders/{id}Query parameter channel, e.g. ebay
Mark shippedPOST /orders/{id}/shipJSON with channel, tracking_number, tracking_carrier

Crosslisting returns an accepted response while work continues. Check FLUF for the final result. Choose stores/channels from the module dropdowns or switch to mapping. Crosslisting uses a specific store target; delisting is selected by channel and cannot select only one of multiple stores on that channel.

Get an order expects the marketplace order reference (order_id), not the composite FLUF key. It reports an error if no order matches.

Shipping supports the existing Depop, eBay, Etsy and Temu single-order handlers; use genuine tracking for a designated test order before enabling your scenario.

Sale and stock events

Native Make event triggers are not available in this release. Developers can use FLUF webhooks with a receiver that verifies the delivery signature and timestamp before passing data to Make. Preserve event_id and deduplicate deliveries before sending messages or changing stock. Do not treat a secret webhook URL alone as signature verification.

Troubleshooting and disconnecting

  • 401: check the token, Bearer prefix and whether the token was revoked.
  • 403: check plan access and token write scope.
  • 404 on every route: the Make API backend has not been deployed.
  • 409 creating a draft: check for the existing SKU before retrying.
  • 429: wait for the returned Retry-After interval.
  • Crosslist accepted but not live: inspect the listing's status in FLUF.

Turn off the scenario, then revoke its token in FLUF → Developers. If you separately registered webhooks, delete those subscriptions too; revoking a token alone does not remove stored webhook subscriptions.

Back to Help Center