LEAD GENERATION

Score doc-portal downloads into MQLs and route hot leads to Slack

When someone downloads a gated asset from your ReadMe doc portal, this looks up the company, applies an intent score.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerReadMe gated download webhook firesReadMeReadMe
  • ActionEnrich visitor against HubSpot contact + companyHubSpotHubSpot
  • LogicCompute intent score from asset weight and account fit
  • LogicBranch: hot lead vs nurture-only
  • ActionPost hot lead alert to sales Slack channelSlack
  • OutputLog download as HubSpot timeline activityHubSpotHubSpot

What it does

Turns raw documentation-download events into qualified, scored leads. Every gated download from your ReadMe portal is matched to a known account, scored by asset type and visitor fit, and the high-intent ones are pushed to sales in real time so reps reach out while interest is fresh.

When to use it

You gate API guides, integration docs, or whitepapers behind an email and want the download itself to signal buying intent — not sit in a CSV nobody reads. Best when your highest-converting content is technical and self-served.

How it works

  1. 1A ReadMe download webhook fires with the asset name and visitor email.
  2. 2Enrich the email against HubSpot to pull company, lifecycle stage, and deal status.
  3. 3Compute an intent score from asset weight (pricing/security docs score higher) plus account fit.
  4. 4Branch on the score: at or above threshold the lead is hot; below it routes to nurture only.
  5. 5Hot leads post to the sales Slack channel with the asset, score, and HubSpot link.
  6. 6Every event is written to HubSpot as a timeline activity so the full download history stays on the contact.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ReadMeAPI docs, changelog, auth.
  2. 2
    Connect HubSpotCRM, deals, marketing, support.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.