Integration · Automation
AI agents for Make
Start a Make scenario by sending it data, through the address of a scenario that begins with a Webhooks "Custom webhook" trigger.
- Actions
- 1
- Read
- 0
- Write
- 1
Actions
What your agents can do in Make
1 action. Each one is a tool your agents can call and a step your workflows can run.
Read 0
Look things up. Nothing changes.
This tool has no read actions.
Write 1
Create, change or send.
Send data to a scenario
Sends one JSON object to the Make scenario behind this webhook, which runs the scenario with the object's fields as the webhook's output.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste a webhook address you create in Make. The address is the credential, and calls go only to Make's own servers.
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Let an agent update Make
Have the agent send data to a scenario in Make as part of a larger task. Turn on approval and a person signs off on each change first.
- 02
Share what it finds in Slack
Give one agent Make and Slack: it can send data to a scenario in Make and post a summary to a Slack channel in the same run.
- 03
Run it as a workflow step
Add "Send data to a scenario" to a workflow, and it runs in Make the same way every time, with or without an agent.
Works well with
More Automation tools
- Zapier1 actionStart a Zap by sending it data, through the webhook URL of a Zap that begins with the Webhooks by Zapier "Catch Hook" trigger.
- n8n1 actionStart an n8n Cloud workflow by sending it data, through the production URL of its Webhook trigger.
- Pipedream1 actionStart a Pipedream workflow by sending it data, through the endpoint URL of a workflow that begins with an HTTP / Webhook trigger.
- UiPath9 actionsRun and watch UiPath robots in Automation Cloud Orchestrator.
- Power Automate7 actionsSee and manage Microsoft Power Automate flows stored in a Dataverse environment.
- Home Assistant9 actionsRead the devices and sensors in a Home Assistant home (states, history, logbook, calendars, templates) and control lights, switches, climate, media players and other everyday devices through Home Assistant actions.
FAQ
Make and MyDeepAgents
Can MyDeepAgents connect to Make?
Yes. The Make connector has 1 action, which makes a change. Your agents can call it as a tool, and your workflows can run it as a step.
How do I connect Make?
Paste a webhook address you create in Make. The address is the credential, and calls go only to Make's own servers. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Make without asking?
Only if you let it. Its one action that changes data can be set to wait for a person's approval before it runs.
Can I use Make in workflows as well as agents?
Yes. Every Make action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Make to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.