Noticeable
Day 44 after signup
Webhooks: get Noticeable events on your own servers
Why it works
- Open with the core capability and the practical problem it solves before moving into technical detail.
- Use concrete use cases and ordered setup steps to make an announcement useful to both prospective and existing users.
- Place security, reliability, and plan availability near the end so readers can assess implementation requirements before taking action.
How it is built
- Feature introduction
- Use case examples
- Event types overview
- Setup instructions
Email copy
Webhooks: get Noticeable events on your own servers You can now send what happens in your Noticeable project straight to your own servers. Register a webhook endpoint, choose the events it cares about, and Noticeable posts each one to it within seconds of it happening. No more polling the API or exporting lists by hand. What you can build with them Keep your CRM in sync. Add a contact when someone subscribes to your emails, and update it when they unsubscribe. Keep your lists clean. Flag an address in your own database as soon as an email to it hard bounces or is reported as spam. React to your own announcements. Rebuild a static site, post to a chat channel or notify your support team when a publication is published, changed or deleted. Keep a copy. Mirror your publications into another system, with the attributes that changed in each update. Events you can receive Events are grouped in two categories, and an endpoint receives only the ones you select. Category Events Email subscriptions Subscribed, Unsubscribed, Hard bounce, Soft bounce, Spam complaint, Spam complaint removed Publications Publication created, Publication updated, Publication deleted Each event carries its details: the subscriber and where the subscription came from, the email that bounced or was reported, or the publication as it is after the change. More categories will join these over time. Set up an endpoint Open your project in the dashboard and go to Integrations, then click Configure on the Webhooks card. Click New Endpoint, enter the https address of your server and select the events to send it. Save, and copy the signing secret shown. It is displayed only once. On the endpoint's Deliveries page, click Send test event to post a sample of any event to your server and check your code before real events arrive. While you choose events, the page shows an example of the exact request your server will receive, so you know the shape of the payload before writing a line of code. Reliable and secure by design Signed requests. Every request is signed with the endpoint's secret, following the open Standard Webhooks specification. Verify them with any Standard Webhooks library, in the language of your servers. You can roll the secret at any time. Automatic retries. When your server is down or answers with an error, the delivery is retried with growing delays for about three days. An endpoint that keeps failing is marked as failing in the dashboard so you notice it. A delivery log. The Deliveries page of each endpoint lists what was sent, when, and how your server answered. Deliveries are kept for 30 days and you can find one by the webhook-id header your server received. Avoid loops when you write back Changes made through the API send events too, including your own. Say your server labels publications automatically: on each Publication updated, it reads the content and adds the Fix label through the API when the text mentions a bug. Adding a label is itself an update, so Noticeable sends a new Publication updated event, your server labels the publication again, and so on without end. A two-way sync between Noticeable and another tool runs into the same trap. To break the loop, add a Noticeable-Reference header of your choice to your API calls, such as Noticeable-Reference: auto-labeler. Every event caused by those calls carries that value in data.request.reference, so your server can recognize its own changes and skip them: if (event.data.request?.reference === 'auto-labeler') { return // our own change: nothing to do } Changes made by your team in the dashboard carry no reference, so they still reach your server as usual. Availability Webhooks are available today on paid plans, per project: 1 endpoint on Starter, 3 on Growth, 5 on Business and 10 on Enterprise. They are not included in the Free plan. Already using our Zapier integration? Nothing changes: your Zaps keep working as before. Open Dashboard You’re receiving this em