Every website lead captured with its source, and three scattered contact lists turned into one CRM

At a glance

The project in 30 seconds

Client: Treehouse Life International
Location: United Kingdom
When: April 2026
Engagement: Fiverr · about 3 weeks, ongoing
My role: Automation & CRM setup
Stack: Framer, Make, Folk

MakeFolk CRMFramerWebhooksGoHighLevel & Pipedrive exports

The situation

Where Treehouse Life started

Treehouse Life's website, built in Framer, has several forms: a wish-list, a contact form, consultation requests and a newsletter sign-up. Leads arrived, but there was no record of which form they used.

Older contacts were spread across GoHighLevel and Pipedrive. To follow up properly, the team had to look in three places.

The challenge

What had to be solved

The goal was simple to say and fiddly to build:

Every form submission in the CRM, automatically, with its source and the page it came from.

No duplicates when the same person fills in a second form.

One clean list combining the GoHighLevel and Pipedrive history.

The approach

How I tackled it, step by step

1
Catch every form
A webhook in Make receives each Framer submission.
2
Clean and label
Two cleaning steps normalise the data and work out the lead source and page.
3
Update or create
Make looks the person up in Folk first, then updates or creates them.
4
Consolidate the past
GoHighLevel and Pipedrive exports imported into organised Folk groups.

What I built

Inside the system

7 real screenshots from the build. Click any image to enlarge.

01Website forms straight into the CRM

Each Framer form posts to a Make webhook. The scenario maps the form to a lead source (wish-list, contact, consultation or newsletter), records the page, then searches Folk. A router updates the existing person or creates a new one.

Make scenario from Framer to Folk — Framer → Folk, with update-or-create

Make variables mapping form IDs to lead sources — Lead-source mapping per form

Scenarios in the client's Make workspace — The scenarios in the client's Make account

Test submissions landing in the Folk Framer Contacts group — Test submissions arriving in Folk

02Three contact lists become one

I imported 1,825 GoHighLevel contacts and 1,036 Pipedrive records (people and organisations) into Folk, organised into groups: Framer contacts, suppliers, leads, clients and partners.

Folk import complete: 1,825 records — 1,825 GoHighLevel contacts imported

Folk import complete: 1,036 records — 1,036 Pipedrive records imported

Folk workspace with groups for suppliers, Framer contacts, GHL contacts, leads and clients — Organised groups in one workspace

The results

What changed for Treehouse Life

One CRM instead of three places to look.

Every new website enquiry arrives in Folk automatically, with its source attached for follow-up and reporting.

Repeat form fills update the existing person instead of creating duplicates.

The client kept working with me after the build, as an ongoing collaboration.

Key decisions

The calls that made it work

Good systems come from good decisions. Here's what I chose, and why.

Look up before writing

Searching Folk first is what keeps repeat visitors as one record.

Label the source at the moment of capture

Adding the source later is guesswork. Capturing it on submission makes marketing reports reliable.

Keep the old CRMs' data in groups

Imported records stay identifiable by origin, so nothing gets lost in the merge.

In the client's words

★★★★★

"Excellent work and responsive to my whole brief."

Treehouse LifeUnited Kingdom · ongoing collaborationVerified Fiverr review

Is this for you?

A similar system could help if…

Your website has several forms and you don't know which brings leads.
Contacts are scattered across old tools.
You use Framer, Webflow or similar and want leads in a CRM automatically.

Contact details in the background are blurred. Every screenshot on this page comes from the real project; nothing is a mock-up.