Webhooks and messaging — Voidhash Docs

MCP tools to manage webhooks and deliveries, send push notifications and run automations.

These tools let an agent manage the webhooks Voidhash sends to your backend, send push notifications, and build and run automations.

Webhooks

Key access: Webhooks. See Webhook delivery.

Tool	What it does
`list_webhooks`	Webhooks with their events, environment and health.
`get_webhook`	One webhook with its recent deliveries.
`create_webhook`	Adds a webhook and returns its signing secret once.
`update_webhook`	Changes a webhook, or turns it on or off. Asks first when turning it off or moving it to test.
`delete_webhook`	Deletes a webhook and its history. Asks first.
`rotate_webhook_secret`	Replaces the signing secret. Asks first.
`test_webhook`	Sends a signed `test.ping` event, waiting up to 10 seconds for the answer.
`list_webhook_failures`	Failed deliveries across webhooks, newest first.
`get_webhook_delivery`	One delivery with every attempt and the body sent.
`retry_webhook_delivery`	Sends failed deliveries again.

Push notifications

Push notifications are in early access. Key access: Notifications; Send notifications to send. Push credentials are set up in Studio or the CLI. See Push notifications.

Tool	What it does
`send_push_notification`	Sends a notification to up to 100 people. Asks first.
`list_push_notifications`	Sent notifications and how their deliveries went.
`list_push_deliveries`	How one notification reached each device.

Automations

Automations are in early access. Key access: Automations; Activate automations to activate, pause, archive, enroll and manage runs. See Automations.

Tool	What it does
`get_automation_catalog`	Every trigger and step type, and what rules and templates can read.
`list_automation_cohorts`	The cohorts a scheduled automation's audience can name.
`list_automations`	Automations with their status and what's wrong with each draft.
`get_automation`	One automation's draft, problems and how many people reached each step.
`create_automation`	Saves a new automation as a draft.
`update_automation`	Saves changes to the draft.
`test_automation`	Walks the draft for one person without sending or changing anything.
`activate_automation`	Publishes the draft and makes it live, or resumes it. Asks first.
`pause_automation`	Stops an active automation at once.
`archive_automation`	Ends an automation and cancels its runs. Asks first.
`unarchive_automation`	Brings an archived automation back as a draft.
`enroll_in_automation`	Takes one person through an active automation now. Asks first.
`list_automation_runs`	Who went through an automation and where they are.
`get_automation_run`	What happened to one person, step by step.
`cancel_automation_run`	Takes one person out of a flow.
`retry_automation_run`	Retries a failed run from the step it failed at.

Example

Our backend missed purchase events last night. Find out why, and resend them once it's fixed.

The agent calls list_webhook_failures and get_webhook_delivery to see how your endpoint answered, then retry_webhook_delivery.

Next steps

Webhook delivery: endpoints, retries and the payload.
Push notifications: set up APNs and FCM.
Automations: triggers, steps and runs.