Webhooks
Send destination publishing updates to a receiver you control.
Do you need this?
Use a webhook when another app should react to a publishing update. You do not need one to schedule posts or receive Nuntio’s own notifications. This needs a one-time setup by the person who manages your automations.
Choose where updates go
Ask that person for a secure receiving address. It must check that updates came from Nuntio and ignore repeats. A Slack or Discord incoming-webhook address cannot do this on its own; use a receiver in between.
Connect
- As a workspace owner or admin, open Settings → Webhooks.
- Enter a name you will recognize and the receiving address, then choose Create. Confirm your identity if asked.
- Save the key shown once and give it privately to the person setting up the receiver. Never put it in a chat message or support request.
- Have that person send a sample through the receiver. Check the result in the receiving app before relying on it.
What gets sent
Each update describes one destination’s publishing result. It contains platform and status information, not the post text, media or passwords. Updates can arrive more than once or out of order.
| Update | Meaning |
|---|---|
| Published | The platform confirmed the publication. Visibility and moderation can still affect who sees it. |
| Failed | A delivery could not finish. A retry may still be planned; the receiver must check the saved retry information. |
| Needs verification | The post may already be live. Check the platform; never trigger an automatic replacement post. |
| On hold | Publishing is waiting for a person to act. |
| Cancelled | The scheduled delivery was cancelled. |
Check the connection
Choose History beside the receiving app. Delivered means that app accepted the update; check the app itself to confirm the message or task completed. A failed webhook does not mean the social post failed.
Fix a problem
If updates stop, check History and ask the person managing the receiver to check its address and key. Rejected updates, including a wrong signature or invalid data, are not retried. Temporary network failures or a busy or unavailable receiver can retry after 5, 15 and 60 minutes, or later if it asks Nuntio to wait. Repeated failures can pause the connection. Disable an active connection and create a new one with a new key to reconnect. Old updates are not automatically replayed. Up to ten connections can be active.