Make.com integrations number over 3,000 apps — but raw count undersells the real story: Make typically offers roughly double the preset actions per app compared to Zapier, meaning deeper control over the apps you already use, not just more logos on a page. The practical question isn't “does Make integrate with X” (usually yes) — it's which connections deliver value fastest.
Here are the 25 worth wiring up first, organized by what they unlock, plus the honest answer for when your app isn't in the catalog.
Key Takeaways
- Make connects 3,000+ apps, including 560 AI apps — and depth-per-app is its real edge over broader catalogs (Make, 2026)
- The HTTP and Webhooks modules are universal adapters: any tool with an API is reachable even without a native integration
- Start with your system-of-record apps (CRM, email, storage) — they anchor the most workflows
- Zapier's 8,000+ catalog still wins the long tail of niche tools — the one honest gap
The Core Stack: Connect These First
1-3. Google Workspace (Sheets, Gmail, Drive) — the universal glue. Sheets alone anchors half of all beginner automations as the poor-man's database; Gmail and Drive handle intake and filing. Our beginner tutorial builds on exactly these.
4. Slack — the notification endpoint for practically every workflow. Deep module support: messages, channels, users, reactions.
5. Notion — databases, pages, and blocks with granular control. The action depth here notably exceeds simpler platforms.
6. Airtable — the step up when Sheets stops scaling. Watch records, create, update, search — full CRUD support.
CRM & Sales
7. HubSpot — contacts, deals, tickets, and timeline events. The anchor of most B2B lead workflows.
8. Pipedrive — leaner CRM, equally deep module coverage.
9. Calendly — booking events trigger onboarding chains, CRM entries, and prep reminders.
10. LinkedIn — limited by the platform's API but workable for lead capture flows paired with enrichment tools.
The full lead-capture-to-CRM architecture using these is documented in our Make.com lead generation playbook.
E-commerce & Payments
11. Shopify — orders, products, customers, inventory. Watch Orders is among the most-used triggers on the platform.
12. WooCommerce — equivalent coverage for WordPress stores.
13. Stripe — payment events (successful charges, failed payments, new subscriptions) make superb triggers for fulfillment and dunning workflows.
Marketing & Content
14. WordPress — create and update posts programmatically; the backbone of content syndication chains.
15. Mailchimp / ConvertKit — subscriber management triggered by anything upstream.
16. Facebook + Instagram — publish, watch, and cross-post.
17. YouTube — watch channels for new videos, feed them into digest and repurposing workflows.
18. Typeform / Google Forms — form submissions are the classic automation entry point.
Browse all 3,000+ integrations yourself — free account, 2-minute signupThe AI Layer
19. OpenAI (ChatGPT) — classification, summarization, generation inside any scenario.
20. Anthropic (Claude) — same pattern, different model strengths.
21. Perplexity — research-with-citations as a workflow step.
These three transform integrations from plumbing into intelligence — sentiment triage, auto-summaries, draft generation. And since February 2026, Make's native AI Agents can orchestrate all of them as reasoning workflows rather than fixed chains.
Utility Modules (The Secret Weapons)
22. HTTP module — the universal adapter. Any REST API becomes an integration: authenticate, request, parse. This is the honest answer to “does Make integrate with [obscure tool]” — if it has an API, effectively yes.
23. Webhooks — instant triggers from any system that can send a POST request. Also the #1 credit-saving swap versus polling triggers.
24. JSON / Text parser — transform data between apps that disagree about formats.
25. Tools (Sleep, Set Variable, Increment) — the small utilities that make complex scenarios composable.
When Make Doesn't Have Your App
Three options, in order:
- HTTP module (above) — 30 minutes of API-doc reading replaces most missing integrations
- Check for a community app — Make's partner-built catalog grows monthly
- Accept the gap and bridge via Zapier for that one tool — the long tail of 8,000+ apps is genuinely Zapier's strongest argument, and hybrid setups are common
What “Double the Actions” Means in Practice
The depth-per-app claim deserves a concrete illustration, because it's Make's least understood advantage.
Take a typical CRM integration. A shallow integration offers the obvious verbs: create contact, update contact, new-contact trigger. Make's version of major apps typically adds the granular layer: search with filters, watch specific field changes, manage associations between records, handle custom properties, work with engagement events — the verbs that real workflows actually need once they mature past hello-world.
The practical consequence: on shallow platforms, workflow ideas die with “the integration doesn't support that,” pushing you into API workarounds early. On Make, the native module usually already has the verb — and when it doesn't, the make-an-API-call module within each app integration (a halfway house between native modules and raw HTTP) covers the gap while reusing your existing authentication.
That last feature deserves its own mention: most major Make integrations include an “API Call” action that lets you hit any endpoint of that app's API using the connection you've already authorized. It's the escape hatch that makes “does Make support X's obscure feature” almost always answerable with yes.
Open any integration and count the actions yourself — free account, no cardDepth compounds quietly: you notice it not on day one, but in month three, when the workflow you're imagining turns out to already be possible.
Wire up your first five apps this week — Make's free plan includes the full catalogConnection Health: The Maintenance Habit Nobody Mentions
Integrations aren't fire-and-forget. Every connection you add is an OAuth token or API key that can expire, get revoked when a password changes, or break when the upstream app ships an API update. Across a 20-connection account, expect one or two connections to need re-authorization per quarter.
Two habits keep this painless. First, name connections properly at creation time — “Gmail (billing inbox)” not “My connection 3” — because six months later you will not remember which token does what. Second, set a warning email on scenario errors (Scenario settings → Notifications) so an expired token surfaces as an email the same hour, not as three weeks of silently unsynced leads.
When an app updates its API, Make typically ships a new module version and marks the old one as legacy. Legacy modules keep running, but plan the swap during a quiet week rather than waiting for the forced deprecation — the version-upgrade path is a five-minute job when it's voluntary and an incident when it isn't.
FAQ
How many integrations does Make.com have? 3,000+ apps including 560 AI apps, with roughly double the preset actions per app compared to Zapier's broader but shallower catalog.
Does Make.com integrate with [my app]? Check the directory first; if absent, the HTTP module reaches any tool with a REST API — which covers nearly everything modern.
Are Make.com integrations free? All integrations are available on every plan, including free. You pay for volume (credits), never for catalog access.
Which integration should a beginner connect first? Google Sheets — it's the training-wheels database that makes every other workflow testable.
Connect the five apps at your business's center first, and the rest of the catalog reveals itself as needed — that's how Make.com integrations compound: each new connection multiplies what every existing one can do. For how the whole platform holds up in production, our Make.com review has the 90-day answer.
