Before you start

Before building your flow, make sure you have:

Access to Make (Note: Make was previously called Integromat.)
Permission to create, edit and run scenarios
Access to the CRM or destination system you want to connect
Permission to create or update the relevant records in that system
An idea of which Unibuddy fields you want to store
An understanding of any fields that your CRM requires before a record can be created
A Main Platform Widget URL. This is the URL of the website where your Unibuddy Main Platform Widget is installed.
At least one prospect or test lead available for testing
Someone who can configure the Unibuddy side of the integration, such as your CRM administrator, IT team or technical team

What you'll do across this guide series

The full setup is split into two stages:

Part 1 — Receive Unibuddy data in Make ← You are here
Create your Make scenario, configure the Custom Webhook, and send the webhook URL and your preferred date format to Unibuddy so the integration can be configured.

Part 2 — Connect Unibuddy data to your CRM
Connect your CRM to Make, choose which Unibuddy data you want to store, map the fields, test the integration and turn your scenario on.

This article covers Part 1.

How does the integration work?

The basic journey is:

Unibuddy → Make → your CRM

When new prospect data is ready to sync, Unibuddy sends the data to the Custom Webhook URL generated by your Make scenario.

New leads are not sent to Make instantly. They arrive at the next scheduled sync.

Unibuddy sends data to Make on a scheduled basis, four times a day: 12am, 6am, 12pm and 6pm UTC.

Make receives the Unibuddy data and then passes it to the steps you configure — for example, creating a new CRM record or updating an existing one.

This guide uses a Unibuddy → Make → Google sheet as an example, but Make can connect Unibuddy to a range of compatible CRM.

The overall process remains Unibuddy → Make → your destination system, but the CRM-specific actions, fields and screens may differ depending on your setup. Your CRM administrator or technical team can help you adapt these steps where needed.

Important: Because Unibuddy sends data on a schedule, clicking Run once in Make does not cause a new lead to be sent immediately. If you're testing the integration, you may need to wait until the next scheduled sync for the test data to appear in Make.

1. Create a new Make scenario

Sign in to Make.
Open the relevant Make organisation or team.
Open Scenarios.
Select Create a new scenario.
Give the scenario a name that makes its purpose clear.

2. Add a Custom Webhook

The Custom Webhook is the connection point between Unibuddy and Make.

When Unibuddy sends lead data to the webhook, Make receives the data and makes the available fields accessible to the next module in your scenario.

To add the webhook:

Click the large plus (+) button.
Search for Webhooks.
Select Custom webhook.
In the Webhook field, select Create a Webhook.
Give the webhook a clear name.
For example:
Unibuddy New Lead
Select Save.

Make will create a unique webhook URL.

3. Copy your Make webhook URL

After saving the webhook, Make will display a unique webhook URL.

Copy the webhook URL.
Keep it available for the next step.

This is the URL that Unibuddy will use to send lead data into your Make scenario.

4. Send the webhook details to Unibuddy

Send the following information to your Unibuddy contact responsible for setting up the integration:

Your Make webhook URL
Your preferred date format

Supported date formats

Choose the date format that best matches your CRM or reporting requirements.

Format	Example
`YYYY-MM-DD`	`2026-10-05`
`MM-DD-YYYY`	`10-05-2026`
`DD-MM-YYYY`	`05-10-2026`

If you are unsure who to send these details to, contact [email protected].

Unibuddy Support team will use the webhook URL to configure the Unibuddy side of the integration.

5. Wait for the Unibuddy configuration and Confirm the webhook connection

Once you have provided the webhook URL, Unibuddy Support will configure the integration on the Unibuddy side and send a test prospect. They will confirm by email when this is done. You can continue once you receive that confirmation.

⏱️ When will sample data appear?

Unibuddy sends lead data four times a day: 12am, 6am, 12pm and 6pm UTC. Sample data will appear at the next scheduled sync, depending on when the next sync runs.

After the next sync, return to your Make scenario and open the Custom Webhook module. Make should show that values have been detected and you are ready to do the mapping.

If no data appears

If the next scheduled sync has passed and no data appears in Make:

Check that the Make webhook URL supplied to Unibuddy is correct.
Check that the webhook connection has been configured correctly.
Contact Unibuddy Support if the data still does not appear.

Do not continue with the CRM field mapping until Make has received sample data.

Troubleshooting

Make is not receiving any data

First, check:

The webhook URL copied from Make is correct.
The same webhook URL was supplied to Unibuddy.
The Unibuddy side of the integration has been configured.
The Make webhook shows that it has been connected.
Run once was selected before the scheduled sync.
The scheduled sync has actually taken place.

If all of these have been checked and Make still has not received data, contact Unibuddy Support.

I clicked Run once but nothing happened

This is expected if the next Unibuddy sync has not happened yet.

Run once tells Make to listen for incoming data. It does not trigger Unibuddy to send data immediately.

Wait for the next scheduled sync at:

12am, 6am, 12pm or 6pm UTC.

A field I expected is missing

Only data included in the Unibuddy webhook payload will be available in Make.

If an expected field is not present in the sample data, contact Unibuddy Support so they can confirm whether that field is included in your integration.

Who should I contact if I need help?

For questions about:

Unibuddy data
The webhook configuration
Which fields are available
The Unibuddy sync
Data not arriving in Make

Contact Unibuddy Support.