Skip to main content
FolkscopeFolkscope

Folkscope + Webhooks

Webhooks are native to Folkscope and they are the foundation everything else builds on. A Flow can fire an outbound HTTP request to any URL you own, carrying the full enriched lead as JSON. Folkscope tracks your chosen accounts, enriches each engager into a lead with role, company, and location, and scores them daily against your ICP. The webhook simply delivers that lead to your endpoint the moment a trigger fires. If you have an engineer, this is the most flexible option, since you decide exactly what happens next.

Folkscope + Webhooks

Send enriched, scored leads to any endpoint you control, in real time.

How it works

  1. 1

    Track the accounts you care about

    Add the LinkedIn profiles and company pages whose engagement you want to act on.

  2. 2

    Folkscope enriches and scores

    Each engager becomes a lead with role, company, and location and gets a daily ICP score.

  3. 3

    A Flow fires the webhook

    On a trigger like NEW_LEAD or an ICP-qualified lead, Folkscope sends a POST request to your URL with the lead as JSON.

  4. 4

    Your endpoint takes over

    Your service receives the payload and does whatever you want with it: store it, route it, notify someone, or enrich it further.

What you can do with it

  • Write every scored lead into your own database or data warehouse for analysis.
  • Build custom routing logic that no off-the-shelf automation tool covers.
  • Push leads into an internal tool or admin panel your team already uses.
  • Forward the payload to a serverless function that calls an API Folkscope does not integrate with.
  • Mirror leads into a queue so you can process them at your own pace and retry on failure.

Setup

  1. Stand up an endpoint that accepts a POST request with a JSON body.
  2. In Folkscope, create a Flow with a webhook action and enter your endpoint URL.
  3. Choose the trigger, such as an ICP-qualified lead, that should fire the webhook.
  4. Verify the request signature or shared secret on your side to confirm it came from Folkscope.
  5. Send a test engagement, inspect the payload, and build your handler around its fields.

Frequently asked questions

What is in the webhook payload?

A JSON body with the enriched lead: name, role, company, location, the ICP score, and which tracked post the person engaged with, plus the trigger that fired it.

How do I know a request really came from Folkscope?

Verify the signature or shared secret included with the request before you trust the payload. That keeps your endpoint from acting on spoofed calls.

When should I use a raw webhook instead of Zapier or Make?

Use a raw webhook when you have engineering help and want full control, or when latency and custom logic matter. Zapier and Make are easier if you would rather not write code.

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 + Make

Folkscope fires a webhook with enriched, ICP-scored LinkedIn leads that Make catches as a scenario, so you can route, filter, and transform leads across any apps you connect.

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.