Tools and providers
Part of Which CRMs receive UK lead marketplace leads — and how to wire them
Which CRMs receive UK lead marketplace leads — and how to wire them
The UK lead marketplace names rarely ship a first-party CRM app. See which CRMs receive their leads and the three steps to wire imports automatically.
What to take away
- Bark, Checkatrade, MyBuilder, Rated People and TrustATrader are the UK lead marketplaces most teams ask about. Public app directories rarely list a first-party CRM app for them.
- HubSpot, Salesforce, Pipedrive, Zoho CRM and Microsoft Dynamics 365 can receive leads natively through private apps, webhooks or APIs.
- HubSpot is often quickest for small teams because private app tokens and workflow webhooks work on most paid plans.
- Salesforce suits larger teams, but decide whether the network writes to Leads or Contacts before you build.
- Pipedrive and Zoho CRM are practical for mid volume, while Zapier, Make or n8n cover the gap when a network only exposes an API.
What native really means in a CRM directory
A native integration is built and maintained by the CRM vendor or the marketplace. It appears in the CRM's app directory and installs through an authorisation screen. Anything else is a connection you own. That difference decides who you call when a mapped field stops arriving.
A CRM record is a container of fields, activity history and an assigned owner, as the general account of customer relationship management sets out. The lead marketplace sends the first payload. Nothing in the network's contract obliges it to send the updates that follow.
For UK lead marketplaces, native usually means CRM side. HubSpot private apps, Salesforce Web-to-Lead, Pipedrive persons and deals API, Zoho CRM webhooks and Dynamics 365 Power Automate are first-party routes. Bark, Checkatrade, MyBuilder, Rated People and TrustATrader mostly leave the build to you.
Three routes, and what each one carries
Lead marketplace CRM integration UK buyers face the same fork: a directory app, an integration platform, or a direct build. A directory app is the least work to install and the vendor keeps it running, but it rarely exists for UK trade marketplaces. An integration platform such as Zapier, Make or n8n gets a connection live in an afternoon and handles field mapping, filters and retries in a visual builder, though it bills per task and every change to the payload is yours to fix. A direct build — a private app token, a webhook receiver or a small serverless function — carries no per-lead fee and gives you full control of the dedupe key and owner rules, but you own the monitoring for as long as the network's API runs.
Three integration routes compared
Directory app
- Maintained by
- CRM or network
- Carries
- Standard fields
- Breaks at
- Network field changes
iPaaS connector
- Maintained by
- Your ops team
- Carries
- Exposed API fields
- Breaks at
- Quotas, silent failures
Direct API
- Maintained by
- Your developers
- Carries
- Full payload
- Breaks at
- No monitoring
Score each candidate on published documentation rather than a sales claim, using the same pass or fail tests set out in our guide to lead network software selection. Whichever route you pick, log the connection beside your other processors and name the person who retests it after a CRM release.
A three-step wiring sequence
Wiring is a data exercise, not a purchasing one. Work in this order.
- Connect the source.Create the credential on the CRM side first: a HubSpot private app token with contact and custom-property scopes, a Salesforce connected app or Web-to-Lead endpoint, a Pipedrive API token, a Zoho OAuth client, or a Power Automate flow for Dynamics 365. Then take the API key or partner credentials and the webhook URL from the marketplace's developer area, and decide which side calls which.
- Map and normalise the fields.Fix the payload before the first live lead: source marketplace, source lead reference, trade or category, postcode, customer name, phone, email, description, consent wording and a timestamp. Use the source marketplace plus the source lead reference as the dedupe key, falling back to a normalised email or phone number, and set the CRM's duplicate rule to match it.
- Route, own and monitor the record.Send every payload to one object — decide Leads or Contacts in Salesforce in advance, and whether a Pipedrive lead becomes a person, a deal or both. Assign the owner with a round-robin or territory rule inside the CRM, never in a spreadsheet. Log each call, retry failures with exponential backoff, alert when errors climb, and reconcile imported counts against the marketplace regularly. Nothing here needs a CSV download or a manual upload.
Three-step wiring sequence
- Draw field map before touching CRM
- Give each network its own source value
- Import capped test batch and reconcile
HubSpot, Salesforce, Pipedrive, Zoho CRM and Dynamics 365
HubSpot tends to be quickest. A private app token lets a network post contacts and custom properties into an account, and a workflow can route the record to an owner. Confirm that the network supports contact creation, not only form submissions.
Salesforce buyers should check whether the network writes to Leads or Contacts. Conversion rules and duplicate matching differ between the two objects. Web-to-Lead forms suit small volumes, while middleware suits a steady daily file.
Pipedrive exposes a persons and deals API, so Zapier is usually enough. Watch the plan limit on active integrations, and decide in advance whether an imported lead becomes a person, a deal or both.
Zoho CRM supports webhooks and a REST API, which suits teams that want to avoid per-task iPaaS costs. Microsoft Dynamics 365 can use Power Automate connectors, but licensing and admin setup add lead time.
For consumer marketplaces, Bark uses a credit model, so volume follows your credit balance. Checkatrade and TrustATrader sell trade memberships, not per-lead access. MyBuilder uses shortlist credits, and Rated People sells leads individually. Each suits different trade volumes.
Houzz Pro receives Houzz enquiries in its own CRM, which suits designers already paying for the platform.
Consent, lawful basis and the record trail
Imported leads still carry the seller's obligations. ICO guidance on direct marketing and privacy and electronic communications covers the calls, texts and emails that follow. That includes the soft opt-in and the rules on screened numbers.
Article 6 of the UK GDPR text lists the lawful bases available. Name the basis you rely on inside the imported record, and file the consent wording or the legitimate interests assessment beside it.
When a batch turns out to be weak, work back from the source value instead of deleting rows quietly. Run the checks in our guide to spot low-quality leads before the records reach a sales queue.
Common questions
The questions below cover what UK lead marketplace and CRM wiring projects run into most often.
Does HubSpot have a native lead marketplace connector?
Only where the marketplace has built one. Search the HubSpot app directory under names such as Bark, Checkatrade, MyBuilder, Rated People and TrustATrader. Most UK networks publish an API or webhook rather than an app.
Can Zapier replace a native integration?
Yes for most mid-volume imports. It becomes expensive and fragile when a connection fires per lead on a high-volume account. Check the task cost before you commit.
Do I need consent for every imported lead?
Not always. Consent is one lawful basis, and legitimate interests can support some business-to-business contact. The basis must be recorded and follow-up must still respect direct marketing rules.
What should I check before the first bulk import?
Duplicate matching rules, owner assignment, required fields and the timestamp format. Test with a small batch and reconcile counts before releasing the file to sales.
