PartnerPage has no built-in app for HubSpot, Zapier, Make or n8n. You connect these tools with webhooks, which send each event in your directory to a URL your tool gives you, or with the PartnerPage API. This article is for vendors who run a directory; partners who want their own contact requests in their CRM use the Lead webhook instead.

Who can do this: Admin role for directory webhooks (Managers can view webhook events and logs); Admins for API keys · Availability: directory webhooks are available on request: contact PartnerPage support. The API and the partner Lead webhook are available on all directories.

Ways to connect PartnerPage to other tools

The following table lists the ways to send PartnerPage data to HubSpot, Zapier, Make, n8n or any other tool.

Option	Who sets it up	What it sends	Where
Directory webhooks	The vendor	Eight directory events, such as `contact_request_created` (a visitor sends a partner a contact request) and `partner_application_created`	Directory sidebar > Webhooks > Events
Lead webhook	Each partner	Every contact request on the partner's own profiles	Settings > Developers in the partner's dashboard
PartnerPage API	Your developer	Any directory data, read or changed on demand	API keys in Settings > Developers; reference at https://docs.partnerpage.io
CSV export	The vendor's team	A file you import by hand	Export on Contact requests and other lists

Example: send each contact request to HubSpot through Zapier

This example sends every contact request in your directory to Zapier, which then creates the contact in HubSpot. It uses a directory webhook with the event trigger contact_request_created.

To send contact requests to HubSpot through Zapier:

In Zapier, create a Zap with the trigger Webhooks by Zapier and the event Catch Hook. Copy the webhook URL Zapier gives you.
In PartnerPage, open your directory and go to Webhooks > Events.
Click Create event.
Enter a Name, such as "Contact requests to HubSpot".
Paste the Zapier URL into Subscriber URL.
In Event trigger, choose contact_request_created.
Click Save.
Open a partner profile in your directory and send the contact form with your own details.
In Zapier, find the test request, then add a HubSpot action that creates or updates a contact and map the fields.

The following table lists the fields you'll usually map from a contact_request_created delivery.

Field in the delivery	What it holds
`contact_request.first_name`, `contact_request.last_name`	The visitor's name
`contact_request.email`, `contact_request.phone`	The visitor's email and phone number
`contact_request.company_name`, `contact_request.company_website`	The visitor's company
`contact_request.comments`	The visitor's message
`contact_request.entry.title`	The partner the request was sent to
`contact_request.utm_query_params`	Campaign (UTM) parameters from the page, if any
`custom_fields`	Answers to your custom form questions, each with `export_label`, `internal_label` and `text_value`
`directory_contact_request_url`	A link to the request in your PartnerPage dashboard

With Make, start the scenario with a Custom webhook module and copy its URL. With n8n, add a Webhook node, set the method to POST and Respond to "Immediately", activate the workflow and copy the production URL. The PartnerPage steps stay the same.

Send to HubSpot without Zapier, Make or n8n

PartnerPage sends every webhook in its own fixed JSON format, and the format can't be changed. HubSpot can't read that format as a form submission on its own, so a tool such as Zapier, Make or n8n, or a small service your developer writes, has to map the fields first.

What to know about directory webhooks

Directory webhooks are switched on by PartnerPage. When they're on, Webhooks appears in your directory's sidebar. If you don't see it, contact PartnerPage support.
One URL per event. Each directory has one subscriber URL per event trigger. To send one event to several tools, send it to one Zap or workflow and pass it on from there.
No automatic retry. Your tool must answer within 15 seconds with a 2xx status. A delivery that fails isn't sent again, so check Webhooks > Logs from time to time; its errors view shows failed deliveries.
Every delivery is signed. The X-Webhook-Signature header lets a developer check that a delivery came from your directory. The Signing secret is on Webhooks > Events.

Full setup steps are in Set up webhooks for your directory.

Partners: send your own contact requests to your CRM

A partner who wants the contact requests they receive in their own HubSpot or other CRM adds a Lead webhook in Settings > Developers. It covers every profile the partner's organization has, in every directory. Directory owners can switch this off for their directory in Customizations > Configuration > Partner lead delivery. See Send new leads to your own tools with a webhook.

Use the PartnerPage API instead

The PartnerPage API suits jobs a webhook can't do, such as reading partners on a schedule or closing a contact request from your CRM. Turn on API access and create a key in Settings > Developers, then follow the reference at https://docs.partnerpage.io. See Turn on API access and create API keys.

What you can't do

Install a PartnerPage app from the HubSpot, Zapier, Make or n8n marketplaces: none exists.
Sync both ways automatically. Webhooks only send data out of PartnerPage; changes in your CRM come back only through the API.
For Salesforce, PartnerPage has a native connection. See Connect Salesforce.

Connect HubSpot, Zapier, Make or n8n