Make integration
Visual automation platform (formerly Integromat) for connecting apps and automating workflows. Create, manage, and monitor scenarios, handle data stores, and orchestrate complex integrations. Perfect for no-code automation, business process management, and app integrations.
Say what should happen.
The workflow builds itself.
Common Make use cases
- Debugging
- Cleanup
- Data export
- Data ingestion
- Manual triggers
- Team management
- Scenario inventory
- Storage management
- Webhook management
- Automation creation
What you can do with Make
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Scenario, 7 operations
create_scenarioCreate scenarioPOSTCreates a new automation scenario.delete_scenarioDelete scenarioDELETEPermanently deletes a scenario.get_scenarioGet scenarioGETRetrieves detailed information about a specific scenario.list_scenariosList scenariosGETRetrieves all automation scenarios in a team.run_scenarioRun scenarioPOSTManually triggers a scenario execution.stop_scenarioStop scenarioPOSTDeactivates a scenario so it stops running on its schedule.update_scenarioUpdate scenarioPATCHUpdates an existing scenario's configuration.
Data store record, 2 operations
add_data_store_recordAdd data store recordPOSTAdds a new record to a data store.get_data_store_recordsGet data store recordsGETRetrieves records from a data store.
Execution, 2 operations
get_executionGet executionGETRetrieves detailed information about a specific execution.list_scenario_logsList scenario logsGETRetrieves execution history for a scenario.
Connection, 1 operation
list_connectionsList connectionsGETRetrieves all app connections in a team.
Data store, 1 operation
list_data_storesList data storesGETRetrieves all data stores in a team.
Team, 1 operation
list_teamsList teamsGETRetrieves all teams in an organization.
Webhook, 1 operation
list_webhooksList webhooksGETRetrieves all webhooks in a team.
Make API rate limits
- 60 requests per minute
Limit depends on the organization plan: Core 60/min, Pro 120/min, Teams 240/min, Enterprise 1000/min.
These are the limits Make documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Make documentation for current values.
Use Make from Claude Code, Cursor or Codex
Connect Make in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Make operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Make
- Create your workspace
Sign up free. Nothing to install.
- Connect Make once
Add your Make connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Make integration FAQ
What can you do with the Make integration?
LiveContext exposes 15 operations on Make, covering scenario, data store record, execution and connection. Common uses include Debugging, Cleanup and Data export.
What are the Make API rate limits?
Make documents 60 requests per minute. Limit depends on the organization plan: Core 60/min, Pro 120/min, Teams 240/min, Enterprise 1000/min. Limits are set by Make and can depend on your plan.
