Sending Bark Leads to Found

Last updated: August 3, 2026

Overview

This article explains how to send the leads you purchase on Bark straight into Found as enquiries, using Zapier as the connector.

What is Zapier?

Zapier is an automation tool that connects different apps so they can pass information between each other. Bark doesn't talk to Found directly, so Zapier sits in the middle - every time you purchase a lead on Bark, Zapier automatically forwards the customer's details to Found as a new enquiry.

Before you start

You'll need

A Bark account - the same login you use to view and purchase leads
A premium Zapier account
A Found Pro plan - the enquiry webhook is a Pro feature
Your Found webhook secret - from Settings > Integrations > Enquiry Webhook > Add Connection
The Location ID for the Found location you want to route enquiries to - from Settings > Integrations > Enquiry Webhook > Location Mappings

Which Bark trigger should I use?

Bark offers two lead triggers in Zapier:

New Bark - fires for every lead posted in your service area, before you've purchased it. These don't include the customer's contact details.
New Purchased Bark - fires only when you buy a lead, and includes the customer's name, phone number and email.

Always use New Purchased Bark. Found needs a name and a phone number or email to create an enquiry, so un-purchased Barks would be rejected - and you don't want enquiries you can't contact filling up your pipeline. It also means your reporting in Found reflects the leads you actually paid for.

Step 1: Create your Zap

In Zapier, click Create Zap
Set the Trigger
- App: Bark
- Event: New Purchased Bark
- Connect your Bark seller account when prompted
Test the trigger to confirm Zapier can pull in a sample purchased lead - you'll use it to map fields in Step 3
Set the Action
- App: Webhooks by Zapier
- Event: POST

Step 2: Configure the webhook

Fill in the action fields for your Webhooks by Zapier as follows:

Field	Value
URL	`https://webhooks.foundcrm.care/add-enquiry`
Payload Type	JSON
Wrap Request in Array	No
Unflatten	Yes
Basic Auth	Leave empty

Step 3: Map your Fields

In the Data section of Configure, add the following rows. The keys on the left must be typed exactly as shown - casing and dots:

Key	Value
`locationId`	Paste your Location UUID from Found
`contact.firstName`	Insert the customer's first name from the Bark lead
`contact.lastName`	Insert the customer's last name from the Bark lead
`contact.email`	Insert the customer's email from the Bark lead
`contact.phoneNumber`	Insert the customer's phone number from the Bark lead
`contactMethod`	Type literally: `CONTACT_FORM`
`notes`	Insert the lead's details from Bark - see below

Make the most of the notes field. Bark leads carry useful context - the service requested, the customer's answers to Bark's questions, and the town or postcode. You can combine several Bark fields (with your own labels) in the notes value, so your team sees the full picture on the enquiry without opening Bark.

Optional, for home care providers: add enquiryDetails.type with the value HOME_CARE, and map enquiryDetails.servicePostcode to the postcode from the Bark lead. (Care homes can use CARE_HOME instead.) Leave Found's other care-detail fields unmapped - they only accept fixed values, and Bark's free-text answers belong in the note.

Step 4: Add Attribution (Recommended)

To make your Bark leads show up correctly in Found's reporting, add these additional rows to the Data section:

Key	Value
`attribution.utmSource`	Type literally: `bark`
`attribution.utmCampaign`	Insert the service or category name from the Bark lead
`attribution.utmContent`	Insert the Bark lead ID

With these in place, your enquiries will be correctly attributed to Marketplace → Bark in Found's reporting, so you can compare Bark against your other enquiry sources - and the lead ID ties each enquiry back to the lead you bought on Bark.

Step 5: Add the Authorization Header

Scroll to the Headers section in Configure and add two rows:

Name	Value
Content-Type	`application/json`
Authorization	`Bearer YOUR_WEBHOOK_SECRET`

The Authorization value must include the word Bearer, a space, and then your secret - for example: Bearer sk_live_abc123.... Pasting just the secret on its own will fail.

Important: Do not put your secret in the Basic Auth field - that uses a different authentication scheme and your enquiries will silently fail.

Step 6: Test and verify

In Zapier, click Test action on your Webhooks by Zapier step - you should get a successful response.
Open Found → Open Enquiries.
Confirm the test enquiry appears with the correct contact details, is attached to the right location and shows Bark as the attribution source.

A successful test in Zapier does not guarantee the enquiry was created. Always verify directly in Found's enquiries list before turning the Zap on.

Once verified, publish the Zap in Zapier. Every lead you purchase on Bark from then on will appear in Found automatically. Leads bought before the Zap was switched on won't flow through - add any you're still working on manually.

Running more than one branch?

If each of your branches has its own Bark account or service areas, set up one Zap per branch, each pointing at that branch's own Location ID from Settings > Integrations > Enquiry Webhook > Location Mappings. Every lead then lands against the right location, and each branch only sees its own enquiries.