Daily product-qualified lead alerts from Amplitude to Slack

Every weekday at 9am, surface product-qualified leads to sales by pulling the members of our designated PQL behavioral cohort from Amplitude, enriching each user against HubSpot, and posting a hot-lead summary to the sales channel in Slack.

Start the run by requesting a cohort download from Amplitude for the configured PQL cohort ID. Amplitude runs the export asynchronously, so poll the download status until async_status reports JOB COMPLETED, then download the CSV of user IDs and emails. The generated CSV URL is valid for seven days, so grab it as soon as the job is done.

For every user in the CSV: search HubSpot contacts by email to find the matching contact record. If no HubSpot contact exists, skip the user and note it in the run log. Then fetch that user's recent activity from Amplitude by their Amplitude ID so we can see what they actually did over the last few days. Look up the HubSpot contact owner (via the Owners endpoint) so we can tag them in Slack.

Write a two to three sentence hot-lead summary for each user covering: what they did (top signals from the recent activity), why it matters for the deal, and a suggested next touch for the sales rep. Keep it concrete; reference the exact events or pages that lit up, not just "lots of activity".

Post one Slack message per new PQL to the configured sales channel using the Slack bot. Look up the contact owner's Slack user ID by their email address so the @-mention actually notifies them, and include the contact's name, company, a link to the HubSpot record, and the hot-lead summary in the message body.

Finally, update the HubSpot contact by bumping a configurable property, for example a numeric "PQL Score" or a datetime "Last PQL Trigger", so downstream HubSpot sequences and workflow rules can react to the trigger.

Dedupe: keep an internal list of users we've already alerted on within the operator's chosen window (default seven days) so the same person doesn't get re-posted every morning. The cohort ID, target Slack channel, HubSpot property to bump, and dedupe window are all inputs the operator configures at setup.

Reference: Amplitude's HubSpot cohort sync destination pattern (https://amplitude.com/docs/data/destination-catalog/hubspot-cohort-sync), extended with per-user narrative and Slack alerting so reps get a story rather than just a list.