Triggering Agents with Webhooks
Agent Webhooks provide a powerful mechanism to trigger an agentโs execution from external systems. Unlike the direct API which provides an immediate response, webhooks are designed for asynchronous operations. When you call a webhook, DocsGPT enqueues the agentโs task for background processing and immediately returns a task_id. You then use this ID to poll for the result.
This workflow is ideal for integrating with services that expect a quick initial response (e.g., form submissions) or for triggering long-running tasks without tying up a client connection.
Each agent has its own unique webhook URL, which can be generated from the agentโs edit page in the DocsGPT UI. This URL includes a secure token for authentication.
API Endpoints
- Webhook URL:
http://localhost:7091/api/webhooks/agents/{AGENT_WEBHOOK_TOKEN} - Task Status URL:
http://localhost:7091/api/task_status
For DocsGPT Cloud, use https://gptcloud.arc53.com/ as the base URL.
For more technical details, you can explore the API swagger documentation available for the cloud version or your local instance.
The Webhook Workflow
The process involves two main steps: triggering the task and polling for the result.
Step 1: Trigger the Webhook
Send an HTTP POST request to the agentโs unique webhook URL with the required payload. The structure of this payload should match what the agentโs prompt and tools are designed to handle.
- Method:
POST - Response: A JSON object with a
task_id.{"task_id": "a1b2c3d4-e5f6-..."}
cURL
curl -X POST \
http://localhost:7091/api/webhooks/agents/your_webhook_token \
-H "Content-Type: application/json" \
-d '{"question": "Your message to agent"}'Triggering with GET (query parameters)
The webhook listener also accepts GET requests, mapping the query string to the payload. This is handy for systems that can only issue a simple GET (for example a โping this URLโ integration):
curl "http://localhost:7091/api/webhooks/agents/your_webhook_token?question=Your+message+to+agent"As with POST, the response is a JSON object containing the task_id.
Preventing duplicate triggers (Idempotency-Key)
To make a trigger safe to retry, send an optional Idempotency-Key header. If the same key is seen again within 24 hours, DocsGPT does not enqueue a second task โ it returns the original task_id instead. This prevents a retried or double-fired webhook from running the agent twice.
curl -X POST \
http://localhost:7091/api/webhooks/agents/your_webhook_token \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-4567-created" \
-d '{"question": "Your message to agent"}'Step 2: Poll for the Result
Once you have the task_id, periodically send a GET request to the /api/task_status endpoint until the task status is SUCCESS or FAILURE.
status: The current state of the task (PENDING,STARTED,SUCCESS,FAILURE).result: The final output from the agent, available when the status isSUCCESSorFAILURE.
cURL
# Replace the task_id with the one you received
curl http://localhost:7091/api/task_status?task_id=YOUR_TASK_ID