Trigger Metronomes from inbound email
POST
/v1/metronomes/email/inboundWebhook endpoint for mail providers that forward messages addressed to workflow-scoped @metronome.computer-agents.com inboxes. If METRONOME_EMAIL_WEBHOOK_SECRET is configured, callers must provide the same value in the x-computer-agents-webhook-secret header or secret query parameter.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
None.
Query parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| secret | query | string | No | — |
Header parameters
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| x-computer-agents-webhook-secret | header | string | No | — |
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| to | string | No | — |
| recipient | string | No | — |
| from | string | No | — |
| subject | string | No | — |
| text | string | No | — |
| html | string | No | — |
| attachments | object[] | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Inbound email processedapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| success | boolean | No | Whether the request succeeded. |
| object | string | No | — |
| matched_count | integer | No | — |
| data | object[] | No | — |
400Invalid inbound email payload
None.
401Invalid webhook secret
None.
Trigger Metronomes from inbound email
Loading...
Response 200
Loading...