Connect FLUF to Zapier

Zapier connects FLUF to other apps—for example, adding a spreadsheet row when you create a listing.

Connect your FLUF account through the invitation below. You do not need individual approval from FLUF. Marketplace actions still follow the requirements of your connected channels.

FLUF is currently available through an early-access invitation, not Zapier's public app directory. Zapier has not yet reviewed or approved the integration. Zapier's own plan limits and charges still apply.

Looking for a workflow to start with? Browse the five Zapier automation recipes, then follow the setup steps below.

Connect your account

1. Sign into your Zapier account, or create one.
2. Open Channels in FLUF and choose Connect to Zapier. You can also open the invitation directly.
3. Accept the invitation, then create a Zap and select the FLUF Connect version added by that invitation.
4. Choose your event, then connect your FLUF account. Sign into FLUF if asked, check the account shown and choose Authorize.
5. Test the step before turning the Zap on.

Example: new listings to Google Sheets

1. Create a sheet with columns such as Title, SKU and Price.
2. In Zapier, choose FLUF Connect → New Listing as the trigger and connect your FLUF account.
3. Test the trigger. If there is no sample, create a draft listing in FLUF and test again.
4. Add Google Sheets → Create Spreadsheet Row as the action, choose your sheet and match its columns to the listing fields.
5. Test the action, check the resulting row, then publish the Zap. New listing events can now add rows; this does not export your whole existing catalogue.

Start with a harmless draft and a test spreadsheet. Actions that change listings or orders affect your real account.

Five more useful workflows

Choose a workflow below after connecting your account through the invitation above. These templates guide you through building a Zap in your own workspace; they are not one-click Zapier imports. Gmail and Google Sheets require your own connected Google account. Other apps' plan limits and charges still apply.

• Sale email alerts
• Packing queue
• Crosslisting error email alerts
• Zero-stock review queue
• Publication ledger

Use real trigger samples belonging to your FLUF account. Do not publish with placeholder or incomplete fields. The Sheets recipes match a source_id column to the trigger's ID (id). Treat this as an opaque key: an initial order preview and a later live event can have different IDs. Do not substitute Listing ID or Order ID. Remove test-created rows before publishing. If a required field is missing, refresh the sample before continuing. Keep notification recipients inside your team. Some triggers have no sample available on first setup. If a real sample is unavailable, keep the Zap in draft and contact FLUF support for help testing it.

Template 1: get sale alerts in your team inbox

Get an internal email when FLUF records a sale.

1. Create a Zap with FLUF Connect → New Sale and select your connected FLUF account. Test with a real sale.
2. Add Gmail → Send Email, connect your own Gmail account, and set To to your team inbox. Do not map the buyer username as a recipient.
3. Set the subject to FLUF sale: followed by the trigger's Channel, then Order ID. Choose a plain-text body and insert the following fields using Zapier's field picker:

1. Test the action to your own inbox. Compare the result with FLUF, then publish the Zap.

The flat item fields describe the first item only. The email is a heads-up, not a complete packing list or payment confirmation. Open the order for bundles and current shipping eligibility. Replaying a successful action can send the email again.

Template 2: build a packing queue in Google Sheets

Give your packing team a shared list of incoming sale events.

1. Create a Packing worksheet with the column headers shown below, plus a final packing_status column for manual updates. Format IDs and SKUs as plain text.
2. Create a Zap with FLUF Connect → New Sale. Connect FLUF and test with a real sale or order preview from your account.
3. Add Google Sheets → Lookup Spreadsheet Row. Select the spreadsheet and worksheet, choose source_id as the lookup column and the trigger's ID (id) as its value. Enable the option to create a row when no match exists.
4. Map the new-row fields:

1. Leave packing_status unmapped so your team can maintain it. Test once, confirm the row, remove the test-created row and publish. See the Google Sheets lookup instructions if the create-if-missing option is unfamiliar.

The first-item fields are a preview only: bundles must be checked in FLUF. Cancellations, returns and shipping changes do not update this queue. Check the current order before packing, and reconcile repeated order events by channel, connection and order ID. The lookup reduces duplicates but concurrent runs can still create them. Do not add an Update Row step that overwrites your manual packing status.

Template 3: email your team about crosslisting errors

Find failed listing attempts without repeatedly checking each marketplace.

1. Create a Zap with FLUF Connect → Crosslisting Error. Connect FLUF and test with an existing real error record. If no sample is available, keep the Zap in draft and contact FLUF support for help testing the trigger.
2. Add Gmail → Send Email, connect Gmail and enter your team inbox in To.
3. Set the subject to FLUF listing needs attention: followed by Listing ID and Channel. Choose a plain-text body and map:

1. Send a test to your own inbox and check the error details. Publish after reviewing the result.

This does not automatically retry or change listings. Fix the underlying issue in FLUF before retrying. Do not deliberately break a live listing to obtain a test record. Replaying an email action can send another notification.

Template 4: keep a zero-stock review queue

Collect quantity-zero events for your team to review.

1. Create a StockReview worksheet with the headers below. Format event and listing IDs as plain text.
2. Create a Zap with FLUF Connect → Out of Stock Alert, connect FLUF and test with a real event.
3. Add Google Sheets → Lookup Spreadsheet Row. Select source_id as the lookup column and the trigger's ID (id) as the value. Enable row creation when no match exists and map:

1. Test the action, check the listing ID and channels, remove the test-created row, then publish. If the app presents channels as line items, keep the complete list in this cell; do not silently map only its first entry.

Quantity zero is not proof of a sale or a completed delist. This is event history, not current stock. Review the listing in FLUF before restocking. The Zap does not change quantity or marketplace availability. Lookup-before-create reduces duplicate deliveries but cannot prevent all concurrent duplicates.

Template 5: record confirmed crosslisting events

Keep a record of listings that reached each marketplace.

1. Create a Published worksheet with the headers below. Format IDs as plain text to preserve long marketplace identifiers.
2. Create a Zap with FLUF Connect → Listing Crosslisted, connect FLUF and test with a real successful crosslisting event.
3. Add Google Sheets → Lookup Spreadsheet Row. Choose source_id as the lookup column and the trigger's ID (id) as the value. Enable creation when no row matches and map:

1. Test and compare the IDs and channel with FLUF, remove the test-created row, then publish.

This uses confirmed crosslisting events rather than queued requests. Some marketplaces provide no public URL or require moderation; a blank URL is allowed. Later delists do not update the ledger, so it is a publication history rather than current availability. Lookup-before-create reduces duplicates but simultaneous runs can still create them.

If the connection page does not open

Refresh FLUF's Channels page and try again, or use the direct invitation above. Searching Zapier's public directory will not find the integration while it is in early access. If you see Open on Zapier in a popup, choose it to continue.

Disconnect

Turn off any Zaps you no longer want to run, then open Zapier connection settings in FLUF and disconnect. Reconnect through Zapier when you want to use it again.