Three different things get called an integration, and adding them up into one number would flatter us. This page keeps them apart.
Some integrations are part of the product: you switch them on and a step of the flow runs through them. One of them, the spreadsheet, is on every plan, because it is how most migrations actually begin. And the generic connector catalogue that earlier versions of this site described has been withdrawn — the section below says why.
Built into the product
These are not optional adapters bolted on the side. Each one sits inside a step of the flow. FattureInCloud, your mail server and a James Suckling subscription are your own accounts, and we do not resell them. The AI provider and the lead search run on WineFlow's accounts: the AI and Leads add-ons are how you pay for them, and what they process passes through our account.
FattureInCloud
Professional and EnterpriseProformas are created on FattureInCloud from an offer, invoices from an order once its goods have shipped (or from a proforma), and credit notes against an invoice already there; customers are synced across; invoice status is read back; and past sales can be imported from it and matched against your own catalogue. Electronic invoicing to the Italian SDI happens on their side, not ours.
Wine-Searcher
Every planA market price reference for one wine, or for every wine on an offer, fetched before you quote. It stays internal: the figure never appears in what the customer receives. A Wine-Searcher account or Trade API key of your own is optional; if you add one, WineFlow stores it encrypted and uses it on your behalf.
James Suckling, Robert Parker, Vinous
Every plan; James Suckling with your own accountCritic scores are looked up on the schedule you set and stored against each wine: a scheduled run fills in the scores a wine is missing, and a refresh you start re-reads the ones it has. A match the system is not sure of waits in a review queue for someone to confirm. James Suckling needs your own subscription, and WineFlow signs in with the credentials you save.
Your own mail server (SMTP)
Every planOffers and campaigns (campaigns from Business up) leave through the mail server you configure — host, port, user, password — so replies come back to you and your domain keeps its own sending reputation. Until you configure one, they go out from WineFlow's own server under your company name; account emails such as password resets always do.
Worth stating plainly, because older material said otherwise: delivery used to run on the Gmail API and no longer does. Any provider that speaks SMTP works, Gmail included; none is privileged.
The AI provider
Professional and Enterprise; an add-on on BusinessThe assistant, wine enrichment and the intelligence reports reach a language model through OpenRouter, with Perplexity for research and a search API for web lookups. A monthly budget per company caps the web lookups, wine enrichments and newsletter drafts — 100 with AI Standard, 500 with Extended, uncapped on Enterprise; the assistant's own model calls are not counted. The intelligence reports need Professional or Enterprise.
Lead search
Leads add-on; included on EnterpriseLead generation queries Google Maps through a search API and returns businesses you can score, qualify and convert into customers without retyping them.
Monday.com
Enterprise onlyCustomers and warehouse rows are imported from your boards, and customers, suppliers and wines can be pushed back. Boards and groups are chosen per company; columns are recognised by their titles rather than mapped by hand. It is often described as a general feature; it is not. It is an Enterprise capability.
Stripe (for paying us)
Every planStripe is how you pay for WineFlow: checkout, plan changes and add-ons. It is not a way to collect money from your own customers.
The connector catalogue has been withdrawn
Until version 0.12.0, WineFlow listed 23 connectors: Salesforce, HubSpot, SAP Business One, Dynamics 365, NetSuite, Odoo, QuickBooks, Zoho Books, Shopify, WooCommerce, PrestaShop, Stripe, PayPal, the carriers DHL, UPS, FedEx, BRT and GLS, and analytics tools from Power BI to BigQuery. We then tested them end to end, and 22 of them did not work: the sign-in flow was never wired to the screen, exports sent WineFlow's field names instead of the other system's, imports could not be saved, and one export reported success without sending anything.
Since version 0.12.1, released on 30 September 2026, none of them is offered on the Connectors screen or through its API, and carrier tracking can no longer be set up from any screen. The code stays in our repository, and a connector comes back only once it has worked against a real account.
What remains is on this page: Excel and CSV, open to every plan, and FattureInCloud and Monday.com, which live in their own module and are described above.
Implemented is not the same as proven
A connector is written code before it is a working one. We would rather you knew the difference now than in week two, which is why a connector is listed only once it has worked end to end.
What we can and cannot claim
- The integrations built into the product — FattureInCloud invoicing, Wine-Searcher, the critic sources, email, the AI client — have automated tests against a simulated vendor. Not every path has one yet: FattureInCloud's sales-history import, for instance, does not.
- Vendor APIs move. A connector written against a 2024 API version can break without a single line changing on our side.
- Field mapping is where integrations really fail. A first sync is a supervised exercise, not a button.
- Ask us on the call about the system your business depends on. We will answer with a yes or a no rather than pointing back at this page.
If your business depends on a connector we have not proven, tell us before you sign. Scoping it is a conversation; discovering it after go-live is a problem.
Where this usually starts
Most migrations begin with a spreadsheet export of your catalogue and your customers, which works on any plan. What can be imported, who owns the data, and how long it takes.
And if you are wondering which systems WineFlow will not replace, that is written down too.