Make integrationBuild scenarios with Make (Integromat)

Create powerful
automations with Make

Point a Make Custom webhook at LeadQuasar and every unlocked lead, list, alert result or reply runs your scenario.

  • Start from a Custom webhook
  • Fields learned from a test
  • Route each event its own way
  • Signed with HMAC-SHA256
  • No credit card required
  • Free forever plan
  • On Plus and Max
Example data

What you get with Make

  • Advanced Workflows

    Multi-step scenarios from one webhook.

  • Any App Make Connects

    Your scenario takes leads anywhere.

  • Custom Logic

    Routers and filters on the event name.

  • Save Time

    No exporting or copying leads by hand.

  • Signature Headers

    Drop anything that isn't from LeadQuasar.

  • Retried for You

    About 15 hours if Make doesn't accept it.

How it works

Connect LeadQuasar with Make in 3 simple steps.

  1. 1

    Connect Make

    Add a Custom webhook.

  2. 2

    Pick Your Events

    Paste it, tick the events.

  3. 3

    Activate Scenario

    Send a test, turn it on.

Supported Events

Each one, on each address you add:

View all
  • Lead unlocked
  • List created
  • Leads added
  • Alert results
  • Email reply
  • Rules
  • Test event
  • HMAC signed

Example Workflows

  1. 1Unlocked lead → enrich it → add it to your spreadsheet or database
  2. 2Leads added to a list → add each to an email campaign
  3. 3A lead replies → create a deal in your CRM and tell the owner

Connect LeadQuasar to Make today

Build lists free, then run a scenario on every event.

Connect Make
In detail

What the Make integration does

Make, formerly Integromat, starts a scenario from a Custom webhook. Point LeadQuasar at it and every unlocked lead, saved list, alert result or email reply runs your scenario.

  • A Custom webhook

    Add Make's Webhooks module, copy its address into LeadQuasar and choose the events. Nothing to install on either side.

  • Make learns the structure

    Click Send test in LeadQuasar while Make is listening and it records the fields, so the next modules can map them.

  • Route by event

    Each request names its event, so one scenario can route unlocks, lists and replies down different paths with a router.

  • Signed requests

    Each one carries X-LeadQuasar-Signature and X-LeadQuasar-Timestamp headers, so a filter can drop anything that didn't come from LeadQuasar.

Plus plan. Part of Plus ($21.99/month) and Max ($29.99/month). Compare plans

Set it up

  1. 1In Make, create a scenario and add the Webhooks module, Custom webhook. Open Make
  2. 2Click Add, name it LeadQuasar, and save.
  3. 3Copy the webhook address, paste it below, pick the events and click Add.
  4. 4Click Send test here so Make learns what LeadQuasar sends, then add your next modules.

Events you can pick

WhenEvent name
A lead is unlockedlead.unlocked
A list is createdlist.saved
Leads are added to a listlist.leads_added
A lead alert finds new leadsalert.new_leads
A lead replies to your emailcrm.reply
Anything an automation rule sendsyour rule's name
FAQ

Make: questions

Does each event use Make operations?

Yes. Each event runs your scenario, which uses operations from your Make plan like any other run.

Can one scenario take every event?

Yes. Pick all the events on one webhook address and route by the event field, or use up to 5 addresses, one per scenario.

What if Make is down or my scenario fails?

When Make doesn't accept a request, LeadQuasar retries it with growing gaps for about 15 hours, then marks it failed. An address that keeps failing pauses itself.