Connect Make

Trigger a Make scenario from an accepted HoneyFalcon lead through a customer-owned Custom Webhook.

Why it matters

The Make preset gives visual automation a stable handoff without changing HoneyFalcon's routing workflow. Operations can map one accepted lead into the tools in a Make scenario while keeping the outbound HTTP result visible in HoneyFalcon.

Where to work

Create the Custom Webhook in Make first. Then open Company -> Connectors in HoneyFalcon, select New connector, choose Make webhook, and select Load preset.

Steps

1. In Make, create or open the target scenario and add a Custom Webhook trigger.
2. Create the webhook, copy its unique URL, and leave Make ready to determine the data structure.
3. In HoneyFalcon, load the Make webhook preset and paste the URL into Destination URL.
4. Review Payload fields, the JSON template, and Successful HTTP statuses; a HoneyFalcon credential is normally not required.
5. Run Test draft with synthetic data so Make can capture a safe sample.
6. Map and test the remaining Make modules, then enable scheduling for the completed scenario.
7. Create connector or Save changes, Activate the saved revision, and verify a new synthetic lead in both Delivery history and Make's execution history.

See it in HoneyFalcon

Step 1 of 3: Make preset selected in the connector editor.

Step 2 of 3: Make destination and protected credential controls.

Step 3 of 3: Make endpoint and Successful HTTP statuses to review before creation.

Build and verify the Make scenario

Create the Custom Webhook in the intended scenario

Make generates the destination URL. HoneyFalcon does not create the scenario or choose its downstream modules.

Keep the webhook URL private and confirm that you are working in the correct Make organization, team, and scenario before pasting it.

Send only a useful sample

The preset starts with a generic JSON mapping. Reduce Payload fields to what the scenario needs and keep each placeholder synchronized with that allowlist.

Use synthetic values when Make is waiting to determine the data structure. Avoid using a production lead just to teach the scenario its schema.

Treat Test draft as one webhook response

Destination accepted the test means Make's Custom Webhook returned an allowlisted status for the visible draft. It does not save the connector or create Delivery history.

A webhook response also does not prove that later modules ran, committed their changes, or handled the mapped values correctly.

Enable and observe both systems

Finish the scenario, test its modules, and enable its schedule in Make. Save and activate the HoneyFalcon connector separately.

For a new synthetic lead, compare the HTTP result in Delivery history with the scenario execution and the final destination reached by Make.

The Make handoff is ready when

• The connector points to the intended Custom Webhook and sends only the required fields.
• Make captures a synthetic sample and maps every required value.
• The completed scenario is enabled separately in Make.
• A new synthetic lead appears in Delivery history and completes the expected Make scenario path.

Continue learning

• Start from: For operations - start here
• Related guide: Edit and test safely
• Related guide: Generic webhook connector
• Previous: Connect Zapier
• Next: Connect HubSpot