CloseNotion

Log Close opportunities to a Notion pipeline database

A Close + Notion agent flow

Sales runs the pipeline in Close, but the weekly revenue review happens in a Notion doc that someone rebuilds by hand every Friday. That copy-paste is the whole job this flow removes. The agent reads opportunities with find_opportunities, filtered to the ones created or won in the period you care about, and writes a page per opportunity into a Notion database with notion-create-pages, mapping the value, the lead, the status, and the close date onto your columns. Close answers the call when the agent asks, so you set the cadence, daily or before each review, and the agent reads then writes, skipping opportunity IDs it already logged.

The flow

Closefind_opportunities

Finds opportunities filtered by lead, user, status, and dates.

Notionnotion-create-pages

Creates one or more Notion pages with specified properties and content.

Step by step

  1. Shape the Notion database

    Create a database with the columns the review needs: opportunity value, lead name, status, expected close date, and owner, so the agent has real properties to populate.

  2. Read the opportunities

    The agent calls find_opportunities with a status and date filter, for example everything won this week, and reads the value, the lead, the status, and the dates on each.

  3. Write one page per opportunity

    It calls notion-create-pages with those fields mapped to your columns. Store each opportunity ID in a property so a re-run updates rather than duplicates.

Tell your agent

Every weekday at 6pm, find Close opportunities won in the last 24 hours. For each one, add a page to the Pipeline database in Notion with the value, lead name, status, owner, and close date. Record the opportunity ID in a property and skip any ID already logged.

Setup

This flow needs both servers connected to your agent. Follow each install guide:

Worth knowing

  • find_opportunities returns the opportunity record; the lead's company name lives on the lead, so the agent may need fetch_lead to resolve it before writing a readable row.
  • notion-create-pages needs the target database ID and exact column names up front. Give the agent both, or fields silently land in the wrong place.
  • Close paginates results. On a first backfill, cap the date window so the agent doesn't write the entire opportunity history into Notion in one run.

Questions

Can it log only closed-won, not every stage?
Yes. find_opportunities filters by status, so point the agent at your won status ID and it reads only those, leaving open and lost opportunities out of the Notion log.
Does it update a row when an opportunity's value changes?
If you key on the opportunity ID it can. The agent looks up the existing page by that ID and calls notion-update-page; without the key it would create a duplicate instead.