Daily Slack digest of yesterday's hottest website visitors

Each weekday at 9am, your sales team gets a Slack message with the highest intent companies that visited your site yesterday and why each one matters.

Agentic Task
LeadfeederSlack BotSalesDaily DigestsNotifications & AlertsLead Enrichment
PromptCreate

Build me a daily sales intelligence digest that posts yesterday's highest intent website visitors to Slack every weekday at 9am in my timezone.

Trigger: cron, every weekday (Monday through Friday) at 9:00am. The schedule should be configurable.

Step 1 — Pull yesterday's leads from Leadfeeder. Use Leadfeeder's List Leads operation against a custom feed I choose at setup, with start_date and end_date both set to yesterday's date in my local timezone. Treat all Leadfeeder IDs as strings.

Step 2 — For the most promising leads from step 1, call Leadfeeder's List Visits For Lead to pull session-level page detail so we can cite which specific pages they hit (pricing, demo, integrations, contact, etc.) and roughly how long they spent. Cap this enrichment to the top 15 or so candidates by Leadfeeder's lead score so we don't blow the rate limit.

Step 3 — Rank the leads with a combined score that rewards higher page count, visits to key pages (pricing, demo, integrations, contact, careers signals), and second-or-later-session status (returning visitors are hotter than first touches). Pick the top 5 to 10 (default 7, configurable).

Step 4 — Post a single Slack message to a channel I pick at setup using the Slack Bot Send a Message operation. Use Slack mrkdwn formatting (single asterisks for bold, not double). Structure: a one-line header like ‘Top intent visitors for <date>’, then a numbered list. For each company include the company name, domain, country, the Leadfeeder lead score, 2–3 standout pages they viewed, and a one-line ‘why this matters’ rationale a rep can read in two seconds. Keep the message short enough to skim before standup.

Step 5 — Empty-state behavior. If List Leads returns no qualifying companies for yesterday, post a short fallback like ‘No qualifying visitors yesterday.’ to the same channel instead of skipping silently — the team should always see that the check ran.

Configuration knobs to expose at setup: the Leadfeeder custom feed ID, the Slack channel, the number of companies to show (5–10), the schedule, and the timezone used to compute ‘yesterday’.

Use the Slack Bot integration (not the user-OAuth Slack integration) because this is automated workspace messaging, not acting as a specific person. Use Leadfeeder for the data side.

What does this prompt do?

  • Pulls yesterday's website visitor companies from your Leadfeeder custom feed every weekday morning.
  • Ranks the top 5 to 10 accounts by intent signals like pages viewed, key pages hit, and whether it was a return visit.
  • Posts one tidy Slack message with each company's name, country, score, the standout pages they viewed, and a one line reason it matters.
  • If nothing qualifying came in yesterday, still posts a short heads up so the team is never left guessing.

What do I need to use this?

  • A Leadfeeder account with at least one saved custom feed for the companies you care about.
  • A Slack workspace where the Slack bot can post in the channel you choose for the digest.
  • A few minutes to pick the channel, the time of day, and how many companies you want in each digest.

How can I customize it?

  • Change the schedule to a different time of day or run it seven days a week instead of weekdays.
  • Swap the channel, or send to multiple channels for different regions or sales pods.
  • Tune the ranking rules, the number of companies in the digest, or which pricing and demo pages count as high intent.

FAQs

Do I need a paid Leadfeeder plan for this?
Yes. Custom feeds and the ability to filter leads by feed are part of Leadfeeder's paid plans. Once you have a custom feed set up, this workflow can read from it on a schedule.
Where in Slack will the digest land?
Wherever you choose. You pick the channel during setup, and you can change it any time. The bot needs to be invited to private channels first.
What if no companies visited yesterday?
The workflow still posts in your channel with a short 'no qualifying visitors yesterday' note so the team knows the check ran and there was simply nothing to act on.
Can I send it to more than one channel?
Yes. You can run the workflow once for each channel, or extend it to fan out the same digest to multiple channels at once.
Why a one line summary per company instead of raw data?
Reps decide in seconds whether to chase a lead. A short, plain English reason next to the standout pages they viewed makes it easy to pick the right accounts before standup.

Related templates

Build a credential rotation checklist when someone leaves

When someone leaves, we check which shared passwords they used in their final months and post a ranked rotation list to your security channel.

1Password
Rippling
Slack Bot
+1
Agentic Task
Weekly Amazon S3 bucket security audit posted to Slack

Every Monday, check every S3 bucket for public exposure, missing encryption and weak backup settings, then get the risks ranked in Slack.

Amazon S3
Slack Bot
Google Sheets
Agentic Task
Log Agorapulse social conversations to HubSpot contacts

Twice every weekday, the conversations from your social inbox land on the right HubSpot contact timelines, with a Slack recap for sales.

Agorapulse
HubSpot
Slack Bot
Agentic Task
Clean up HubSpot contacts from your Amazon SES suppression list

Every morning, find the addresses that hard bounced or filed a spam complaint, update the matching HubSpot contacts, and post a short Slack recap.

Amazon SES
HubSpot
Slack Bot
Agentic Task
Draft polite follow-ups for emails that never got a reply

Every weekday at 4pm, spot the threads that went quiet, stage a ready-to-send nudge in your mailbox, and get a ranked Slack recap.

Aurinko
Google Sheets
Slack Bot
Agentic Task
Replay failed SQS messages when a bug fix is merged

When you merge a fix in GitHub, this agent checks the matching dead-letter queue, replays the failed messages, and reports back on the pull request and in Slack.

Amazon SQS
GitHub
Slack Bot
Agentic Task

Stop chasing cold leads while warm ones get forgotten.

Connect Leadfeeder and Slack once, and your sales team starts every morning with the companies most worth their time.