More Resources
Prompt

Post a daily pipeline brief to Slack every morning

Time to build: 2 min
Difficulty: Easy
Tools: Claude ▪ Gmail ▪ Google Calendar ▪ Lusha ▪ Slack

Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha, Gmail, Calendar, and Slack connector output, but were not pulled from a live session. Run the prompt with your own data and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.

Before the first call of the day, this Claude prompt pulls today’s external meetings from Google Calendar, checks Gmail for threads that have gone silent, runs a quick contact health check via Lusha, and posts a structured morning brief to Slack. Every rep and manager starts the day with the same picture — no standup needed.

The prompt

Open in Claude Open in ChatGPT 
<context>
Before the day starts, I want a morning pipeline brief posted to our team Slack channel — today's external meetings, any unanswered threads that need attention before EOD, and a quick contact health check on any deal touching a call today. One post, one channel, everything the team needs to start the day aligned.

My setup:
- Slack channel: [CHANNEL NAME — e.g. #pipeline or #team-sales]
- Team members to tag: [NAMES OR "tag the deal owner per item"]
- What I sell: [PRODUCT / SOLUTION]
- Pipeline stage focus: [ALL ACTIVE DEALS / PROPOSAL AND BEYOND / SPECIFIC STAGE]
</context>

<task>
1. Pull today's external meetings from Google Calendar:
   - Company, attendees, meeting type, time
   - Flag any meeting with no prep email sent in the last 48 hours

2. Search Gmail for any active deal thread with no reply in 7+ days:
   - Deal name, company, last outbound topic, days since last touch
   - Flag if there's an outstanding commitment or unanswered question in the thread

3. Use Lusha to run a quick contact health check on every deal with a meeting today:
   - Primary contact still at the company?
   - Title current?
   - Any account signal in the last 14 days?

4. Build the morning brief and post to Slack:

   Format — one structured post, *bold* key fields:

   *Good morning — pipeline brief for [DATE]*

   *TODAY'S CALLS*
   For each external meeting: time, company, verified attendee names and titles, one thing to know

   *THREADS NEEDING ATTENTION TODAY*
   For each thread 7+ days without reply: deal, last topic, days silent, recommended action

   *CONTACT FLAGS*
   Any contact issue detected via Lusha — departed, title changed, signal detected

   *SUMMARY*
   X calls today · X threads need attention · X contact flags

5. Tag the relevant deal owner next to each item.
</task>

<constraints>
- Post to Slack. Don't return as text only.
- Keep the brief scannable — reps read this on their phone before the first call.
- ONE THING TO KNOW per meeting must be specific — not "be prepared."
- If there are no flags or silent threads, say so — don't pad the output.
- SUMMARY line is for the manager, not just the rep.
</constraints>

What you'll get back

The situation: A sales manager runs this every morning for a team of three AEs. Posted to #pipeline before 8:30am. Tuesday, two external meetings on the calendar, three threads overdue for a reply.

Slack post — #pipeline — Tuesday May 27

Good morning — pipeline brief for Tuesday, May 27

TODAY’S CALLS

10:00am — WD — Discovery follow-up · @sarah.ae S.R., VP of Sales ✓ · D.K., Head of Sales Ops ✓ ⚠ No prep email sent in the last 48 hours. One thing to know: S.R. asked about HubSpot integration 9 days ago and is still waiting on an answer. Address it before anything else on the call.

2:00pm — [Sales enablement SaaS} — Proposal demo · @james.ae B.N., Sr Director RevOps — ⚠ Lusha contact flag: B.N. may have departed. Verify before joining. Replacement found: J.S., VP RevOps — j.s@[h***s***].com ✓ One thing to know: B.N. committed to looping in VP RevOps before this call. That intro never happened. Confirm who is actually joining before you start the demo.

THREADS NEEDING ATTENTION TODAY

⚠ [collaborative AI workspace] expansion · @james.ae · 38 days silent Last topic: enrichment workflow case study — promised but never sent. Action: Send the case study before EOD or re-schedule the conversation.

⚠ [Sales content SaaS] new business · @sarah.ae · 14 days silent Last topic: pricing follow-up after discovery. No reply from either side. Action: One-line check-in referencing the pricing question before EOD.

⚠ [Revenue orchestration platform] RevOps · @tom.ae · 11 days silent Last topic: integration with Salesforce — question unanswered. Action: Answer the Salesforce integration question today. Deal is at Proposal — silence at this stage is a risk signal.

CONTACT FLAGS

🔴 [Sales enablement SaaS] — B.N. may have departed (see call note above) ⚠ [Customer support SaaS] — A.L. promoted from VP to SVP since last email — update CRM title before next touch

2 calls today · 3 threads need attention before EOD · 1 contact departed (Sales enablement SaaS) · 1 title change (Customer support SaaS)

Thread and calendar data based on live Gmail and Calendar connector field format. Contacts verified against live Lusha data, May 26, 2026. Names masked to initials.

Why use Lusha in Claude

The [Sales enablement SaaS] flag is what justifies running this every morning. Without the brief, James joins a Proposal demo at 2pm without knowing the primary contact may have left and the buying group intro was never made. The brief surfaces that at 8:30am — giving the AE five hours to verify and adjust. The [collaborative AI workspace] thread flag — 38 days, promised case study never sent — is the kind of thing a rep knows but doesn’t prioritize until it’s too late. A manager who sees it in the morning brief can address it in a 30-second Slack message before the day gets away from the team.

Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.

FAQ

  • Who runs this — the manager or each rep?

    Either works. A manager running it for the whole team gets the cross-team view and can address systemic gaps. A rep running it for a personal pipeline gets a personal morning checklist. The Slack channel determines the audience — post to #pipeline for the team view, to a personal channel for the individual view.

  • Can I run this automatically every morning?

    Not natively in Claude — the prompt runs on demand. For fully automated daily posts, use the Lusha + Zapier or n8n automation plays which support scheduled triggers. This play is for teams that want the brief on demand with a manual run each morning.

  • What if there are no threads needing attention and no contact flags?

    The prompt posts: “No threads overdue · No contact flags — clean day.” That’s a useful output — it confirms the team’s pipeline is in good shape without requiring anyone to check individually.

  • How is this different from the daily meeting brief?

    The daily meeting brief is a personal pre-call brief for one person — one screen per meeting, designed for individual prep. This prompt is a team brief posted to Slack — covers the whole pipeline including threads and contact flags, designed for manager visibility and team alignment. Use the meeting brief for personal prep, use this one for the team’s morning operating view.

Related Prompts

Ready to run this?

One data connection. Works in Claude, ChatGPT, your CRM, or any agent you build.

Start for free Read the Docs