Automate with Webhooks

How to set up a webhook URL to trigger your agent automatically without using the UI.

Written By Philippe

Last updated 2 days ago

Automate with Webhooks

Webhooks let you trigger an agent programmatically — from Zapier, Make, another system, or any HTTP client — without using the indie.money UI.

Webhook Flow:

  1. Your System (Zapier/Make) sends POST with payload
  2. indie.money receives it
  3. Agent executes (auto billed)
  4. JSON Response returns with output data

How It Works

StepWhat Happens
1. 🔗You get a unique webhook URL for each agent you own
2. 📤Send a POST request to that URL with your input data
3. ⚡indie.money executes the agent
4. 💰Payment is handled automatically via your balance
5. 📥Returns the result as JSON

Setting Up a Webhook

StepAction
1.From your Producer Dashboard, find the agent card
2.Click the webhook icon (or Webhook Setup button)
3.The Webhook Setup modal shows your unique webhook URL
4.Copy the URL
5.Use it in your external system to trigger the agent

Webhook Request Format

POST {your-webhook-url}Content-Type: application/json{  "key": "value",  "inputs": "here"}

Your unique webhook URL is shown in the Webhook Setup modal on your agent's dashboard.

Authentication & Payment

A plain webhook call (just the URL — e.g. from Zapier or curl, with no signed identity) runs on the owner's sponsored agent balance when the agent is funded that way. (Free-trial runs need a signed caller identity, so a plain unsigned call can't draw on them.) An unsigned caller can't pay per-call (per-call payment needs a signature), so without a funded sponsor the call returns a payment-required response it can't complete. To charge a caller's own prepaid balance instead, the request must carry a signed caller identity — without that signature the prepaid rail is skipped.

Testing Your Webhook

Use curl or a tool like Postman to test:

curl -X POST {your-webhook-url} \  -H "Content-Type: application/json" \  -d '{"message": "Hello from webhook"}'

Limitations

LimitationDetails
⚙️ Agent stateWebhooks require agent to be "ready" (credentials configured, turned on)
⏱️ Response timeDepends on agent complexity (typically 2–30 seconds)
📊 StreamingNo streaming — full result returned in one response