Webhooks

PodcasterPlus sends webhooks through the automation system: a Webhook step in an automation makes an HTTP request to your endpoint whenever the automation runs. That's how you connect podcast events (a booking confirmed, an episode published, a download milestone) to Zapier, Make, n8n, or your own backend.

There is no separate webhook subscription API. If you want an HTTP callback, you build an automation with a Webhook step.

Add a webhook step

1. Go to Automations in your podcast's sidebar and click New Automation.
2. Configure the trigger you want to react to.
3. Add the Webhook step from the Actions group in the step library.

The flow builder guide covers the builder itself; webhook allowances start on paid plans (see limits below).

Configure the request

A Webhook step has four settings:

Setting	What it does
Webhook URL	Where to send the request.
HTTP method	POST (default), PUT, or PATCH.
Custom headers	Optional JSON object of extra headers, e.g. an authorization header.
Payload template	The JSON body. Use Insert Tag to drop any magic tag at the cursor.

Magic tags are replaced at execution time in the URL, in header values, and in the payload. Inside the payload, tag values are JSON-escaped, so quotes and newlines in real data can't break your JSON. A tag with no value for that run becomes an empty string.

Every request carries these defaults (your custom headers can add to or override them):

Content-Type: application/json
User-Agent: PodcasterPlus-Automation/1.0

Know the payload shapes

Your template, filled in. Normally your endpoint receives exactly the JSON you wrote in the payload template, with the magic tags replaced.

The fallback payload. If the step has no template, or the template isn't valid JSON after the tags are filled in, PodcasterPlus sends a standard payload instead:

{
	"event": "automation_trigger",
	"timestamp": "2026-07-11T12:00:00.000Z",
	"context": {
		"podcast_name": "The Creative Hour",
		"episode_title": "How to Build a Successful Podcast",
		"guest_first_name": "Sarah",
		"...": "every magic-tag value for this run, keyed by tag name"
	}
}

context contains the run's full magic-tag data. For bookings with several attendees it also includes guests (the full attendee roster as structured objects) and primary_guest, so consumers that need per-attendee data can read them from the fallback payload.

Validate your template

Test the automation after saving (the Test button) and check the delivery in run history. If your endpoint received the fallback payload instead of your template, the template wasn't valid JSON once the tags were filled in.

Understand delivery behavior

All verified behavior of the delivery pipeline:

• Timeout: requests time out after 30 seconds.
• Success: any 2xx response counts as delivered.
• Failure: a non-2xx response, an invalid URL, a network error, or a timeout marks the step as failed. The response status and body are recorded with the run.
• No retries: a failed delivery is not retried. Each webhook step sends at most one request per automation run.
• Inspection: open run history and view a run's Execution Details to see each webhook's result, including the response your endpoint returned.

Authenticate the requests yourself

Requests are not signed, and there is no shared-secret verification scheme. To authenticate PodcasterPlus at your endpoint, put a secret in Custom headers:

{
	"Authorization": "Bearer your-secret-token"
}

Treat the URL and headers as secrets if they contain credentials; anyone with edit access to your automations can see them.

Respect the monthly allowance

Webhook calls are metered per account, per calendar month:

Plan	Webhook calls per month
Free	Not included
Creator	1,000
Studio	5,000
Production House	20,000
Enterprise	100,000

Webhooks are a paid feature: the Free plan's allowance is zero, so a Free account's webhook step never sends. Once an account exhausts its allowance, further webhook steps are skipped, not queued; the skip is recorded in run history with the reason. Allowances reset on the 1st of the month, and the Plan Limits page has the full matrix.

What's Next?

• Flow builder: build the automation around your webhook step.
• Magic Tags List: everything you can put in a payload.
• Run history: inspect deliveries, responses, and skips.