Webhooks

Where: Settings, Webhooks

A webhook is an HTTP callback Nitty Music Social fires when a post publishes. Use it to mirror content into Slack, log posts into a spreadsheet, trigger an automation, or update your own system.

Adding one

1

Name it

For your own reference in the list.

2

Give it a URL

Where Nitty Music Social should POST.

3

Choose the scope

All integrations, or a specific set of channels. Scoping by channel is how you route a client's posts to that client's system.

4

Send Test

Fires a test call immediately, so you can confirm the endpoint is reachable and see the payload shape before anything real depends on it.

5

Save

The header shows how many webhooks you have against your allowance.

Building the receiver

Always Send Test first and capture the body: that is the contract, and it is more reliable than any description here.

Two habits worth having:

• Return 2xx quickly, then do the work asynchronously. A slow endpoint is indistinguishable from a broken one.
• Be idempotent. Treat a repeated delivery as a no-op rather than posting twice.

When a webhook stops firing

The endpoint is not publicly reachable

Nitty Music Social calls from its servers, so localhost and private network addresses will not work. Use a tunnel while developing.

The endpoint is returning an error

Check your own logs first, then use Send Test to reproduce.

The webhook is scoped to the wrong channels

A webhook scoped to specific integrations stays silent for everything else. Re-check the scope.

Your plan changed

Downgrading below the webhook allowance can take webhooks out of service.

Related

Webhooks tell you when Nitty Music Social acted. To make Nitty Music Social act, use the Public API or MCP.