Hey everyone,
We are a lead generation agency and currently use Zapier as our main tool. However, Zapier is becoming too expensive, so we are evaluating Make. Most of our workflows start when we receive a real-time lead from Meta/Facebook, which we then send to Google Sheets, a CRM, or via an HTTP request.
One Zapier feature we use a lot is “Transfer Data”, and I can’t find anything similar in Make.
Here’s how it works in Zapier: for every scenario, there is an option called “Transfer Data.” When I click it, I see a table with all the data that scenario has received. I can then select some or all of that data and run the scenario again.
This is extremely useful for us in many cases:
-
Missed leads due to connection issues
-
Example: We use Ad Account A. The campaign manager is B, but the connection was created with Manager C’s account.
-
If Manager C’s token expires or Facebook suspends their account, the scenario stops working, even though leads are still being generated.
-
After fixing the connection, we can easily recover missed leads with Zapier’s “Transfer Data” by just selecting and re-sending them.
-
Accidental data loss
- Example: A lead in Google Sheets gets deleted by mistake. Instead of manually re-entering, Zapier lets us resend just that lead in a couple of clicks.
-
Client-side issues
- Sometimes a client’s CRM crashes, and we need to re-send their leads quickly.
In short, Zapier’s “Transfer Data” is very handy because it keeps a copy of both successful and failed data in a user-friendly table. This makes resending or recovering data very easy compared to Make’s logs.
I noticed Make has an option to “List leads” in the facebook app which I think polls data and allows forwarding. But that requires setting up the integration again.
My question:
Does Make have a simpler way to poll and re-send data (like Zapier’s “Transfer Data”) without creating another scenario from scratch?
Thanks!
Polling Triggers
There are two main types of triggers, Polling (scheduled), and Instant (webhooks). Polling triggers can only run on a schedule. Instant triggers can be run as soon as data is received by the webhook.
- Polling means Make checks external service for changes (pull changes to Make).
- Webhook (instant) triggers means external service calls Make when there are new changes (push changes to Make).
You can basically use a polling trigger — it’s basically a API request that Make has to occasionally “call” to fetch the latest changes/items.
If you want to re-run your scenario on older data,
Polling Triggers: Epoch Panel & Selecting Older Data
Go to the Epoch Panel, by right-clicking on the trigger module (polling triggers only), and select “Choose where to start” from the list of options in the context menu.
If you select “From now on”, the next time the scenario runs it will only return new data (or nothing if there is no new data).
You can also select other old data to re-run your scenario with next using the “Choose manually” option. This will then show you a list of previous historical items you can select to process the next time the scenario is triggered.
For more information, see
Here are some useful links and guides you can use to learn more on how to use the Make platform, apps, and app modules. I found these useful when I was learning Make, and hope they might benefit you too —
Getting Started
Help Centre Basics
Articles & Videos
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
Thank you, @samliew , for your kind response. I think I was not able to explain my concern clearly earlier, so I have updated it with more details. If possible, please have a look again.
I also could not follow your instructions after “Go to the Epoch Panel.” I tried but could not find where exactly this panel is located.
the following is my polling trigger but it does not have the options that you mentioned.
From what I understood, you are suggesting that I should create another scenario if I want to resend some data. If that is correct, then unfortunately it is not what I am looking for.
I do understand there are polling triggers and I can explore those. But what I was hoping for is something similar to Zapier’s “Transfer Data” feature, where in just a couple of clicks I can see all the past data, select what I need, and resend it—without having to configure the source and destination again.
With the workaround you suggested, I would have to:
-
Create a new scenario,
-
re-select the source, facebook page, form etc
-
Set up a webhook,
-
Re-select the destination,
-
Map each field again,
-
Do the formatting,
-
And then test everything.
It takes several minutes to do this. We run 100s of campaign and we often need to do this often.
Zapier has a built-in feature to do this boring repetitive task in a matter of few seconds. I hope I was able to clarify what I am missing here on make.com
List Leads is not a trigger module, that is a search module being used as the initial module in your scenario.
Only Polling Trigger modules have an Epoch Panel.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
What would you recommend in this situation? Is there any Polling trigger for facebook leads?
Yes, Facebook Lead Ads has both types of trigger modules.
For more information, see https://www.make.com/en/integrations/facebook-lead-ads
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
Hey,
Thank you so much for your help. Your solution does work, but it’s not exactly what I was hoping for. What I am looking for is an in-built ability to quickly “transfer leads” within an existing scenario, something that only takes a few seconds (similar to the feature available in Zapier).
The solution you suggested works, but it requires creating a new scenario with fresh steps and integrations, which takes a few minutes. Maybe in the future, Make.com will consider adding such a feature for more convenience.
I am not familiar with that feature on Zapier as described. Also I don’t understand why a few minutes of setting up a scenario is an issue…?
