Skip to content

Make integration

Buyer intent leads in your Make scenarios

Needle POSTs one JSON event per lead to a Make custom webhook, so a scenario can route community leads to a sheet, a CRM, or team chat. Start from the blueprint below and change the second step to whatever you need.

Try free for 7 daysBrowse all integrations

7-day free trial - no card. Cancel anytime.

How it works

  1. Step 1

    Save a brand and turn on Auto Search

    Add the problem phrases, competitors, and communities you care about. Needle reruns the search on your schedule.

  2. Step 2

    Import the blueprint

    Create a scenario in Make, import needle-make-blueprint.json from the scenario menu, then create a webhook in the first module and pick your Google connection in the second.

  3. Step 3

    Test and enable in Needle

    Copy the webhook address (https://hook.<region>.make.com/…), paste it under Alerts & Integrations → Make, and click Test and enable while the webhook module is waiting for data, so Make learns the fields.

  4. Step 4

    Switch the scenario on

    Schedule it to run as data arrives. Real leads come in after the next Auto Search run; the test event is filtered out before the sheet.

Why teams route Needle leads through Make

Available on the Growth plan and up.

  • Any next step

    Swap the Google Sheets module for a CRM, a ticket, or a chat message without changing anything in Needle.

  • Branch on intent

    Filter on lead.tier to treat hot leads differently from worth-engaging ones, or on lead.platform to split by community.

  • One stable schema

    Every event uses LeadEvent v1, so mappings you build keep working as Needle adds optional fields.

Download the Make blueprint

A two-module scenario: Webhooks → Custom webhook, then Google Sheets → Add a row.

Download blueprint (JSON)

needle-make-blueprint.json

  • No connections or credentials are included. Make asks you to create the webhook and choose your own Google connection after import.
  • Before the first lead, create a tab named "Needle leads" with a header row in the order shown below, then pick the spreadsheet in the Add a row module.
  • A filter between the modules passes only event = "lead.created", so the test event from Needle never becomes a row.
  • The blueprint does not check the X-Needle-Signature header. Keep the webhook address private.

Field mapping in the blueprint

Columns A to M of the sheet, and the webhook value each one is mapped from. Every other field in the event is also available to map.

Sheet columnMake value
A occurred_at{{1.occurred_at}}
B brand_name{{1.brand.name}}
C lead_tier{{1.lead.tier}}
D lead_platform{{1.lead.platform}}
E lead_title{{1.lead.title}}
F lead_url{{1.lead.url}}
G lead_author{{1.lead.author}}
H lead_excerpt{{1.lead.excerpt}}
I lead_score{{1.lead.lead_score}}
J lead_matched_term{{1.lead.matched_term}}
K lead_competitor_mentions{{join(1.lead.competitor_mentions; ", ")}}
L lead_dashboard_url{{1.lead.dashboard_url}}
M event_id{{1.event_id}}

When Make is the wrong choice

  • Every request must be verified

    The blueprint trusts the webhook address. If you need the HMAC signature checked, use the n8n template or your own endpoint.

  • You only want a sheet of leads

    The Google Sheets destination writes rows directly with a small Apps Script, with no scenario to maintain.

  • Your tool is already native

    Slack, Discord, Google Chat, Teams, Notion, and Airtable connect straight from Needle - and HubSpot and Pipedrive on Scale.

Frequently asked questions

Setup, limits, and every platform are covered in the docs.

Which Make URLs does Needle accept?
Webhook addresses on make.com or integromat.com, such as https://hook.eu1.make.com/…. Other hosts are rejected when you save; use the custom webhook destination for those.
How do I avoid duplicate rows?
Needle never sends the same lead to the same destination twice within 30 days. If you replay executions in Make, add a Search Rows step on event_id before Add a row.
Does Make get one request per lead or a digest?
One per lead. Needle sends one request per hot or worth-engaging lead after each Auto Search run - at most 25 per destination per run - and never sends the same lead to the same destination twice within 30 days. Runs follow the interval you set per brand: every 4 to 24 hours on Growth, as often as hourly on Scale.
Which plan includes Make?
Make is available on the Growth plan and up. The 7-day free trial lets you try it first.
Does Needle reply or post for me?
No. Needle finds and ranks conversations and can draft a reply for you to edit. You decide whether to respond, and you post it yourself.

Connect Needle to Make today

Send ranked buyer threads to Make on your Auto Search schedule, so the conversations worth replying to land where your team already works.

Try free for 7 daysBook a demo

Cancel anytime