Zapier
Fire a Zap with a payload - reach anything a Zap can reach from an automation.
Connect one Zap by its Catch Hook URL and hand it data from an automation or an agent: send a JSON object (or a raw body, for a Catch RAW Hook Zap) and Zapier runs the Zap's action steps - Slack, Sheets, a CRM, or anything else in its app directory. This is a one-way door: Zapier answers with a request id and nothing the Zap produced, so a fire is never proof the Zap ran. The hook URL is the credential; it is stored encrypted and never appears in a result, an error or a log line.
How you connect it
Credentials
Paste the credentials Zapier gives you, such as an API key or token, into the connection form. They are stored encrypted and never shown again.
The setup guide in the manual covers every step, and each tool in full.
What agents can do with it
3 tools for your agents to use.
Reads 1
Read-only: these look things up.
- Describe Zap
Changes 2
These can create, update, send or delete.
- Trigger Zap
- Trigger Zap with a raw body
Any of these can be set to wait for a person’s approval before it runs.
Put it to work
See what an agent could do in Zapier for you.
Bring the job, the systems it touches, and the decisions that need a person.