Make · Product

Make Integrations

Thousands of native connectors, plus anything with an API.

The app catalogue spans CRM, ecommerce, finance, marketing, support and data tooling. For serious builds the more important capability is the generic HTTP module and the custom-app framework, which turn 'not supported' into 'not yet packaged'.

Disclosure: We may earn a commission if you purchase through links on this page. This never affects our reviews.

Features
🔌

Native connectors

Pre-built modules with typed inputs and outputs for mainstream SaaS.

🌐

Generic HTTP

Any documented REST API with OAuth, API key or basic auth.

📦

Custom apps

Package your own connector once and reuse it across scenarios.

📡

Webhooks both ways

Receive instant events and send payloads to any endpoint.

Use cases
  • Connect an internal API to your CRM without writing a service
  • Sync ecommerce orders into accounting and fulfilment
  • Pipe product events into analytics and lifecycle email
  • Bridge two tools that will never build a native integration
Tutorials

Connect an API that has no native Make connector

The HTTP module pattern that covers most 'unsupported' integrations.

  1. Read the vendor's auth docs and create credentials.
  2. Add the HTTP module and configure the auth header or OAuth connection.
  3. Send one test request and inspect the raw response bundle.
  4. Map the fields you need into the next module explicitly.
  5. Wrap the call in an error handler with a retry for rate limits.
FAQs
Does Make integrate with my tool?+

Almost certainly — either natively or through the generic HTTP module if the tool has a documented API.

Are connectors as polished as Zapier's?+

Mostly, though Zapier still leads on the very long tail of niche SaaS apps.

Related reading