End-of-day Nooks dialing digest in Slack

By General Input

Every weekday at 5pm ET, post a Slack recap of the team's Nooks dials, connects, meetings booked, and a per-rep leaderboard.

Integrations

  • Nooks
  • Slack Bot

Type

Agentic Task

Categories

  • Sales
  • Operations

Build an agent workflow that runs every weekday at 5pm America/New_York and posts an end-of-day dialing digest from Nooks to a configured Slack channel using the Slack Bot integration. One Slack message, sectioned for skimming, no em dashes anywhere in the copy.

Inputs the user configures on this workflow: the Slack channel ID (or channel name) to post into, an optional list of Nooks user IDs to scope the digest to a specific team, and an optional toggle for the zero-activity callout (default on).

Each run, the agent should:

1. Resolve today's window in America/New_York (midnight to 5pm local, converted to ISO 8601 with timezone offset). Use Nooks List Calls with a time filter for the day, paginating through all results. If a team scope is configured, also filter by owner.

2. Call Nooks List Users to map owner IDs to rep names. Call Nooks List Call Dispositions to translate the workspace's disposition IDs into human-readable labels. Workspace dispositions are not standardized, so always resolve them dynamically. Identify which dispositions count as a connect, a meeting booked, and a callback by matching on the label text (e.g. "Connected", "Meeting Booked", "Callback"); if the workspace uses different labels, pick the closest semantic match and note the chosen mapping in a small footer.

3. Compute the day's totals: total dials, connect rate (connects divided by dials), meetings booked, callbacks. Build a per-rep leaderboard with dials, connects, connect rate, and meetings booked, sorted by connects descending. Include reps from List Users who had zero calls today in a separate "No activity today" list (skip this section if the toggle is off).

4. Highlight up to three standout positive outcomes from the day, prioritizing meetings booked and then high-value connects. For each highlight, include the rep name, the prospect name, and the account name. Pull prospect details with Nooks Get Prospect only when the call payload does not already include the names, and follow the account href from the prospect to get the account name.

5. Format one Slack message using Slack mrkdwn (`*bold*`, `_italic_`, `<url|text>`), with clear sections: a header with the date, a totals line, the leaderboard as a code block or bulleted list (whichever renders cleaner for the team size), a "Standouts" section, and the optional "No activity today" list. Keep it scannable; no em dashes; use periods or commas instead.

6. Post the message with the Slack Bot Send a Message operation to the configured channel. If the bot is not in the channel and the workspace allows it, attempt to post to the public channel directly; otherwise surface a clear setup error telling the user to invite the bot.

Edge cases: if there were zero calls in the window, still post a short message saying so (do not skip silently). If Nooks returns a 429, honor Retry-After and continue. If List Call Dispositions returns no matching label for a category (e.g. no "Meeting Booked" equivalent), omit that metric rather than guessing. Do not invent rep names or accounts; if a call has no resolvable owner or prospect, group it under "Unattributed".

Trigger: cron, every Monday through Friday at 17:00 America/New_York. Integrations: Nooks (API key) and Slack Bot (OAuth).

Related prompts

Explore more prompts
A brand asset library your marketing team actually searchesTurn Mailjet email clicks into ranked HubSpot follow-upsClean out the Looker dashboards and Looks nobody opensLiveKit live operations console for room moderationWake up dormant Keap leads with a researched reasonLiveChat coverage board for planning next week's shiftsPhone routing control panel for LiveKit voice agentsLinkedIn Ads budget pacing dashboard for every client accountGive your team Looker numbers without buying more seatsPause marketing emails to escalated customers, then restore them