Webhooks

MAEL exposes two inbound webhook endpoints; it does not (yet) send outbound webhooks to your own systems — workflow state changes are consumed by polling the Workflows API or the dashboard’s WebSocket today.

Slack interactive actions

POST /api/v1/webhooks/slack/actions receives approve/reject button clicks from an approval notification. Configure your Slack app’s Interactivity request URL to point at this endpoint; MAEL verifies the request signature before processing anything.

# What the workflow engine does on receipt (illustrative, not a webhook
# you write yourself):
#   1. Verify the Slack signing secret (timing-safe comparison)
#   2. Resolve the approval request_id from the button's callback payload
#   3. POST-equivalent to /workflows/runs/{run_id}/approvals/{request_id}/respond
#   4. Update the Slack message to reflect the decision

WordPress webhook receiver

POST /api/v1/webhooks/wordpress/{tenant_id} accepts WordPress-side events for a specific tenant’s connected site — signature-verified the same way.

Building your own outbound notifications today

Until outbound webhooks ship, poll GET /api/v1/workflows/runs/{run_id} or GET /api/v1/workflows/approvals on whatever interval your integration needs — both are cursor-paginated and cheap to poll.

Roadmap

Content Generation Troubleshooting

Get Started

Architecture

Deployment

SDK

CLI

Guides

Examples

Resources

Slack interactive actions

WordPress webhook receiver

Building your own outbound notifications today

Roadmap

​Slack interactive actions

​WordPress webhook receiver

​Building your own outbound notifications today

Roadmap

Slack interactive actions

WordPress webhook receiver

Building your own outbound notifications today