test_dispatch
Test-dispatch a webhook — Send a synchronous test delivery for a webhook using a provided or captured payload, and return the HTTP result so the agent can verify the integration end to end.
Send a synchronous test delivery for a webhook using a provided or captured payload, and return the HTTP result so the agent can verify the integration end to end. This is a REAL delivery, not a dry run — for an internal REST endpoint it can create or modify data (e.g. create a WordPress user) — so it requires confirmation. Any non-2xx response stops the run, and the status and response body come back to the agent so it can fix the mapping or snippet and re-test. Registered as the WordPress Ability flowsystems-webhook-actions/test-dispatch, so external AI tools (Claude Code, Cursor) can call it over MCP, or over the Abilities REST route with a scoped API token.
/ Plan step shape
{ "ability": "test_dispatch", "input": { "webhook_id": …, "trigger": …, "payload": … } }
/ Scope & confirmation
Minimum API-token scope for external (MCP/REST) callers: full. This step always pauses for explicit user confirmation before it runs. External MCP/REST callers get a 428 and must re-send the same call with "confirmed": true.
/ Input fields
| Name | In | Type | Req | Description |
|---|---|---|---|---|
| webhook_id | param | integer | yes | |
| trigger | param | string | — | |
| payload | param | object | — | Optional custom payload, sent as-is. When omitted, the captured example is used with the stored field mapping applied — matching real deliveries. |
/ Examples
Plan step as Build with AI proposes it
{ "id": "step_1", "ability": "test_dispatch", "summary": "…", "input": { "webhook_id": 12, "trigger": "wpcf7_mail_sent" } }
/ Related