Weekly Crunchbase watchlist digest in Notion and Slack

Every Monday at 8am in my local timezone, run a competitor watchlist sweep and produce both a per-competitor activity log in Notion and a single ranked digest in Slack.

Trigger: cron, every Monday at 8am. Crunchbase is not a poll provider and does not push webhooks, so a schedule is correct here.

Inputs the workflow should ask me to configure on first run: the Notion data source ID of my competitor watchlist database (one row per tracked competitor, with at least a company name property and a Crunchbase permalink or profile URL property), the Notion target where activity log pages should be written (either child pages under each competitor row, or a dedicated activity log database keyed by competitor name), and the Slack channel ID for the Monday digest.

Step 1: Use Notion Query a Data Source to read every row of my watchlist database. For each row extract the competitor name and the Crunchbase permalink (or fall back to UUID if that is what is stored).

Step 2: For each competitor, call Crunchbase Lookup Organization using the permalink, then Crunchbase Get Entity Card to pull related cards like press references, key people, and leadership changes, and Crunchbase Search Funding Rounds filtered to that organization with announced_on in the last seven days. Use the last-seven-days window for press, leadership changes, and acquisitions as well. Skip any competitor with no meaningful change rather than padding the output.

Step 3: For each competitor that did move, summarize what changed in plain language across funding rounds, acquisitions, leadership changes, and recent press. End each summary with a one-line so-what implication aimed at a product and GTM reader. Use Notion Create a Page to write that summary back into Notion as an activity log entry, either as a child page under the competitor's row or as a new page in the dedicated activity log database keyed by competitor name, whichever the user picked at setup. Include the date range in the page title.

Step 4: After all competitors are processed, rank the changes by strategic meaningfulness (a real funding round, named acquisition, or C-suite change outweighs routine press), pick the top three, and use Slack Send a Message via the Slack Bot integration to post a single digest to the configured channel. Format the message with a short header, three numbered items, each with the competitor name, a one-line change description, the one-line so-what, and a link back to the Notion activity log entry for the full write-up. Do not pad the digest with quiet competitors. If fewer than three competitors moved, post fewer items and say so.

Use the Slack Bot integration (slackbot) for the digest message, not the user Slack integration, because the post should come from a shared bot identity, not a specific person.

Quality bar: the agent must skip competitors with no real change instead of writing empty Notion pages or padding the Slack digest. The Notion watchlist is the single source of truth for who is tracked, so do not maintain a separate list anywhere.