Hermoso webhooks: 28 events, signed, and you can resend any delivery
Get a webhook, Slack or Discord alert for 28 Hermoso events, from a post going live to a new lead or a DM, pick exactly which, and resend any delivery from the last 7 days.

Your Zap, your n8n flow or your own server can now hear about 28 things that happen in Hermoso, the moment they happen: a scheduled post went live, a lead form was filled in, a customer sent a DM, an ad was rejected, a video finished rendering. Pick exactly the events you want, and if your endpoint was down, send any delivery again from the last 7 days.
Where alerts go
Each brand has three alert channels, and each one is a URL you paste once:
- Slack: an incoming-webhook URL. The event arrives as a readable message.
- Discord: a channel webhook. Same readable message.
- Webhook: any public HTTPS endpoint, including a Zapier, Make or n8n catch hook. It gets one JSON POST per event.
Hermoso says hello to the URL before saving it, so a dead Slack or Discord webhook is caught on the spot.
The 28 events
| Group | Events | On by default |
|---|---|---|
| renders | render.finished, render.failed | Yes |
| posts | post.published, post.partial, post.failed, post.deleted | Yes |
| approvals | approval.awaiting | Yes |
| watch | watch.finding (new competitor ads) | Yes |
| credits | credits.low | Yes |
| leads | lead.created (Meta, LinkedIn and Snapchat lead forms) | Yes |
| connections | account.connected, account.disconnected, account.broken, account.expiring, account.permissions_changed | Yes |
| adrules | adrule.acted | Yes |
| ads | ad.rejected, ad.delivery_issue, budget.exhausted | Yes |
| whatsapp.template_status | Yes | |
| inbox | comment.received, message.received | Ask for it |
| channel_posts | post.channel.published, post.channel.failed | Ask for it |
| mentions | mention.received | Ask for it |
| reviews | review.received | Ask for it |
| email.replied, email.bounced | Ask for it |
Choose by group, by exact name or by family, such as post.* or account.*. Every event and its fields, with a sample body, is in the alert events reference.
Built for real receivers
- Signed. Deliveries follow Standard Webhooks:
webhook-id,webhook-timestampandwebhook-signatureheaders, an HMAC-SHA256 over the raw body. Rotate the secret any time, and the old one keeps signing for 24 hours while you switch. - Retried. A timeout or a 5xx is retried, up to seven attempts over about 16 hours. The
webhook-idstays the same, so dropping a duplicate is one line. - Resendable. Any delivery from the last 7 days can be sent again: same event, same id, same body bytes, freshly signed. Handy after you fix a bug in your receiver.
A worked example
A small agency runs eight client brands. They want a row in a Google Sheet for every lead, and a ping in the team's Slack whenever a scheduled post fails anywhere.
On each brand they paste an n8n webhook URL and keep only leads, and point the Slack channel at post.failed and post.partial. On Monday their n8n server is down for an hour during a deploy. Three lead.created deliveries fail. Hermoso retries them, and the one that ran out of patience while they were still fixing things they resend from the channel's card. Same body, same id, so the Sheet gets each lead exactly once.
Set it up in the app
- Open Connectors and choose the Slack, Discord or Webhook card.
- Paste the URL. For a webhook, copy the signing secret that starts with
whsec_: it is shown once. - Pick the events and send a test. To resend, open the card and choose the delivery under Send one of these again.
Or ask ChatGPT or Claude
With Hermoso connected to ChatGPT or Claude, one sentence does it: Send new leads and failed posts to my webhook at https://hooks.example.com/hermoso, and resend yesterday's failed lead delivery.
The tools are set_alert_events, list_alert_settings, send_test_alert, redeliver_webhook and rotate_webhook_signing_secret, and all of them are free. More: the alerts docs, the event reference and the changelog.
Questions people ask
What events can a Hermoso webhook send?
28 events in 15 groups: renders, posts, approvals, competitor-watch findings, low credits, new leads, account connections, ad rules, ad rejections and delivery issues, WhatsApp template status, comments and messages, per-channel posts, mentions, reviews, and email replies and bounces.
How do I verify a Hermoso webhook?
Each delivery is signed the Standard Webhooks way. Compute an HMAC-SHA256 of id.timestamp.body with your whsec_ secret and compare it to the webhook-signature header, using the raw body before any JSON parsing.
Can I resend a webhook delivery?
Yes. Any delivery from the last 7 days can be sent again with the same event, id and body, signed with a fresh timestamp, from the channel card in the app or with redeliver_webhook.
Does Hermoso retry failed webhooks?
Yes. A timeout, a 5xx, 408, 425 or 429 is retried up to seven attempts over about 16 hours. Other 4xx answers refuse that one event without turning the channel off.
Can alerts go to Slack or Discord instead?
Yes. Paste a Slack incoming-webhook URL or a Discord channel webhook and the same events arrive as readable messages.