Make Scenario connecting Facebook Ads and Pipedrive

The Story of a Make Workflow: Facebook Lead Ads to Pipedrive

A UK construction client was checking Facebook daily and pasting leads into Pipedrive from a CSV. Here’s how I replaced that routine with a simple Make workflow, what it saves in time and effort, and why there’s no AI in it.

On one Sunday in October, sixteen leads came in through Facebook for a UK construction company I built a workflow for. The first arrived at 5:02am and the last at 8:25pm. Nobody at the company lifted a finger, and each one was in their CRM within seconds, with the details already sitting in the sales team’s inbox.

Before this workflow, those sixteen leads would have waited in Facebook until someone next went looking.

There’s no AI in it, and I think that’s the most useful thing about the story. In my view, too many companies would happily buy an AI sales agent while their leads are still sitting in a CSV.

The Old Routine

The client runs Facebook Lead Ads aimed at other businesses. When someone filled in the form, nothing happened. No notification, no email, no record in the CRM.

So someone had to remember to check Facebook every day, download the new leads as a CSV and paste them into Pipedrive by hand. By the time anyone saw a lead, it was hours old. This is the kind of job that gets done faithfully right up until the person doing it goes on holiday.

Those hours matter more than they sound. A 2011 Harvard Business Review study found that firms trying to contact a prospect within an hour were nearly seven times as likely to qualify the lead as firms that waited even an hour longer. It’s an old study of American companies, so I wouldn’t treat the number as gospel. Still, I’d be surprised to meet a salesperson who thinks a lead gets warmer with age.

There’s a slower risk too, because lead data is only available from Meta for 90 days. Forget the downloads for long enough and the leads are gone.

What the Workflow Does

I built it in Make back in March. When someone submits the form, the sales team gets an email with their details, and Pipedrive gets a new lead with a named owner. The typical run takes just under three seconds.

Make scenario connecting Facebook Lead Ads to an email step, a Pipedrive search and a router leading to Pipedrive lead creation.

How it was Built

There are seven modules, and none of them is clever.

The trigger. Make’s Facebook Lead Ads module is instant, so a new submission fires the workflow straight away. I wouldn’t use a scheduled check here, because that’s only a quicker version of the job I was trying to get rid of.

The email. This sends the lead’s name, work email, phone number and company to the people who follow up. It’s the simplest step in the build, and on its own it fixes the lack of notifications.

The search. Before creating anything, the workflow looks in Pipedrive for an exact match on the lead’s work email. Ads don’t know who’s already in your CRM, and nobody wants two records for one person.

The router. This is the only decision in the whole thing. If Pipedrive finds the person, the workflow attaches a new lead to them. If it doesn’t, it creates the person first and then the lead. Both paths title the lead with the person’s name and company, and give it the same owner, so it’s easy to pick out in Pipedrive.

Make router splitting into two paths, one creating a lead for an existing Pipedrive person and one creating the person first.

Each run in the month I checked used five Make operations, which is a small price for a job someone used to do by hand.

What it Saves

I don’t have a stopwatch figure for the old routine, and I won’t make one up. What I can do is count the work that has gone.

From 1 October to 3 November, the workflow handled 87 leads, and every run succeeded. Under the old routine, that same stretch meant over 30 daily trips to Facebook, plus downloading and pasting 87 leads into Pipedrive. With four details per lead, that’s 348 fields moved by hand, all of which could land in the wrong column. Today that work is zero.

I think effort is the bigger saving. A small job that has to happen every single day is never really small, because someone has to carry it around in their head, and cover it when they’re off. If you run something similar, time it for a week and multiply. The answer tends to be more annoying than you’d expect.

Then there’s the waiting. Of those 87 leads, 49 arrived outside Monday to Friday, 9am to 5:00pm, and 16 of them came in at the weekend. Each of those would have sat unseen until the next check. Now the sales team has the details within seconds. What they do with that email is up to them, but at least the choice is theirs.

As for results, the client tells me they’ve seen a huge surge in quality leads, and although their sales cycle is long, it’s already bearing fruit. I won’t claim the workflow created those leads, because the ads and the people following up did that. What the workflow did was make sure nothing went stale in a CSV while they got on with it.

What it Doesn’t Do

It doesn’t pick up the phone. The logs tell me how fast a lead reached Pipedrive, and they say nothing about how fast anyone rang them.

It also isn’t perfect. If I built it again, I’d add error handling, because the email runs first and a mail failure would stop the lead from reaching the CRM. I’d also match on more than an email address, since someone using a second address becomes a second person.

What I’d Take From This

I spend most of my time on this site talking about AI, so I’m hardly against it. But an AI agent writing the perfect follow-up can’t do much with a lead nobody has seen yet.

So before you buy anything, look for your own version of that CSV: the dull job someone does every day because nothing else does it. Fix that first.

I write about what’s worth doing in AI marketing, and what isn’t, in my free weekly newsletter. Subscribe here.

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Total
0
Share