Daily product-qualified lead alerts from Amplitude to Slack

Every weekday, pull your PQL cohort from Amplitude, enrich each user in HubSpot, and post a hot-lead summary to your sales channel in Slack.

Agentic Task
AmplitudeHubSpotSlack BotSalesProductNotifications & AlertsLead Enrichment
PromptCreate

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.

Additional information

What does this prompt do?
  • Pulls today's members of your product-qualified lead cohort from Amplitude, waits for the export to finish, and reads the resulting user list.
  • Matches each user to their HubSpot contact and pulls their recent in-product behavior so the agent can write a two to three sentence hot-lead summary: what they did, why it matters, and a suggested next touch.
  • Posts one Slack message per new PQL to your sales channel, tagging the HubSpot contact owner so the right rep sees it immediately.
  • Stamps a PQL Score or Last PQL Trigger property on the HubSpot contact so your existing sequences and workflows can react.
  • Remembers who has already been alerted on within a configurable window so the same person isn't re-posted every morning.
What do I need to use this?
  • An Amplitude project with a behavioral cohort that captures your product-qualified leads
  • A HubSpot account with contacts and a property to bump (a numeric score or a date field)
  • A Slack workspace and a channel where sales should be pinged
How can I customize it?
  • Change the schedule: weekdays at 9am is a starting point, but you can run it hourly, only on specific days, or across multiple cohorts.
  • Swap the cohort, the target Slack channel, or the HubSpot property being bumped without touching the rest of the workflow.
  • Adjust the dedupe window so the same user isn't re-alerted if they stay in the cohort for several days.

Frequently asked questions

How is this different from Amplitude's native HubSpot cohort sync?
Amplitude's built-in HubSpot cohort sync is an enterprise add-on that mirrors cohort membership onto contact lists. This workflow gives you the same PQL alerting pattern without the enterprise SKU, and adds a per-user narrative summary of what they did and why it matters, plus a Slack ping that tags the contact owner.
Do I need a specific Amplitude plan?
Any plan that supports behavioral cohorts and cohort exports works. If your team already builds cohorts in Amplitude, you have what you need.
What happens if a cohort member isn't in HubSpot yet?
The user is skipped and noted in the run log, so nothing breaks. If this happens often, it's usually a sign to tighten upstream lead capture so more of your active users are in the CRM.
Will the same person get alerted every day they stay in the cohort?
No. The workflow remembers who it has already surfaced within a configurable window (default seven days), so reps only get pinged about a genuinely new PQL.
Can I customize the Slack message or route to multiple channels?
Yes. You can change the channel, the message format, or add routing rules (for example, send enterprise-tier users to a separate channel) when you configure the workflow.

Related templates

Braintree
Slack Bot

Daily Braintree declined-payment recovery digest to Slack

Every weekday at 8am, your billing team gets a Slack rundown of yesterday's failed Braintree charges, the revenue at risk, and who to chase first.

6d ago

Agentic Task
Prompt
Azure DevOps
Slack Bot

Weekday Azure DevOps sprint standup digest in Slack

Every weekday morning, roll up your sprint's work items into a clear per-person standup summary and post it to your team's Slack channel before you meet.

6d ago

Agentic Task
Prompt
Braintree
Zendesk
Slack Bot

Track new Braintree disputes before the deadline slips

Every three hours we scan Braintree for new disputes and chargebacks, open a tracked ticket with a tailored evidence checklist, and alert your team in Slack before the response deadline slips.

6d ago

Agentic Task
Prompt
Databricks
Slack Bot

Daily Databricks data health check with Slack alerts

Every weekday morning we check your most important Databricks tables for freshness and data problems, and ping Slack only when something actually looks wrong.

6d ago

Agentic Task
Prompt
Have I Been Pwned
Slack Bot

Monday morning employee breach exposure briefing in Slack

Every Monday, automatically find which employee accounts on your company domain turned up in data breaches and get a plain-English briefing in Slack.

6d ago

Agentic Task
Prompt
Azure DevOps
Slack Bot

Instant Slack alert when an Azure DevOps build fails

When a pipeline build fails, we post a tight Slack card naming who pushed, the likely cause, and a link to the build so on-call can triage in seconds.

6d ago

Agentic Task
Prompt

Turn Amplitude cohorts into a daily sales briefing

Give your reps a heads-up the moment a real user hits PQL, with the story of what they did and who owns them.

Explore more promptsCreate