Skip to main content
Nylon sends six events. Three are about a post finishing, three are about a connected account changing.

​
Post events

The three are mutually exclusive — exactly one fires per post. post.partially_published is the one that catches people out. A post going to four accounts is four independent attempts, and three succeeding while one fails is a normal outcome, not an edge case. If you retry the whole post on this event you will publish twice on the three that worked.
You do not need these for posts you publish yourself and wait on — the API response already told you. They matter for scheduled posts, where nothing of yours is waiting.

​
Account events

profile.needs_attention is the one worth wiring up first. It is how you tell a user their account needs reconnecting before their next scheduled post fails, rather than after. profile.connected fires on a reconnection too, so it doubles as the “they fixed it” signal — use it to clear whatever warning you showed.

​
Choosing a subset

An endpoint with every event ticked is stored as “no filter”, which means it also receives event types Nylon adds later. An endpoint with a named subset receives exactly that subset and nothing new. Pick deliberately:
  • Leave everything ticked if your receiver ignores events it does not recognise. You get new capabilities for free.
  • Choose a subset if an unknown event type would break your handler.
Both are fine; the failure mode is choosing “all” and then writing a handler that throws on anything unexpected.

​
Filtering the delivery log by event

Open an endpoint from the Webhooks list and the delivery log underneath filters by event and by status — useful for answering “did any profile.needs_attention go out this week” without searching your own logs.

Payload shapes

What each event carries, and the envelope around it.

Deliveries and failures

What happens when your endpoint does not answer.