Trigger Metronomes from GitHub webhooks
/v1/metronomes/github/inboundWebhook endpoint for GitHub repository events. Published workflows with GitHub trigger nodes match on the configured event type and optional repository, branch/ref, actor, action, and payload filters. If webhook signature verification is configured on the backend, GitHub signatures in x-hub-signature-256 are verified. For internal testing, callers may also provide a matching 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.
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| secret | query | string | No | — |
| Name | Location | Type | Required | Description |
|---|---|---|---|---|
| x-github-event | header | string | No | — |
| x-github-delivery | header | string | No | — |
| x-hub-signature-256 | header | string | No | — |
| x-computer-agents-webhook-secret | header | string | No | — |
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| action | string | No | — |
| repository | object | No | — |
| sender | object | No | — |
| ref | string | No | — |
| issue | object | No | — |
| pull_request | object | No | — |
| comment | object | No | — |
| release | object | No | — |
| workflow_run | object | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
| Field | Type | Required | Description |
|---|---|---|---|
| success | boolean | No | Whether the request succeeded. |
| object | string | No | — |
| matched_count | integer | No | — |
| data | object[] | No | — |