Make - Nango Docs

Overview

Pre-built tooling

Pre-built integrations

Access requirements

Setup guide

Useful links

API gotchas

Pre-built tooling

✅ Authorization

Tools	Status
Pre-built authorization (API Key)	✅
Pre-built authorization UI	✅
Custom authorization UI	✅
End-user authorization guide	✅
Expired credentials detection	✅

✅ Read & write data

Tools	Status
Pre-built integrations	✅
API unification	✅
2-way sync	✅
Webhooks from Nango on data modifications	✅
Real-time webhooks from 3rd-party API	🚫 (time to contribute: <48h)
Proxy requests	✅

✅ Observability & data quality

Tools	Status
HTTP request logging	✅
End-to-end type safety	✅
Data runtime validation	✅
OpenTelemetry export	✅
Slack alerts on errors	✅
Integration status API	✅

✅ Customization

Tools	Status
Create or customize use-cases	✅
Pre-configured pagination	🚫 (time to contribute: <48h)
Pre-configured rate-limit handling	🚫 (time to contribute: <48h)
Per-customer configurations	✅

Others

Function name	Description	Type	Source code
`clone-scenario`	Duplicate a scenario into the same or a different team.	Action	🔗 Github
`create-data-store-record`	Create a new record in a data store.	Action	🔗 Github
`create-data-store`	Create a new data store	Action	🔗 Github
`create-data-structure`	Create a new data structure (schema) that data stores or scenarios can use.	Action	🔗 Github
`create-hook`	Create a new custom webhook.	Action	🔗 Github
`create-scenario`	Create a new scenario from a blueprint.	Action	🔗 Github
`create-team`	Create a new team within an organization.	Action	🔗 Github
`delete-data-store-records`	Delete one or more records from a data store.	Action	🔗 Github
`delete-data-store`	Delete one or more data stores from a team.	Action	🔗 Github
`delete-hook`	Delete a webhook.	Action	🔗 Github
`delete-incomplete-executions`	Delete one or more incomplete executions for a scenario.	Action	🔗 Github
`delete-scenario`	Delete a scenario.	Action	🔗 Github
`disable-hook`	Disable a hook so it stops accepting incoming data.	Action	🔗 Github
`enable-hook`	Enable a disabled hook to start accepting incoming data	Action	🔗 Github
`get-connection`	Retrieve details of a single connection	Action	🔗 Github
`get-data-store`	Retrieve details of a single data store.	Action	🔗 Github
`get-data-structure`	Retrieve details of a single data structure.	Action	🔗 Github
`get-hook-incoming`	Retrieve the full payload of a single queued webhook item.	Action	🔗 Github
`get-hook`	Retrieve details of a single hook.	Action	🔗 Github
`get-organization`	Retrieve details of a single organization.	Action	🔗 Github
`get-scenario-blueprint`	Retrieve the current blueprint (flow definition) of a scenario.	Action	🔗 Github
`get-scenario-execution`	Retrieve the status and result of a single scenario execution.	Action	🔗 Github
`get-scenario-log`	Retrieve a single execution log entry for a scenario.	Action	🔗 Github
`get-scenario-usage`	Retrieve operations and data-transfer usage for a scenario.	Action	🔗 Github
`get-scenario`	Retrieve all properties of a single scenario.	Action	🔗 Github
`get-team`	Retrieve details of a single team.	Action	🔗 Github
`learn-start-hook`	Put a hook into learning mode to auto-detect the payload structure of the next request.	Action	🔗 Github
`learn-stop-hook`	Stop payload structure detection for a hook.	Action	🔗 Github
`list-connections`	List connections for a team.	Action	🔗 Github
`list-data-store-records`	List records stored in a data store.	Action	🔗 Github
`list-data-stores`	List data stores for a team.	Action	🔗 Github
`list-data-structures`	List data structures (schemas) for a team.	Action	🔗 Github
`list-hook-incomings`	List queued webhook payloads waiting for processing by a scenario.	Action	🔗 Github
`list-hooks`	List webhooks/mailhooks for a team.	Action	🔗 Github
`list-incomplete-executions`	List incomplete/failed executions (DLQ) for a scenario.	Action	🔗 Github
`list-organizations`	List organizations the API token’s user is a member of.	Action	🔗 Github
`list-scenario-logs`	List execution and edit history log entries for a scenario.	Action	🔗 Github
`list-scenario-module-logs`	List operation logs for a single module within a scenario.	Action	🔗 Github
`list-scenarios`	List scenarios for a team or organization.	Action	🔗 Github
`list-teams`	List teams within an organization.	Action	🔗 Github
`ping-hook`	Check whether a hook is active and inspect its learned data structure.	Action	🔗 Github
`run-scenario`	Manually execute an active scenario.	Action	🔗 Github
`start-scenario`	Activate (turn on) a scenario so it can run on its schedule or trigger.	Action	🔗 Github
`stop-scenario`	Deactivate (turn off) a running scenario.	Action	🔗 Github
`test-connection`	Verify that a connection’s saved credentials are still valid.	Action	🔗 Github
`update-connection-name`	Rename a connection.	Action	🔗 Github
`update-data-store-record`	Update a single record in a data store.	Action	🔗 Github
`update-data-store`	Update a data store’s name, structure, or size limit.	Action	🔗 Github
`update-data-structure`	Update a data structure’s name or field spec.	Action	🔗 Github
`update-hook`	Rename a hook.	Action	🔗 Github
`update-scenario`	Update a scenario’s name, blueprint, or scheduling.	Action	🔗 Github
`update-team`	Update a team’s name or operations limit.	Action	🔗 Github
`connections`	Sync connections for a team.	Sync	🔗 Github
`data-store-records`	Sync records inside each data store for a team.	Sync	🔗 Github
`data-stores`	Sync data store metadata (not records) for a team.	Sync	🔗 Github
`hooks`	Sync webhooks/mailhooks for a team	Sync	🔗 Github
`incomplete-executions`	Sync incomplete/failed executions (dead-letter queue) for each scenario in a team.	Sync	🔗 Github
`organizations`	Sync organizations the API token’s user belongs to.	Sync	🔗 Github
`scenario-executions`	Sync execution history (run logs) for each scenario in a team	Sync	🔗 Github
`scenarios`	Sync scenarios for a team	Sync	🔗 Github
`teams`	Sync teams across accessible organizations.	Sync	🔗 Github

Access requirements

Pre-Requisites	Status	Comment
Paid dev account	❓
Paid test account	❓
Partnership	❓
App review	❓
Security audit	❓

Setup guide

No setup guide yet.

Need help getting started? Get help in the community.

Contribute improvements to the setup guide by editing this page

Useful links

How to generate an authentication token
Make Authentication
Make API-rate limiting
API docs
Contribute useful links by editing this page

API gotchas

When adding a new connection, you will also need to add your environmentUrl, this can be the link to your private instance of Make, for example, development.make.cloud, or the link to Make (with or without the zone, depending on a specific endpoint), for example, eu1.make.com. For more details, check API structure.

Contribute API gotchas by editing this page

Going further

Connect to Make

Guide to connect to Make using Nango Connect.

​Overview

Pre-built tooling

Pre-built integrations

Access requirements

Setup guide

Useful links

API gotchas

​Pre-built tooling

​Others

​Access requirements

​Setup guide

​Useful links

​API gotchas

​Going further

Connect to Make

Overview

Pre-built tooling

Others

Access requirements

Setup guide

Useful links

API gotchas

Going further