Do I need a paid BuiltWith plan?

Yes, if you want the full tech profile and the recommendations. Free BuiltWith accounts only return aggregate counts, not the vendor-level detail this brief is built around.

What happens if tomorrow's calendar has no external meetings?

Nothing. The workflow simply does not send any messages on days where every meeting is internal.

What if I have multiple external attendees from different companies in one meeting?

The brief covers all of them. Each unique prospect domain is researched once, then the brief lists every external attendee and rolls up the stack highlights per company.

What if BuiltWith has no data on a prospect?

You still get the brief with the attendee list and a short note that no tech profile is available, so you are not left in the dark on the day of the call.

Can it post to a sales channel instead of my DMs?

Yes. Ask the workflow to send the briefs to a private Slack channel and it will post each meeting's brief there instead of as a personal message.

Pre-Meeting Prospect Briefs in Slack | General Input

Build me an agent workflow that drafts a pre-meeting prospect brief for every external meeting on tomorrow's calendar and DMs each one to me in Slack before the workday starts.

Trigger: cron, every weekday (Monday through Friday) at 6:30am in my local time zone.

Steps:

1. Pull tomorrow's events from my primary Google Calendar using the Google Calendar List Events operation. Set timeMin to tomorrow 00:00 and timeMax to tomorrow 23:59 in my time zone, with singleEvents=true and orderBy=startTime. Skip events whose status is cancelled.

2. Filter to external meetings: keep only events where at least one attendee's email domain is different from my own internal email domain. Ask me for my internal domain at setup (for example, acme.com) and remember it.

3. For each external meeting, collect the distinct external attendee email domains. Treat consumer mailbox domains (gmail.com, yahoo.com, outlook.com, hotmail.com, icloud.com, proton.me) as unknown: still list those attendees in the brief, but skip the tech-stack lookup for them.

4. For each distinct prospect domain, call BuiltWith Domain API Lookup to get the live tech stack plus contact metadata, and BuiltWith Recommendations API Lookup to get technologies that similar sites use which this prospect is missing or likely to adopt next. Only look up each unique domain once even if it appears across multiple meetings.

5. For each meeting, draft a tight one-page brief with these sections:

- Subject line: "Pre-call brief: {company name} at {start time, local}"

- Who's attending: every external attendee with email and inferred role if obvious, plus the internal attendees from my side

- Prospect snapshot: CMS, ecommerce platform, analytics stack, ad and martech stack

- Standout vendors that hint at maturity, scale, or budget (enterprise CDPs, data warehouses, premium analytics, paid security tools, etc.)

- Likely tech gaps or next-up bets from the Recommendations lookup, with a one-line reason each

- Two or three talking points or tech-led questions the rep could open the call with

6. Send each brief as a separate Slack direct message to me using the Slack Send a Message operation. The recipient is my own Slack user ID (open a DM with myself). One Slack message per meeting. The first line of the message is the subject line in bold using Slack mrkdwn (*bold*), followed by the rest of the brief.

Edge cases and behavior:

- If tomorrow has no external meetings, send nothing. Do not send a "nothing scheduled" message.

- If a BuiltWith lookup returns no data for a domain, still send the brief and note "no public tech profile available" instead of skipping the meeting.

- If two meetings include the same prospect domain, reuse the same BuiltWith results across both briefs (do not duplicate the API calls).

- Order the messages by the meeting's start time so the first DM is the earliest call of the day.

Use the Slack user OAuth integration (not the bot integration) so the DM appears in my own messages as if I sent it to myself.

What it does

Looks at tomorrow's calendar and singles out external meetings, ignoring internal syncs
Researches each prospect company's live website tech stack: CMS, ecommerce platform, analytics, ad tools, and standout vendors
Surfaces technologies a similar site is likely to adopt next, so you walk in with a forward-looking angle
Drafts a tight one-page brief per meeting with attendees, stack highlights, and two or three opening talking points
Sends each brief as a Slack direct message with a clearly labeled subject line so it's easy to find before the call

What you’ll need

A Google Calendar account (the one your meetings are booked on)
A Slack account with permission to send yourself direct messages
A BuiltWith account and API key (a paid plan is recommended for the full tech profile and the recommendations lookup)
Your company's email domain, so the workflow knows which meetings count as external

How to customize it

Shift the run time earlier or later, or schedule it the evening before instead of the morning of
Change which meetings count as external by adding partner domains, investors, or recurring 1:1s to a skip list
Adjust the brief format: longer or shorter, more product angles, more discovery questions, a specific opener
Send to a private Slack channel for your sales pod instead of a personal DM

Use cases

Meeting Workflows
Lead Enrichment
Research & Monitoring

Daily Slack briefs for tomorrow's prospect meetings

Integrations

Type

Categories

What it does

What you’ll need

How to customize it

Use cases

FAQs

Related prompts