Skip to main content
FolkscopeFolkscope

Folkscope + Make

Make connects to Folkscope through the webhook layer. A Flow fires an outbound webhook, a Make custom webhook trigger catches it, and your scenario takes over from there. Folkscope handles the tracking, enrichment, and daily ICP scoring, so the lead arriving in Make already has role, company, location, and a score attached. Make is a good fit when you want more control than a simple one-to-one Zap, like branching logic, data shaping, or chaining several apps together in one scenario.

Make logo

Folkscope + Make

Catch Folkscope leads in a Make scenario and route them your way.

How it works

  1. 1

    Track accounts and capture engagement

    Folkscope watches the LinkedIn profiles and company pages you add for new engagement.

  2. 2

    Enrich and score the lead

    Every engager becomes a lead with role, company, and location and gets an ICP score on the daily run.

  3. 3

    Flow sends a webhook to Make

    A Flow trigger posts the lead to your Make custom webhook URL as a JSON payload.

  4. 4

    Your scenario routes and transforms

    Use routers, filters, and modules in Make to shape the lead and send it to one or more apps.

What you can do with it

  • Branch a scenario so different ICP score bands go to different destinations.
  • Enrich the payload further with another Make module before writing it to a destination.
  • Create records in several systems at once, like a CRM plus a spreadsheet plus a chat alert.
  • Hold leads in a data store and batch-create them on a schedule instead of one at a time.
  • Map engagers to the right account owner using lookup tables inside the scenario.

Setup

  1. In Make, add a Custom Webhook trigger to a new scenario and copy its address.
  2. In Folkscope, create a Flow with a webhook action and paste the Make URL.
  3. Choose the Flow trigger, such as an ICP-qualified lead, to control what reaches the scenario.
  4. Build the routers, filters, and destination modules you want in Make.
  5. Run the scenario once with a test engagement to confirm the payload and mapping.

Frequently asked questions

Is Make a native integration?

No. Make connects through Folkscope's outbound webhook and a Make custom webhook trigger. There is no native Make build, but the webhook gives you full access to the lead data.

Why pick Make over Zapier?

Both work over the same webhook. Make tends to fit when you want branching logic, data shaping, or several actions in one scenario. Zapier is often quicker for a simple one-step route.

Can I filter leads inside Make?

Yes. You can gate the Flow on ICP score and add filters inside the scenario, so you control quality both before and after the webhook fires.

More integrations

Folkscope + Zapier

Folkscope fires a webhook with enriched, ICP-scored LinkedIn leads that Zapier can catch and send to thousands of apps, so you build the routing your team needs.

Folkscope + Webhooks

Folkscope's native outbound webhook fires enriched, ICP-scored LinkedIn leads to any URL you control, so you can build your own routing, storage, or notification logic.

Folkscope + Google Sheets

Folkscope sends enriched, ICP-scored LinkedIn leads into Google Sheets through Zapier, Make, or a webhook, so every engager lands as a row you can filter and share.

Folkscope + HubSpot

Folkscope tracks LinkedIn engagement, enriches and ICP-scores the people who engage, then creates or updates HubSpot contacts automatically through a Flow. Native integration.

Your next customer is already engaging

Start tracking a profile today. Your first scored leads arrive tomorrow morning.

Start tracking free

No browser extension. No LinkedIn login required.