Integrations

Integrations, one pair at a time

Each page pairs two connectors with a worked flow, a starting field map, what syncs in each direction, and how approvals and audit apply.

Request a Demo Browse all connectors

Integration

HubSpot to NetSuite

Turn a closed-won HubSpot deal into a NetSuite customer and sales order without rekeying: the flow reads the deal's associated company and contacts, creates or matches the customer, and raises the order, with a value gate for large deals. Order number and billing status flow back to the deal. Every order is a run you can inspect step by step.

Two-way · Within minutes of a won deal · Deal moves to Closed Won

Integration

HubSpot to QuickBooks

Turn a closed-won HubSpot deal into a QuickBooks invoice, built from the deal's line items, with the company matched so nothing is duplicated. When the invoice is paid, the deal shows it, and revenue properties in HubSpot stay honest. An approval step can hold anything unusual. Every invoice is a run you can inspect step by step.

Invoice out, payment back · Minutes after close · Won deal, then payments

Integration

HubSpot to Salesforce

Keep marketing's system and sales's system in step: qualified contacts and companies flow from HubSpot into Salesforce, pipeline and owner changes flow back, and each field has a defined source of truth so neither side overwrites the other. Every record change is a run you can inspect step by step.

Two-way · Within a polling interval · Lifecycle stage or property changed

Integration

HubSpot to Slack

Put deal activity where the team will actually see it, and put a control where it matters. Deal stage changes and new high-value deals alert the right channel, a discount over a threshold waits for an approver, who gets the approval link in Slack, a deal room channel is created for large opportunities, and its messages are logged back to the HubSpot deal as notes. One run history.

Mostly HubSpot to Slack · Within minutes of the change · New or updated deal

Integration

HubSpot to Snowflake

Land HubSpot contacts, companies, deals, and engagements in Snowflake within minutes of a change, model them alongside the rest of your data, and write scores and segments back to HubSpot, with every load recorded as a run you can inspect.

Mainly HubSpot to Snowflake · Within a polling interval · Contact or deal changed

Integration

NetSuite to Snowflake

Land NetSuite transactions, entities, and custom records in Snowflake without a nightly export you cannot see into: SuiteQL queries and SuiteAnalytics datasets on a short schedule, merged on internal ID with a watermark. Every load is a run you can inspect step by step.

NetSuite to Snowflake · Every few minutes, polled · Scheduled, on lastModified

Integration

Salesforce to Google Sheets

Give a stakeholder a Salesforce view they can open without a login, and let a team maintain a lookup table a flow reads live: a pipeline sheet refreshed on a schedule with a last-updated stamp, and a routing sheet the sales ops team edits that drives lead assignment. Rows are matched on a key column, not a shifting row number, and every write is a run you can inspect.

Two-way · Scheduled, or on record change · Schedule, or new record

Integration

Salesforce to NetSuite

Keep the CRM and the ERP in step: push closed-won deals into NetSuite as sales orders, map customers and items cleanly, and send billing and fulfillment status back to Salesforce, with every sync recorded as a run you can inspect step by step.

Two-way · Within minutes, or scheduled · Opportunity closed-won

Integration

Salesforce to QuickBooks

Close a deal in Salesforce and have the invoice waiting in QuickBooks Online, with the customer matched and the line items carried from the opportunity. When the invoice is paid, the opportunity shows it. No rekeying, no month-end surprises, and an approval step for anything unusual. Every invoice is a run you can inspect step by step.

Invoice out, payment back · Minutes after close · Won opportunity, then payments

Integration

Salesforce to Slack

Bring Salesforce into the channel where the team already works: deal and pipeline alerts with the record context attached, and approval steps that hold a workflow for a named person, send them the link in Slack, and write the decision, and who made it, back to Salesforce. Every notification and approval is in the run history.

Alerts out, decisions back · Within minutes of the change · Opportunity or quote changed

Integration

Sync Salesforce to Snowflake

Land Salesforce accounts, opportunities, and custom objects in Snowflake as they change, using Change Data Capture, model them next to the rest of your data, and write scores and segments back to Salesforce, with every load recorded as a run you can inspect.

Mainly Salesforce to Snowflake · Streamed via Salesforce CDC · Record created or updated

Integration

Shopify to HubSpot

Give HubSpot the full picture of every Shopify customer: contacts with real order history, orders as a custom object with line items and revenue, and abandoned checkouts that a HubSpot workflow can act on. Marketing consent from checkout is carried, never assumed. Every sync is a run you can inspect step by step.

Mostly Shopify to HubSpot · As Shopify sends the webhook · orders/create, customers/update

Integration

Shopify to NetSuite

Push paid Shopify orders into NetSuite as sales orders, matching shoppers to customers and line items to items, hold high-risk orders for review before they post, and send fulfillment status and inventory levels back to the store. Every order is a run you can inspect step by step.

Two-way · On each paid order · Order paid

Integration

Shopify to QuickBooks

Book Shopify sales in QuickBooks Online without exporting a spreadsheet every week. Each paid order becomes a sales receipt with tax and shipping on their own lines, each Shopify Payments payout is reconciled to the bank deposit with fees split out, and refunds are booked as they happen. Every entry is a run you can trace back to the Shopify order.

Shopify to QuickBooks · On each order, payouts daily · orders/paid

Integration

Stripe to NetSuite

Book Stripe activity into NetSuite the way finance needs it: each paid invoice recorded as a customer payment against the right AR invoice, each payout reconciled to a bank deposit with processing fees on their own line, and anything that will not match sent to a person for review. Every entry is a run you can trace.

Mainly Stripe to NetSuite · As each Stripe event arrives · invoice.paid, payout.paid

Integration

Stripe to QuickBooks

Get Stripe into QuickBooks Online the way an accountant would: each payout recorded as a bank deposit that matches the real bank line, processing fees posted to a fees account, and sales and refunds booked as they happen. Every entry is a run you can trace back to the Stripe object.

Stripe to QuickBooks · On payout, typically daily · payout.paid

Integration

Stripe to Salesforce

Put the billing signal where the account team can see it. Subscriptions, payments, and failed charges from Stripe land on the Salesforce account and opportunity, MRR stays current on the account, and a failed payment opens a case for CS before the customer churns. Every update is a run you can trace back to the Stripe event.

Mostly Stripe to Salesforce · As each Stripe event arrives · invoice.paid, invoice.payment_failed

Integration

Stripe to Snowflake

Land Stripe in Snowflake so finance and analytics model revenue on the same data. Charges, invoices, subscriptions, refunds, and payouts load from the event stream with a historical backfill, amounts are normalized out of integer minor units, and each payout is tied to the balance transactions inside it. Every batch is a run you can inspect.

Stripe to Snowflake · As events arrive, plus backfill · Stripe event, scheduled reconcile

Integration

Zendesk to Salesforce

Give support agents the account context on every ticket, and give the CRM a live view of support load: new tickets create or link a Salesforce Case, status and comments sync both ways with a loop check in the flow, and each account's ticket count and CSAT roll up to the Salesforce Account. Every record change is a run you can inspect.

Two-way · Webhook in, polled back · Ticket created or updated

What each page covers

Each page is a starting point, not a template you are locked into. The worked example is a flow teams often build first, the field mapping is where that flow starts, and the direction table shows what moves each way. Where a connector describes its output fields, you can check the mapping against them in the builder; otherwise check it with Test this step.

Every pair runs on the same platform as every other flow: the same connectors, the same run history with step-level detail, the same approvals when a person needs to decide, and the same tamper-evident audit log for every action.

Not seeing your pair?

Any two of the 310 connectors can be combined in a flow, and a Poll for changes trigger or an inbound webhook endpoint gives any pair an event-driven start. If the pair you need is not documented yet, bring it to a demo and we will build it against your own systems.

Frequently asked questions

Do these pages describe pre-built templates?

They describe flows built from standard steps on the platform: a trigger, a lookup, a mapping, a write, and the approvals and error handling around them. Nothing on these pages needs code, and every step is visible in the run history when it runs.

How current are the connector facts?

The operation counts, trigger counts, and delivery kinds match the connectors in the current release of the platform.

See it on your data

Bring one real integration

We will build it with you against your own systems, with the run log open.

Request a Demo