Daily Warmly warm accounts briefing in Slack

Every weekday at 8am ET, post a ranked morning briefing of yesterday's warm accounts and visitors from Warmly to a dedicated Slack channel, with a 3 to 5 sentence reason to reach out today.

Agentic Task
WarmlySlack BotSalesDaily DigestsNotifications & AlertsLead Enrichment
PromptCreate

Build an agent workflow that posts a daily warm-account briefing from Warmly into Slack. Trigger: cron, every weekday (Mon-Fri) at 8:00 AM America/New_York.

On each run, the agent should do the following:

1. Use Warmly's List Warm Accounts to fetch all warm accounts from the last 24 hours, and Warmly's List Warm Visitors to fetch all identified visitors from the same window. Paginate (take/offset) until the page is shorter than the take size so the agent has the full day of data, not just the first page.

2. For each warm account, combine the account-level signal (number of sessions, distinct pages, identified visitors) with the matching visitor records to determine intent. Rank by: (a) multiple sessions on the same account, (b) decision-maker seniority on the visitor's title (VP, Director, Head of, C-level), and (c) visits to high-intent pages, especially anything that looks like pricing, demo, contact, or product pages.

3. Use the CRM-intersection field that Warmly returns on each account to label the account as either 'Net-new' (not in CRM) or 'Already in pipeline' (matched to an existing CRM record).

4. Pick the top 8 to 10 accounts only. The whole point is that reps actually read it, so do not exceed 10.

5. For each of those top accounts, write 3 to 5 sentences explaining why a rep should reach out today: what the account does, who visited and their title, the highest-intent page(s) they viewed, the pipeline status (net-new vs already in pipeline), and a concrete suggested next step.

6. Send a single message to a dedicated Slack channel (ask the user which channel during setup) using Slack Bot's Send a Message. Format the digest as Slack mrkdwn: a header line with the date, then each account as a numbered block with the account name in *bold*, a one-line tag for 'Net-new' or 'Already in pipeline', the visitor's name and title, the top 1 to 3 pages they viewed, and the 3 to 5 sentence write-up. Keep the message scannable: short blocks, clear separators, no walls of text.

7. If the last 24 hours had zero qualifying warm accounts, post a short single-line message saying so. Do not skip the post, the channel should be predictable.

Notes for the build: Warmly is read-only for this workflow (no writes, no credits consumed beyond list reads). All Warmly calls go through the agent-tools execute path with the workspace's Organization ID. The Slack channel and time zone should be configurable. Do not @-mention anyone in the digest by default.

Additional information

What does this prompt do?
  • Pulls the last 24 hours of warm accounts and identified visitors from Warmly each weekday morning before reps start their day.
  • Ranks accounts by intent signal: number of sessions, decision-maker seniority on the visitor, and visits to high-intent pages like pricing or demo.
  • Flags which accounts are net-new versus already in your pipeline using the CRM match field Warmly returns.
  • Posts a single, scannable digest of the top 8 to 10 accounts to a dedicated Slack channel, with bolded account names, the visitor's title, the highest-intent pages they viewed, and 3 to 5 sentences on why this rep should reach out today.
What do I need to use this?
  • A Warmly workspace with API access enabled, plus your Warmly Organization ID.
  • A Slack workspace and a channel where the briefing should land (for example, a dedicated warm-traffic or website-visitors channel).
  • Permission to install a Slack bot in that workspace and invite it into the briefing channel.
How can I customize it?
  • Change the schedule or time zone (for example, 7am PT for a West Coast team, or run twice a day).
  • Swap the Slack channel, route to multiple channels, or DM specific reps based on territory.
  • Adjust what counts as a high-intent signal (which pages matter, which titles qualify as a decision maker) or change the cap from 8 to 10 accounts to a different number.
  • Filter out accounts that are already won, lost, or owned by a specific rep so the briefing only surfaces opportunities worth acting on.

Frequently asked questions

Will this work for an account that is already in our CRM?
Yes. Warmly returns a CRM match field on each warm account and visitor, and the briefing uses it to label each account as net-new or already in pipeline so reps know whether to prospect or follow up.
How does it decide which accounts make the top 8 to 10?
It scores each account on intent signals: number of sessions, decision-maker seniority on the identified visitor, and visits to high-intent pages like pricing or demo. You can change which signals matter most after you set it up.
Can I send the briefing somewhere other than Slack?
Yes. The briefing format is built for Slack, but you can route the same digest to a different channel, several channels, or even individual reps by DM. Email or other destinations work too with a small tweak.
What happens on days with no warm traffic?
When the last 24 hours are empty, the briefing posts a short note that there were no qualifying warm accounts so the channel stays predictable and reps know the workflow is healthy.
Does this use a lot of Warmly credits?
Reading the list of warm accounts and visitors is free in Warmly. Credits are only consumed when you actively identify new visitors, which this briefing does not do on its own.

Stop scrolling Warmly every morning.

Connect Warmly and Slack once, and your reps get a ranked, reason-to-reach-out briefing in their channel every weekday at 8am.