App Integrations
Every integration pair compared across Zapier, Make, and n8n. See which platform supports your apps, how many triggers and actions are available, and which one we recommend for each combination.
215 integrations — page 1 of 9
Deel + QuickBooks
Deel runs global contractor payroll. QuickBooks tracks the books. Deel's own QuickBooks integration handles the main path — invoices, expenses, and vendor records sync automatically to QuickBooks Online. An automation tool covers the rest: Slack alerts when contracts terminate, bridging Deel to QuickBooks Desktop (where native sync doesn't work), reconciliation reports, and triggering QB records from approved timesheets.
PagerDuty + Sentry
Sentry captures errors; PagerDuty wakes up the engineer. The pair is foundational to any incident-response workflow — a Sentry alert fires, a PagerDuty incident triggers, and the on-call sees it on their phone in seconds. Sentry and PagerDuty ship a direct native integration, but teams use automation platforms to extend it: enrichment, conditional routing, noise filtering, two-way resolution sync, and custom escalation logic the native connector does not cover.
HubSpot + Zoom
Zoom is where sales calls happen. HubSpot is the CRM behind them. HubSpot ships a native Zoom Meetings app that logs recordings and transcripts to the contact timeline. An automation platform covers what native doesn't: webinar registration flows, attaching summaries to specific deals, deal-stage updates from meeting outcomes, and moving attendees into nurture workflows based on attendance.
Cal.com + HubSpot
Cal.com is an open-source scheduler — think Calendly, but you can host it yourself. HubSpot is a CRM. When someone books a demo in Cal.com, sales ops wants that person in HubSpot before the call starts. Both apps have a native integration that handles contact sync. An automation platform is for the extras: creating deals, routing by lead value, and pinging Slack on high-value bookings.
Canva + Slack
Canva is where marketing teams make graphics, decks, and social posts. Slack is where they talk about everything else. Canva ships a native Slack app that handles sharing designs and comment notifications, so most teams start there. An automation tool helps with the stuff the native app doesn't do: pulling Slack file uploads into a Canva brand kit, posting design-export links to custom channels, and kicking off design drafts from a slash command.
PandaDoc + Salesforce
PandaDoc builds and sends sales documents — proposals, contracts, quotes. Salesforce is the CRM where those documents correspond to opportunities. PandaDoc ships a native Salesforce integration as a paid add-on with two-way sync, which is the right path for most sales teams. An automation platform covers the edges: teams not paying for the add-on, workflows outside its scope, and cross-tool alerting when a contract sits unsigned too long.
GitLab + Slack
GitLab is where engineering work happens; Slack is where engineering teams talk about it. Bridging them pushes merge request events, pipeline results, and review requests into the Slack channels where engineers already live. The native GitLab-for-Slack app covers the base case, so this pair is specifically for teams that need cross-tool enrichment, per-project routing, and the custom notification logic the native app can't express.
Greenhouse + Microsoft Teams
Greenhouse is where recruiting happens; Microsoft Teams is where the rest of the company lives. Connecting the two pulls candidate events out of the ATS and puts them in the channels and DMs where hiring managers, interviewers, and execs already work. Teams running high-volume recruiting on Greenhouse use this pair to turn stage changes, scheduled interviews, and offer approvals into Teams notifications, cutting the lag between pipeline activity and human attention.
Figma + Linear
Figma and Linear link the two systems where product work actually lives — design comments and engineering tickets. This pairing closes the handoff gap: instead of designers pasting screenshots into Linear by hand or engineers scrolling Figma threads for context, automation keeps the two graphs aligned. Teams blending design, PM, and engineering lean on this integration to make review loops and shipping status auditable in both tools without double-entry.
Google Forms + Google Sheets
Google Forms collects responses; Google Sheets stores, analyzes, and shares them. The two have a native link that covers the one-form-one-sheet case built into Google Workspace. Integration with an automation platform exists for workflows the native link can't do: fan-out to multiple sheets, multi-form aggregation, transformations on response data, or multi-destination routing where the same response also needs to hit a CRM or Slack.
HubSpot + Intercom
HubSpot is the CRM source of truth; Intercom is the customer messaging surface. Integrating them matches inbound Intercom conversations to HubSpot contacts, pushes ticket events into the CRM, and keeps properties in sync across both systems. Both apps ship native marketplace integrations — but running them alongside another sync creates duplicate user data, so the iPaaS path matters specifically for workflows the native apps can't cover, like ticket-to-deal lifecycle routing.
Miro + Notion
Miro is a digital whiteboard. Notion is a docs-and-database tool. Teams use them together for product work: Miro for brainstorming and flows, Notion for specs and wikis. Notion has a native embed that lets you drop a public Miro board into a page. An automation platform does the other direction: creating a Miro board automatically when a Notion database row appears, pre-populated with cards from the row's fields.
Gusto + QuickBooks
Gusto runs payroll; QuickBooks tracks the books. Their native integration handles the core path — automated journal entries from Gusto to QuickBooks Online on every pay run. Automation platforms matter here for the cases that fall outside that path: QuickBooks Desktop workflows, custom class or location categorization, contractor vendor sync, and bridging finance ops across other tools like Slack, Sheets, and approval systems. Teams serious about payroll accounting start with the native sync and layer iPaaS for the edges.
PayPal + QuickBooks
PayPal processes payments. QuickBooks tracks the books. QuickBooks ships a free native Connect to PayPal app that pulls PayPal sales, refunds, fees, and deposits into the Banking tab for review. That covers basic reconciliation. An automation platform helps with the detail work native doesn't do: creating QuickBooks customer records, generating per-sale invoices, consolidating multiple PayPal accounts, and alerting finance on refunds.
Discord + Slack
Discord and Slack are the two dominant chat platforms, but they serve different crowds — Discord runs communities, Slack runs companies. Integrating them lets you relay announcements, sync support threads across audiences, or bridge two overlapping groups without making members choose which tool to open. Community managers, developer-relations teams, and open-source maintainers rely on this pair to meet users where they already chat.
Google Sheets + JotForm
JotForm is a form builder. Google Sheets is a spreadsheet. When someone fills out a JotForm, you usually want the answers in a Sheet. JotForm has a native Google Sheets integration built in that handles the simple case: one form, one sheet, fields mapped. An automation platform covers the rest — splitting responses into multiple rows, routing to different sheets, and fanning out to Slack or a CRM at the same time.
BambooHR + DocuSign
BambooHR is the system of record for employee data; DocuSign is the system of record for signed agreements. Together they handle the paperwork side of hiring and employee lifecycle: offer letters, onboarding forms, policy acknowledgments, and role-change documents. Integrating them means HR teams stop shuttling PDFs between inboxes and drives, and BambooHR records stay authoritative as envelopes move through signed, declined, or expired states.
ConvertKit + Gumroad
Gumroad is where creators sell digital products and memberships; Kit (formerly ConvertKit) is where they maintain the email relationship. Integrating the two closes the gap between a sale and the post-purchase sequence — tagging buyers, moving them into product-specific flows, handling refunds and cancellations, and keeping customer-only broadcast segments accurate. For solo creators and small teams running Gumroad, this pair is the backbone of post-purchase email.
Shopify + Square
Shopify runs your online store. Square runs your in-person POS (point-of-sale terminal). Unlike most pairs in this series, there's no native integration — Shopify and Square compete, so bridging the two always means a third-party tool. An automation platform handles inventory sync, order routing, and catalog matching between them. Dedicated Shopify App Store bridges also exist for merchants who need inventory reservation and multi-location support past what iPaaS offers.
Loom + Slack
Loom records short videos. Slack is where teams work. Loom ships a native Slack app that handles the main stuff — /loom to record, videos embed in-line, pings when someone watches or reacts. Because Loom has no open API (only an SDK and webhooks), an automation platform here is narrower than usual: archive videos to Drive or Notion, alert on specific viewers, or digest weekly video activity back into Slack.
HubSpot + Slack
Get instant Slack notifications for new HubSpot leads, deals, and form submissions. Keep your sales team in the loop without leaving their chat window.
Salesforce + Slack
Get Slack notifications for new Salesforce leads, deal stage changes, and opportunity updates. Keep your enterprise sales team informed in real-time.
Gmail + Google Sheets
Log incoming emails to a spreadsheet automatically. Track client inquiries, support requests, or any inbox that needs a searchable paper trail.
HubSpot + Gmail
Automatically create or update HubSpot contacts from incoming Gmail emails. Log email activity to CRM records, and trigger email sequences based on CRM events.