FLUF Connect

Approve a review draft and send it to the marketplace, optionally correcting fields first — the way to resolve a `failed` draft. This publishes a real listing. `state` comes back as `listed` (live now), `pending` (accepted and publishing shortly, so a resend is not needed) or `failed` (the marketplace refused again; `message` says why and `draft` is the refreshed draft). Physical items only: through ChatGPT, FLUF will not list digital goods, gift cards, tickets, services or items in prohibited categories (weapons, drugs, medicines, tobacco, adult); those come back under `not_listable_here`.

approve_draft

Ask Intesa, the FLUF assistant inside the seller's account, a question. In ChatGPT Intesa only reads: it explains why a channel stopped syncing, what a listing error means, what sold and where, and answers from FLUF's support docs. It does not change listings, settings or anything else. Replies can take up to a minute.

ask_intesa

List existing FLUF products on one or more marketplaces. Not always synchronous: channels completed by the seller's own browser extension (e.g. Vinted, Facebook) return `queued` and go live minutes later. The response has a `status` per channel. Repeats of the same (product, channel) pair within 30s are ignored as accidental double-submits. Physical items only: through ChatGPT, FLUF will not list digital goods, gift cards, tickets, services or items in prohibited categories (weapons, drugs, medicines, tobacco, adult); those come back under `not_listable_here`.

crosslist

Delete FLUF products. By default only the FLUF record is removed and every marketplace listing is left untouched; pass `also_delist: true` to also end the listings on every marketplace they are live on, which cannot be undone. Deleted FLUF records go to Recently Deleted in the dashboard and can be restored for 60 days. Suited to sold-out or obsolete inventory.

delete_products

Get the seller's orders across every connected marketplace, in one unified shape.

get_orders

List the marketplace channels available on this account: which are already connected, and which this seller's plan can list to. Returns the channel ids that crosslist accepts; the roster differs per account and changes over time.

list_channels

List the authenticated seller's FLUF products. Each row has a `vid` (the product handle that crosslist accepts), title, price, stock, source channel and the channels it is already live on. `status` is what the channel last reported to FLUF, not a live check, so an ended listing can still read 'active'. Each row's `liveness` ('confirmed' | 'unconfirmed' | 'unknown'), `last_seen_at` and `last_seen_age_hours` say when a channel scan last returned that listing. Filtering on `liveness: "confirmed"` narrows both the rows and `total` to listings a channel has recently confirmed; without it, `total` counts the seller's whole listing history. Two 'active' rows for the same item are usually one listing that ended and its relist, because channels issue a new listing id on relist. Each row's `listed_on` maps channel → {first_listed_at, last_listed_at} (ISO 8601): when FLUF first and most recently listed the item there. Kept after the item sells or ends, so it works for sold products too. Channels FLUF never pushed to, such as the item's own source, are absent; use `created_date` for that.

list_products

List the seller's review drafts: listings FLUF has prepared but not sent. A `failed` draft is one a marketplace refused for a reason the seller can fix — the `reason` says what it objected to, and `fields` holds every value with `editable: true` on the ones that can be changed (a `select` field lists its `options`). A `pending_review` draft is waiting for a go-ahead. approve_draft sends a draft, with corrected values if any. Once the item is live on that marketplace its draft leaves this list on its own.

list_drafts

Send a bug report to FLUF's human support team. Use it when the user describes a problem with FLUF that can't be resolved here, or when a FLUF tool keeps failing or contradicts the user's account and the user agrees to report it. The report arrives as a direct message a person reads, so the fields are short: a title, two or three sentences, and the identifiers. Problems the user can fix themselves (expired token, lapsed plan, a channel needing reauthorisation) are not bugs — the fix belongs in the reply instead. The user's account identity is attached automatically. Replies arrive in the user's FLUF inbox.

report_bug