Skip to content
Home

Send leads to Zapier or Make

For your IT person · About 10 minutes

Most firms don’t need this: every lead is in My leads on Protection Connect, and HubSpot, Pipedrive, Salesforce, Zoho CRM and FLG connect straight from the Integrations page. This page is for whoever sets up your firm’s Zapier or Make, to send leads somewhere else.

How it works

  1. In Zapier, create a Zap with the trigger Webhooks by Zapier, then Catch Hook (a paid Zapier plan). In Make, add a Custom webhook (Make’s free plan works).
  2. Copy the link it gives you, and paste it on Protection Connect’s Integrations page: Use Zapier or Make? For your IT person. Press Save.
  3. Press Send test there. A made-up lead for Test Person arrives, with every field below filled in, so you can match each one to your system.
  4. Add the action that adds the lead to your system, and turn the Zap or scenario on.

Leads start going to a new Zapier or Make link an hour after it is saved, and every lead stays in the firm’s My leads tab. If a lead can’t be sent, we keep trying for 24 hours, and we email the firm’s owner and admins if the link keeps failing.

What each lead contains

Each new lead is sent as JSON, in an HTTP POST: {event, api_version, id, test, created_at, lead}. event is lead.delivered for a new lead (test for Send test). id is the same on every retry of one lead, so you can drop repeats. lead holds what the firm sees when it opens the lead:

  • ref: the Protection Connect reference, for example PC-7K3Q9X2M.
  • brand, brand_label: the website the customer used (for example 50Life).
  • product, product_label: what they asked about (for example Over 50s life insurance). For critical illness enquiries, product stays life and product_label gives the cover type (for example Life and critical illness).
  • title, first_name, last_name, phone (in international form, +447700900123), email, postcode (empty on new leads because our websites no longer ask for it; don’t make it required).
  • age, smoker_status (smoker or non_smoker, only when the customer shared it).
  • applicant_type: single or joint. On a joint lead, partner_age and partner_smoker_status describe the partner (never a name or contact details), and cover_gbp is the cover for each person, not the total.
  • cover_gbp, term_years: the cover and term asked about (no term for whole-of-life cover).
  • price_pence, price_gbp: what your firm paid for the lead.
  • source_label: how the customer found the website.
  • consented_at, contact_methods: when the customer agreed to be contacted about this enquiry, and how (phone, email). It is not consent to marketing.
  • repeat_for_firm: true when the same person has enquired with your firm before.
  • dashboard_url: the lead in Protection Connect.
  • Income protection leads from LifeAdviser can also carry employment_status, work_type, annual_income_band, monthly_benefit_band, deferred_period and benefit_period; critical illness leads can carry cover_type. Each field contains a code, with the dashboard wording under the same name plus _label (for example employment_status_label). A field is left out when the customer was not asked.

Two more events tell your system about a lead it already has: lead.withdrawn (the customer asked for their details to be erased: delete the lead from your systems) and lead.credited (we credited the lead to the firm).

Checking it came from us

Zapier and Make don’t need this. If your own system receives the leads directly, every request carries X-PC-Timestamp and X-PC-Signature: v1=<HMAC-SHA256 of timestamp + "." + body>, made with a signing secret shown once when the address is saved. Reject requests more than 5 minutes old.

Questions? Email support@protectionconnect.co.uk.