Turn content downloads into useful conversations
Personalise the follow-up around what someone read instead of dropping every lead into the same sequence.
content-download-nurture.md
Turn content downloads into useful conversations
Set up the tools below, then run the steps in order for the user.
Inputs
Ask the user for these before you start.
content_asset: the asset that was downloaded, e.g. The 2026 outbound benchmarkfollow_up_window: how far back to look, e.g. 3 daysnurture_log: the Notion database that logs each send
Set up
Search CRM records (HubSpot, tool:hubspot/search-crm-records)
Use the first option your agent supports.
MCP (official, remote)
Add this server to your agent's MCP settings, then sign in when asked.
{ "mcpServers": { "hubspot": { "url": "https://mcp.hubspot.com" } } }
Call the MCP tool search_crm_objects.
API (official)
- Base URL: https://api.hubapi.com
- Endpoint:
POST /crm/objects/2026-09/{objectType}/search - Auth: send the header
Authorization: Bearer $HUBSPOT_API_KEY
Brew (tool:brew/generate-email, tool:brew/send-email)
Use the first option your agent supports.
MCP (official, remote)
Add this server to your agent's MCP settings, then sign in when asked.
{ "mcpServers": { "brew": { "url": "https://brew.new/api/mcp" } } }
- Generate an email: call the MCP tool
create_email - Send an email: call the MCP tool
send_email
CLI (official)
Install the command, then confirm it runs.
brew install getbrew/tap/brew-cli
brew-cli --version
- Generate an email: run
brew-cli emails generate - Send an email: run
brew-cli emails send
Set $BREW_API_KEY in your environment first (get a key: https://brew.new/settings/api).
Create a page (Notion, tool:notion/create-page)
Use the first option your agent supports.
MCP (official, remote)
Add this server to your agent's MCP settings, then sign in when asked.
{ "mcpServers": { "notion": { "url": "https://mcp.notion.com/mcp" } } }
Call the MCP tool notion-create-pages.
CLI (official)
Install the command, then confirm it runs.
npm install --global ntn
ntn --version
Run ntn api v1/pages.
Set $NOTION_API_TOKEN in your environment first (get a key: https://www.notion.so/developers/tokens).
Make one read-only call to each tool to confirm access.
Steps
- Pull downloads with Search CRM records (HubSpot). List contacts who downloaded
content_assetwithinfollow_up_window. Keep name, company and email. - Write follow-ups with Generate an email (Brew). Draft one email per contact that references a specific section of the asset. Show the drafts to the user.
- Send with Send an email (Brew). Send each approved email to its contact.
- Log the send with Create a page (Notion). Append one row per sent email to
nurture_logwith contact, asset and date.
Done when
- Every download in the window has a follow-up sent or declined.
- The nurture log has one row per send.
Rules
- Only use the tools listed above.
- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.
Built from these files in the repository
- workflows/content-download-nurture.md
- companies/hubspot/tools/search-crm-records.md
- companies/hubspot/company.md
- companies/brew/tools/generate-email.md
- companies/brew/company.md
- companies/brew/tools/send-email.md
- companies/notion/tools/create-page.md
- companies/notion/company.md
The layout and the rules come from lib/catalog/render-markdown.ts, the set-up wording from lib/catalog/render-access.ts.
