Directory webhooks tell your own systems the moment something happens in your partner directory: a new lead comes in, a lead changes status, a partner applies or submits a profile. Each notification is an HTTPS POST with a JSON body, sent to a URL you choose within seconds of the event.

Typical uses are pushing new leads into your CRM, posting to a Slack channel, or starting an automation in n8n, Zapier or Make.

Building the receiving end? The developer pages are in the API docs: Verify and handle webhook deliveries and Directory webhook events and payloads.

Before you start

Webhooks are switched on per directory by PartnerPage. When they are on, Webhooks appears in the left menu of your directory. If you do not see it, message us from the chat in your dashboard.
Your team members need the Webhooks permissions (Events and Logs) in their role to see and manage subscriptions.
You need a URL that can receive the webhook: an endpoint your developers built, or a webhook URL from n8n, Zapier or Make. It must be reachable from the public internet over HTTPS.

Create a subscription

Open your directory in the PartnerPage dashboard and choose Webhooks, then Events.
Click Create event.
Give the subscription a Name for your own reference, for example "New leads to HubSpot".
Enter the Subscriber URL: the HTTPS address we should call.
Pick the Event trigger you want to receive. The Event data sample on the page shows an example payload for the trigger you picked.
Click Save.

Each directory can have one subscriber URL per event trigger. To send the same event to several systems, point the subscription at one endpoint (an n8n or Zapier flow, or your own service) and pass it on from there. You can edit or delete a subscription from the Events list at any time.

Events you can subscribe to

Event trigger	Sent when
`contact_request_created`	A new lead is created for a partner
`contact_request_updated`	A lead is accepted, declined, closed or reopened, or its project status changes
`matchmaking_request_created`	A visitor submits your matchmaking form
`matchmaking_request_updated`	Your team assigns, closes or reopens a matchmaking request, or changes its owner
`partner_application_created`	Someone submits your partner application form
`partner_application_updated`	Your team accepts or declines an application
`partner_get_listed_completed`	A partner completes the Get Listed flow
`profile_submitted_by_entry_owner`	A partner submits a new or edited profile for your review

The fields of each event, with example payloads, are in Directory webhook events and payloads in the API docs.

Your signing secret

Every delivery is signed, so your receiving system can check that it really came from your PartnerPage directory. The secret used for the signature belongs to your directory alone.

Go to Webhooks, then Events. The Signing secret card is at the top of the page. It is shown to team members whose role can edit webhook events.
Copy the secret and store it in your receiving system.
Have your developer check the signature on every request. Verify and handle webhook deliveries in the API docs has the steps and code samples.

To replace the secret, click Regenerate. The new secret applies immediately: deliveries fail the signature check in your receiving system until you update it with the new secret. The card shows when the secret was last regenerated.

If the card says "Not in use yet". Your directory used webhooks before each directory had its own secret, and your deliveries are still signed with the older shared secret. Click Regenerate to switch to your own secret right away, then add it to your receiving system.

Check your deliveries

Webhooks, then Logs, lists every delivery with its timestamp, the subscription name, the event trigger and the HTTP status your endpoint returned. Open an entry to see the response text and the exact payload we sent. Use the errors filter to show only failed deliveries.

A delivery that fails is not sent again. Check the Logs page from time to time, and use the ids in the payload to look up anything you missed in the dashboard.

Let partners receive their own leads

Partners listed in your directory can add a webhook of their own, so the leads they receive from your directory go straight into their CRM. This is on by default. The partner's side is described in Send new leads to your own tools with a webhook.

A partner only receives new leads on their own profiles, with the same details they already see in their PartnerPage dashboard. Nothing that only your team sees is included.
Your own webhooks are not affected. You still receive every event you subscribed to.
To switch it off for your directory, go to Customizations, then Configuration, find Partner lead delivery, turn the toggle off and click Save. Partners keep their webhook, but leads from your directory are no longer sent to it.

Test it

Open a partner profile in your directory and submit the contact form with your own details. Within a few seconds the delivery appears under Webhooks, then Logs, with the status your endpoint returned.

Quick start with n8n, Zapier or Make

n8n. Add a Webhook node, set the method to POST and Respond to "Immediately". Activate the workflow and copy the Production URL into the Subscriber URL field.
Zapier. Create a Zap with the trigger "Webhooks by Zapier", event "Catch Hook", and copy the URL it gives you.
Make. Add a "Custom webhook" module and copy its URL.

Questions? Message us from the chat in your dashboard.

Set up webhooks for your directory