Daily PitchBook deal log to Google Sheets and Slack

Build a deterministic code workflow that runs on a cron trigger every weekday at 6:00 AM in my local timezone and logs yesterday's PitchBook deals into our team's sourcing Google Sheet, then posts a one-line Slack notification.

Step 1. Use the PitchBook Search Deals operation with a fixed set of thesis filters: sector tags, deal type, geography, deal size range, and a date range covering the last 24 hours (yesterday through the moment the job runs). Paginate through all results. Do not summarize, rank, or filter further. Treat this as a straight pull.

Step 2. For each matching deal, call the Google Sheets Append Values operation against a designated spreadsheet and worksheet. Append one row per deal with these columns in this order: company name, deal type, deal date, amount, lead investor, co-investors (comma-separated), sector, headquarters (city, state/country), and the PitchBook entity URL. Use USER_ENTERED so dates and numbers render correctly.

Step 3. After all rows have been appended, use the Slack Bot Send a Message operation to post a single short message to a designated sourcing channel. The message should state how many new deals were added today and include a link back to the Google Sheet. If zero deals matched, still post the message so the team knows the job ran.

Expose these as configurable inputs at the top of the workflow: the cron schedule, the PitchBook thesis filter values (sectors, deal types, geographies, deal size range), the spreadsheet ID and worksheet name, and the Slack channel ID. Everything else is hardcoded.

Important: this is intentionally a deterministic pipeline. Do not add ranking, scoring, AI summarization, or conditional branching. The value is the auditable, row-level feed. Pair it mentally with a separate digest workflow if I ever want a written summary, but keep this one strictly as an append-and-notify job.

Additional information

What does this prompt do?

Runs a fixed PitchBook search every weekday at 6am for deals that closed in the last 24 hours and match your thesis filters (sector, deal type, geography, deal size).
Appends one row per deal to your team's sourcing Google Sheet with company name, deal type, date, amount, lead investor, co-investors, sector, headquarters, and the PitchBook link.
Posts a short Slack message to your sourcing channel with the count of new deals added and a link back to the sheet.
Keeps a clean, auditable row-level log of new activity so analysts can sort, filter, and pivot without re-pulling data.

What do I need to use this?

A PitchBook account with API access (a separate contract from the standard PitchBook platform login).
A Google account with edit access to the sourcing spreadsheet you want to append to.
A Slack workspace and the name of the channel where the morning notification should land.

How can I customize it?

Change the run time or the days of the week the job fires (for example, run seven days a week or only on Mondays).
Tune the thesis filters: which sectors, deal types, geographies, and deal size bands count as a hit.
Swap the destination spreadsheet, the column order, or the Slack channel that gets the morning ping.

Frequently asked questions

Does this require PitchBook API access, or is a regular PitchBook login enough?

It requires PitchBook API access, which is a separate contract from the standard PitchBook platform login. Your PitchBook account manager can provision it.

Will this overwrite my existing sheet?

No. New deals are appended as additional rows below your existing data, so the historical log keeps growing day over day.

What if no deals match my filters on a given day?

Nothing is added to the sheet, and the Slack message will say zero new deals were logged. You always know the job ran.

Can I change which sectors or deal sizes count as a match?

Yes. The thesis filters (sector tags, deal type, geography, deal size range) are all editable, and the workflow picks them up on the next run.

Why log deals to a sheet instead of just posting a summary in Slack?

The sheet gives you a row-level audit log you can sort, filter, and pivot. Pair it with a written digest if you also want a curated read, but the sheet is the source of truth.