The tools QoreFlow syncs from

Contacts and invoices from your Xero organisation, with payments folded in.

Customers and invoices from your QuickBooks Online company: who you invoice, what you invoiced, when it was due, and whether it is paid, outstanding or overdue. QuickBooks connects by signing in to Intuit - there is no key to paste.

Orders are not created - QuickBooks Online is an accounting ledger, so QoreFlow syncs customers and invoices only. Bills, expenses, items, estimates, payroll and bank transactions are not synced. Intuit publishes no narrower read-only scope than its accounting scope, so the permission you grant technically permits more than reading: QoreFlow only ever reads, and never writes anything back to QuickBooks. A company whose home currency is not pounds is refused rather than converted.

Contacts and sales invoices from your Sage Business Cloud Accounting business: who you invoice, what you invoiced, when it was due, and whether it is paid, outstanding or overdue. Sage connects by signing in with your Sage ID - there is no key to paste.

Orders are not created - Sage is an accounting ledger, so QoreFlow syncs contacts and sales invoices only. Purchase invoices, bank transactions, products, quotes, estimates and payroll are not synced. Sage does publish a read-only permission, and QoreFlow asks for exactly that one, so the connection cannot change anything in Sage even in principle. A business whose base currency is not pounds is refused rather than converted.

Customers and invoices from Zoho Books: who you invoice, what you invoiced, when it was due, and whether it is paid, outstanding or overdue.

Orders are not created - Zoho Books is an accounting ledger, so QoreFlow syncs customers and invoices only. Bills, expenses, items, estimates and bank transactions are not synced, and amounts are taken as Zoho Books reports them and treated as GBP.

Customers and invoices from your Wave business: who you invoice, what you invoiced, when it was due, and whether it is paid, outstanding or overdue.

Orders are not created - Wave is an accounting ledger, so QoreFlow syncs customers and invoices only. Bills, receipts, products, estimates and bank transactions are not synced, and amounts are taken as Wave reports them and treated as GBP.

Companies and contacts from HubSpot as customers, and WON deals as orders: the deal amount, the date it closed, and its pipeline as the sales channel.

Open and lost deals, tickets, tasks, notes, line items and marketing activity are not synced, and no invoices are created - won deals are treated as orders. Amounts are taken as HubSpot reports them and treated as GBP.

Accounts and contacts from Salesforce as customers, and WON opportunities as orders: the amount, the close date, and the opportunity type as the sales channel.

Open and lost opportunities, leads, cases, tasks and products are not synced, and no invoices are created - won opportunities are treated as orders. Amounts are taken as Salesforce reports them and treated as GBP.

People and organisations from Pipedrive as customers, and WON deals as orders: deal value, the date it was won, and its pipeline as the sales channel.

Open and lost deals, activities, notes and products are not synced, and no invoices are created - won deals are treated as orders. Amounts are taken as Pipedrive reports them and treated as GBP.

Accounts and contacts from Zoho CRM as customers, and WON deals as orders: the deal amount, the date it closed, and the deal's pipeline as the sales channel.

Open and lost deals, leads, activities, notes and products are not synced, and no invoices are created - won deals are treated as orders. Amounts are taken as Zoho CRM reports them and treated as GBP.

Email campaigns, sends, opens and clicks from HubSpot Marketing.

Email campaigns you have already sent from Brevo, with Brevo's own figures for each one: sends, delivered, unique opens, unique clicks, unsubscribes and bounces.

Contacts, lists, automations, SMS and transactional email are not synced, and drafts and scheduled campaigns are not synced either - only campaigns Brevo records as sent.

Email campaigns you have already sent from Mailchimp, with Mailchimp's own figures for each one: sends, unique opens, unique subscriber clicks, unsubscribes and bounces.

Audiences, contacts, tags, landing pages, ads and automations are not synced, and drafts and scheduled campaigns are not synced either - only campaigns Mailchimp records as sent. Mailchimp does not report a delivered figure, so delivered is left at zero rather than being estimated.

Daily campaign figures for one Google Ads account: spend, impressions, clicks and conversions, one row per campaign per day. Figures for the last four weeks are refreshed on every sync, because ad platforms restate them.

No keyword, ad-group, ad-creative, audience, device or location detail, and no search terms - only daily totals per campaign. Google Ads accounts that report in a currency other than pounds are listed but cannot be selected, because QoreFlow models spend in pounds and will not convert figures on your behalf. Conversions are Google's own conversion count for the account's chosen conversion actions, not QoreFlow's.

Daily campaign figures for one Meta ad account - Facebook and Instagram placements together: spend, impressions, clicks and conversions, one row per campaign per day. Figures for the last four weeks are refreshed on every sync, because ad platforms restate them.

No ad-set, ad-creative, placement, audience, demographic or platform breakdown - only daily totals per campaign, so Facebook and Instagram spend arrives combined. Ad accounts that report in a currency other than pounds are listed but cannot be selected, because QoreFlow models spend in pounds and will not convert figures on your behalf. Conversions are Meta's own attributed conversion actions under the account's attribution setting, which Meta restates for weeks after the event.

Daily campaign figures for one LinkedIn ad account: spend, impressions, clicks and website conversions, one row per campaign per day. Figures for the last four weeks are refreshed on every sync, because ad platforms restate them.

No creative, audience, company, job-title or seniority breakdown, and no lead-form contents - only daily totals per campaign. Ad accounts that report in a currency other than pounds are listed but cannot be selected, because QoreFlow models spend in pounds and will not convert figures on your behalf. Conversions are LinkedIn's external website conversions only, so lead-form submissions are not counted as conversions.

Daily figures for one Facebook page: impressions, post engagements, and followers as the page's fans on the day. Followers = the page's fans on the day. Followers is the audience on that day, a point-in-time count, and is never summed across days. Figures for the last four weeks are refreshed on every sync, because social platforms restate them.

No per-post, per-video, demographic, location or referrer breakdown, no comment or message content, and no paid-versus-organic split - only daily totals for the page. Posts published per day arrive as zero, marked as not reported, because counting them needs access to your page's content and QoreFlow asks only for insights. Engagements are Meta's own page post engagements figure, which counts reactions, comments, shares and post clicks together and cannot be separated. Facebook deduplicates impressions within a day but not across days, so daily figures must not be added up to claim a monthly reach.

Daily figures for one Instagram business account: impressions, and followers as the account's follower count on the day. Followers = your followers on the day. Followers is the audience on that day, a point-in-time count, and is never summed across days. Figures for the last four weeks are refreshed on every sync, because social platforms restate them.

No per-post, story, reel, hashtag, demographic or location detail, no captions or comments, and no follower identities - only daily totals for the account. Engagements and posts published arrive as zero, marked as not reported, because Instagram serves neither at day grain for an account: an engagement figure exists only as a period total, and QoreFlow will not spread a period total across days as though it were daily. Instagram reports followers only as of the day it is asked, so earlier days in the window carry no follower figure rather than today's repeated backwards. Only business and creator accounts linked to a Facebook page can be connected at all, which is Meta's rule.

Daily figures for one LinkedIn organisation page: impressions, engagements as LinkedIn's own total interactions, and followers as the page's follower count on the day. Followers = your page followers on the day. Followers is the audience on that day, a point-in-time count, and is never summed across days. Figures for the last four weeks are refreshed on every sync, because social platforms restate them.

No per-post, per-video, demographic, seniority, industry or company-size breakdown, no post text or comments, and no visitor identities - only daily totals for the page. Posts published per day arrive as zero, marked as not reported, because LinkedIn serves no daily count of them at page grain. LinkedIn reports followers only as of the day it is asked, so earlier days in the window carry no follower figure rather than today's repeated backwards.

Daily figures for one YouTube channel: impressions as views, engagements as likes, comments and shares added together, videos published on the day, and followers as subscribers. Followers = subscribers on the day. Followers is the audience on that day, a point-in-time count, and is never summed across days. Figures for the last four weeks are refreshed on every sync, because social platforms restate them.

No per-video, playlist, traffic-source, geography, device or demographic breakdown, no watch time, no revenue, and no comment text - only daily totals for the channel. Subscribers are the channel's total on the day, arrived at from YouTube's daily net change, so a day YouTube withholds for privacy leaves the figure absent rather than guessed. Impressions are views, which is YouTube's own count of a video being watched, not an ad-style impression, and the two must not be compared across platforms as if they were the same thing.

Customers and orders from your WooCommerce store: order date, status, net total excluding tax and shipping, and your store as the sales channel.

Products, stock, coupons and refund records are not synced, and no invoices are created - WooCommerce orders become orders only. Amounts are taken as your store reports them and treated as GBP.

Customers and orders from one Shopify shop. Each order arrives with its date, the sales channel Shopify names it against, its status and the net value of the goods - tax, shipping and anything refunded taken off. Orders from the last four weeks are re-read on every sync, so a refund or cancellation recorded after the sale corrects the original order rather than leaving a stale figure or adding a second one.

No products, line items, inventory, fulfilments, payouts, transaction fees, draft orders or abandoned checkouts. Shops that sell in a currency other than pounds are listed but cannot be selected, because QoreFlow models revenue in pounds and will not convert figures on your behalf. Guest checkouts arrive as orders with no customer attached, because Shopify records no customer for them. An order status Shopify uses that QoreFlow does not model keeps Shopify's own word rather than being folded into one of ours.

Customers and orders from one BigCommerce store. Each order arrives with its date, the channel BigCommerce names the sale against, its status and the net value of the goods - tax, shipping and anything refunded taken off. Orders from the last four weeks are re-read on every sync, so a refund or cancellation recorded after the sale corrects the original order rather than leaving a stale figure or adding a second one.

No products, line items, inventory, shipments, payment fees, carts or abandoned checkouts. Stores that sell in a currency other than pounds are listed but cannot be selected, because QoreFlow models revenue in pounds and will not convert figures on your behalf. Guest checkouts arrive as orders with no customer attached, because BigCommerce records no customer for them. A BigCommerce order status QoreFlow does not model keeps BigCommerce's own word rather than being folded into one of ours.

Orders from your amazon.co.uk seller account: order date, the sales channel Amazon names, order status and the order total Amazon reports. Orders from the last four weeks are re-read on every sync, so a refund or cancellation recorded after the sale corrects the original order rather than leaving a stale figure or adding a second one.

No customers at all - buyer names and addresses sit behind Amazon's restricted data roles, so QoreFlow does not build a customer list from Amazon and every Amazon order arrives with no customer attached. No products, line items, inventory, fees, advertising, settlements or FBA figures. QoreFlow models the amazon.co.uk marketplace only, so other marketplaces are listed but cannot be selected. Amazon's Orders data reports the order total including tax, and reports cancellations rather than refund amounts, so an Amazon refund shows as the status Amazon gives it and not as a reduced value.

Payments and customers from your own Stripe account: each successful charge as a completed sale at the amount actually captured, with refunds subtracted so a refund recorded later corrects the original figure, plus the customers those payments belong to. Stripe is the odd one out in this family - there is no sign-in handover, because you create a restricted, read-only API key in your own Stripe dashboard and paste it here.

Balance, payouts, fees, disputes, subscriptions and Stripe invoices are not synced. Stripe's own processing fees are a cost, and QoreFlow will never net them off revenue behind your back. Only charges in pounds are modelled: a charge in another currency is not synced at all rather than converted. Nothing is ever written back to Stripe - the key you paste is read-only.

Daily website figures for one Google Analytics 4 property: sessions, users as visitors, page views and key events as conversions, split by Google's default channel group and mapped to QoreFlow's traffic sources. Each scheduled sync re-reads the last 7 days because Google Analytics figures settle late.

No page-level, device, location or campaign-name detail, and no visitor identities - only daily totals per traffic source. Channel groups Google does not name are recorded as 'other' rather than being guessed as paid or organic. Google Analytics applies its own sampling and thresholding to recent days, so QoreFlow reports what the API returns rather than adjusting it.

Daily Google search performance BY PAGE for one verified property: clicks, impressions and average position for each page on each day. Each scheduled sync re-reads the last 7 days because Search Console publishes its figures late.

Not by search query - QoreFlow syncs page-level performance only, so no keyword or search-term rows are brought in. No country, device or search-appearance breakdown either. Google omits rows with very low volume and anonymises rare queries, so totals here can sit below the totals shown in Search Console itself, and QoreFlow reports what the API returns rather than filling the gap.

Daily website sessions for one PostHog project: pageview events as pageviews, distinct people as visitors and distinct session ids as sessions, split by traffic source from the referring domain and UTM medium. Each scheduled sync re-reads the last 7 days because analytics figures settle late.

Conversions are not synced and land as 0 - conversion goals are not configurable in QoreFlow yet, and reporting a zero is honest where guessing one would not be. No event-level, person-level or feature-flag detail is stored. Where a day's visits came from more than one traffic source, a person who arrived from two of them is counted under each, so per-source visitors can exceed the day's people total.

Daily website sessions for one Matomo site: visits as sessions, unique visitors as visitors, pageviews from Matomo's Actions report, and goal conversions, split by traffic source. Each scheduled sync re-reads the last 7 days because analytics figures settle late.

No page-level, device or location detail, and no visitor identities - only daily totals per traffic source. Matomo groups campaign visits without saying whether a campaign was paid, so campaign visits land as 'other' rather than being guessed as paid. Some Matomo configurations do not report unique visitors over a range; where Matomo does not report them, visitors land as 0 rather than being estimated.

One .xlsx or .csv file from your OneDrive, mapped to customers, orders or invoices and re-read whenever the file changes. Rows you delete from the file are removed from QoreFlow too, because the file is the source of truth.

Documents, presentations, PDFs and the contents of other files. QoreFlow reads the one table you map and nothing else in your drive.

One .xlsx or .csv file from a SharePoint document library, mapped to customers, orders or invoices and re-read whenever the file changes. Rows you delete from the file are removed from QoreFlow too, because the file is the source of truth.

Site pages, lists, documents and PDFs. QoreFlow reads the one table you map and nothing else on the site.

One Google Sheet, .xlsx or .csv file from your Google Drive, mapped to customers, orders or invoices and re-read whenever the file changes. Rows you delete from the file are removed from QoreFlow too, because the file is the source of truth.

Docs, Slides, PDFs and the contents of other files. QoreFlow reads the one table you map and nothing else in your Drive.

One .xlsx or .csv file from your Dropbox, mapped to customers, orders or invoices and re-read whenever the file changes. Rows you delete from the file are removed from QoreFlow too, because the file is the source of truth.

Documents, PDFs, images and the contents of other files. QoreFlow reads the one table you map and nothing else in your Dropbox.

Posts, pages and authors from your WordPress site, with publish dates.

Boards, items and status changes from monday.com.

A deterministic year of UK SMB trading data - customers, orders across channels with seasonality, and invoices paid, outstanding and overdue - plus four months of website traffic by source, a year of email campaigns, three months of search performance by page, and thirteen months of advertising spend and social engagement by platform, and thirteen months of support tickets and work items with their priorities, channels, projects and assignees.

Nothing here is your data: it is generated, so the figures are plausible rather than real. Rates such as open rate, conversion rate and cost per click are not modelled - the counts are landed exactly as a real source would report them, and any rate is computed as a ratio measure. Where a figure would not exist at source it is left empty rather than filled with nought: an unanswered ticket has no first-response time, an unresolved ticket has no resolution time, and an unestimated work item has no points.