Integrations: outbound webhooks
Send workspace events (post published, account disconnected…) to your own systems as signed HTTPS requests.
Settings → Integrations (address /app/settings/integrations) sends events from this workspace to a URL of yours, for example an automation tool (Zapier, Make, n8n) or your own server. Only Owner and Admin can see and change it.
Step by step: add an endpoint
- Open Settings → Integrations.
- In the first box type your endpoint URL, for example
https://your-system.example.com/omnibrand-hook. It must be https and reachable on the public internet. - In **Events (comma separated, * for all)** type the events you want, or click a suggestion:
*,post.published,post.failed,workspace.created,invitation.accepted,social_account.token_expired,social_account.disconnected. - Click Add endpoint.
- Signing secret (copy now - shown only once): appears with the secret. Copy it into your receiving system now; OmniBrand never shows it again (only its last four characters).
- Click Send test on the endpoint. You see ✓ delivered with the HTTP status your server returned, or ✗ with the reason.
Each endpoint
- The URL and a badge active or disabled.
- "events: … · secret ••••1234", plus "· N consecutive failures" when deliveries are failing.
- The switch Enabled / Disabled pauses or resumes deliveries.
- Send test sends an event named
webhook.test. - Delete removes the endpoint at once.
What your server receives
A POST with a JSON body: id (the event's id - use it to ignore duplicates), event (for example post.published), occurredAt, and data (the event's details). Headers:
X-OmniBrand-Signature:sha256=followed by the HMAC-SHA256 of the raw body, keyed with your signing secret.X-OmniBrand-TimestampandX-OmniBrand-Signature-V2: the HMAC-SHA256 of the timestamp, a dot, and the body - use it to reject old replays.
Answer with any 2xx status within 5 seconds.
If something goes wrong
- Network errors, 5xx and 429 answers are retried up to 3 times within the same delivery; other 4xx answers are not retried.
- Redirects are never followed; register the final URL. The test says Endpoint redirected (HTTP 301)… if yours redirects.
- After 20 consecutive failed deliveries the endpoint is switched to disabled automatically and admins are notified. Fix the receiver, then turn the switch back to Enabled.
Good to know
- An endpoint receives only this workspace's events, plus account-wide events (billing and account events).
- The workspace you are in when you add the endpoint is the one it belongs to.
Checked against the product on Sep 23, 2026