Connect FLUF to n8n

FLUF Connect is verified by n8n. Build workflows that move sales into a spreadsheet, turn reviewed stock rows into drafts, or let an AI assistant look up your inventory.

n8n is a workflow builder: choose what starts a workflow, then connect the steps you want it to perform. You control when it runs and which accounts it can access.

Browse all eight n8n workflow templates, or watch the short seller demonstration for an overview, then follow the steps below.

What you need

• An n8n workspace that allows the FLUF Connect node.
• A paid FLUF plan with API access, and a personal access token. Read-only access supports inventory lookups. Event-triggered workflows and actions that create or change listings require write access on your plan and token. API access is not included in the trial.
• Your own credentials for other apps used by a template, such as Google Sheets or OpenAI. Those services may charge separately.
• For sale and stock triggers, n8n must have a public HTTPS webhook address.

Install and connect

1. Open FLUF → Channels → Automate and choose Set up n8n, or open n8n setup directly.
2. In n8n's node picker, search for FLUF Connect and install the verified node if offered. If it is not listed, ask your workspace administrator about community-node availability. On self-hosted n8n, open Settings → Community nodes → Install and enter n8n-nodes-fluf-connect. The official npm package identifies the publisher and source code.
3. In FLUF → Developers, create a personal access token named n8n. Use read-only access for inventory lookups; enable writes only for workflows that need them. Copy the token when shown.
4. In n8n, create a FLUF Connect API credential, paste the token and test the connection. Select it on each FLUF node in your workflow.
5. Download a template below. In n8n, open a new workflow and choose Import from File from its menu. Select your credentials and complete the app-specific setup before running it. Templates are supplied inactive and contain no account credentials.

Never paste your FLUF token into an AI prompt, spreadsheet or shared workflow file.

Template 1: keep a sales ledger in Google Sheets

Download the sales ledger workflow

For sellers: keep a sale-by-sale record alongside your bookkeeping. For agencies: build a separate reporting sheet for each client's account.

1. Create a Google spreadsheet with a tab named Sales. Add these headers in row 1, one per cell: event_id, order_id, channel, connection_id, sold_at, order_total, currency, item_count, items.
2. Open Save sale in Sheets, select your Google credential and paste the spreadsheet ID (the part between /d/ and /edit in its URL).
3. Select your FLUF credential on New FLUF sale. Listen for a test event, then use a real sale event from your account to check the row. The template rejects incomplete sample events.
4. Check the order total and currency against the source order. This is a sales ledger, not a profit calculation: it does not deduct fees, tax or stock costs. Mixed currencies must be reported separately.
5. Publish or activate the workflow when ready.

The template updates rows by event_id to handle repeated deliveries. Google Sheets does not enforce unique keys: simultaneous deliveries can still create duplicate rows. For strict deduplication or high-volume reporting, use a database with a unique event ID. Avoid adding payments or repeated customer messages without a stronger duplicate check.

Template 2: turn approved spreadsheet rows into FLUF drafts

Download the approved stock workflow

For sellers: prepare stock with a helper and review it before import. For creators and agencies: give a client a simple approval sheet while you build the workflow behind it.

1. Create a Stock tab with these headers, one per cell: sku, title, price, approved, fluf_listing_id, import_status.
2. Add one test row with a unique SKU, a title and a positive numeric price in your FLUF store currency. Enter yes under approved. Leave the two result columns empty.
3. Select your Google credential and the same spreadsheet ID on Read stock sheet and Record result in Stock. Select a FLUF credential with write access on both FLUF nodes.
4. Execute the workflow manually. It checks the SKU first. If a listing already exists, it records that ID without changing the listing. Otherwise it creates a zero-stock draft and writes its ID back to the sheet.
5. Open the result in FLUF, add photos and any missing marketplace details, and review the quantity before deciding to crosslist.

This workflow does not publish anything to a marketplace. Run only one import at a time and keep SKUs unique. If a run fails after creating a draft, check FLUF before retrying; the SKU lookup helps recover without creating another draft. Duplicate sheet SKUs and SKUs with surrounding spaces stop the import for review. FLUF returns the first matching listing, so check that SKUs are unique in FLUF before importing.

Template 3: ask an AI assistant about an exact SKU

Download the inventory assistant workflow

For sellers: ask “What is the price and quantity for SKU DENIM-001?” For creators: use the workflow as a starting point for a private stock assistant. For agencies: keep each client's credentials and workspace separate.

1. Select your OpenAI credential on OpenAI chat model. Model usage is billed by your provider, and product information used in responses is sent to that provider.
2. Select a read-only FLUF credential on Look up SKU.
3. Use n8n's built-in chat to ask about a real SKU. Compare the response with FLUF. Try a nonexistent SKU too: the assistant should say it was not found.
4. Keep the chat private. Add appropriate authentication and access controls before building a customer-facing interface.

Its only tool is Find Listing by SKU. It cannot change prices, crosslist or ship orders. Zero stock and unknown stock are different; check the returned data before relying on an AI answer.

Template 4: get sale alerts in your team inbox

Download the sale email workflow

Know when a sale arrives without opening another dashboard.

1. Import the workflow and choose your FLUF credential on FLUF event.
2. In Email your team, select your Gmail credential and enter your own team address in To. The subject and plain-text body are already mapped. This sends an internal notification, not a buyer message.
3. Listen for a real New Sale event. Check the order ID, marketplace, order total and full item list in the email against FLUF. Unknown totals stay unknown rather than becoming zero.
4. Activate after a successful test. Repeated event delivery or manually replaying a run can send another email.

A notification does not confirm payment or shipping eligibility. Review the order in FLUF before fulfilling it.

Template 5: build a packing queue in Google Sheets

Download the packing queue workflow

Give your packing team a shared starting point, with one row per sale event and the full bundle of items.

1. Create a Packing tab with headers: event_id, order_id, channel, connection_id, sold_at, items, packing_status.
2. Select your FLUF credential on FLUF event. In Save in Packing, select Google credentials and set your spreadsheet ID.
3. Test with a real sale containing items. The items cell stores the full item array, including quantities, rather than just the first SKU. Events without items stop for review.
4. Enter packing progress manually in packing_status. The workflow does not map or overwrite that column.
5. Activate after checking the row against the order in FLUF.

Rows match event_id to reduce duplicate deliveries. Concurrent Sheets writes can still create duplicates. A later event for the same order can have a different event ID: reconcile by order, channel and connection before packing. This is an event intake queue; cancellations, returns and shipping changes are not synchronised. Always check the current order in FLUF. It does not purchase labels or mark orders shipped.

Template 6: email your team about crosslisting errors

Download the crosslisting error workflow

Surface failed crosslisting attempts with the listing ID, marketplace and error text.

1. Select your FLUF credential on FLUF event.
2. In Email your team, select Gmail credentials and enter your team's address in To.
3. Test using an existing real Crosslisting Error payload from your workflow's event history or a naturally occurring error while listening. Check the listing ID and error text. Do not deliberately fail a live listing to obtain a sample.
4. Activate when ready. Replayed events can send another email.

The workflow does not retry, edit or publish a listing. Open FLUF to review and fix the cause first.

Template 7: keep a zero-stock review queue

Download the zero-stock review workflow

Collect quantity-zero events so your team can review depleted stock.

1. Create a StockReview tab with headers: event_id, listing_id, channels_affected, fired_at.
2. Choose your FLUF credential on FLUF event. On Save in StockReview, select Google credentials and enter the spreadsheet ID.
3. Test with a real Out of Stock Alert event and check the listing ID. channels_affected is stored as a JSON array; it can be empty.
4. Activate when ready. Each event is matched by event_id; simultaneous deliveries can still duplicate rows in Sheets.

Quantity zero is not proof of a sale or a completed delist. This is event history, not a current inventory snapshot. Check FLUF before restocking. The workflow does not change quantity or marketplace availability.

Template 8: record confirmed crosslisting events

Download the publication ledger workflow

Keep a record of which listing reached which marketplace, with the marketplace ID and public link when available.

1. Create a Published tab with headers: event_id, listing_id, channel, external_id, channel_url, fired_at.
2. Select your FLUF credential on FLUF event. On Save in Published, select Google credentials and set the spreadsheet ID.
3. Test with a real Listing Crosslisted event. Compare the listing ID, channel and external ID with FLUF.
4. Activate when ready. Rows match event_id; simultaneous deliveries can still create duplicates in Sheets.

This records confirmations, not queued requests. A blank URL does not mean crosslisting failed: some channels supply no public link or moderate listings first. Later delists are not reflected here, so this is a history of publication events rather than a list of currently live stock.

Build on the templates

Creators can share walkthroughs showing how they adapt a workflow for their audience. Agencies can offer stock preparation, reporting and workflow maintenance using a separate FLUF token for each client. Start with one of the eight examples above, then add an approval step before actions that change a client's account.

FLUF's node also supports updating listings, crosslisting and delisting, finding orders, marking supported orders shipped, and reading connected channels. Triggers cover sales, new listings, stock and crosslisting events. Crosslisting is queued in the background: use Listing Crosslisted or Crosslisting Error to track the final result.

Troubleshooting

• Node not listed: check with your n8n workspace administrator. Self-hosted installations can use the npm package name above.
• Credential test fails: check the token and that your FLUF plan includes API access.
• Reads work but writes fail: check both your plan and token allow writes.
• No sale events: check the workflow is listening or active and the webhook address is reachable over HTTPS.
• Sheets columns do not match: check the tab, headers and spreadsheet ID, then refresh the node's column mapping.
• Import stops on a SKU: remove duplicate sheet rows and surrounding spaces. Check that SKUs are unique in FLUF too.

Disconnect

Deactivate your FLUF workflows in n8n first, then revoke their token in FLUF → Developers. If your n8n instance is unavailable, remove its webhook subscriptions in FLUF as well as revoking the token.