How to Build an AI Agent for HubSpot and Notion

The workflow problem

Marketing teams plan campaigns in Notion because it is flexible, visual, and collaborative. They build content calendars with database views, kanban boards for asset production, and linked briefs for every campaign. But execution happens in HubSpot: email sequences, landing pages, workflows, and lead scoring. The gap between planning and execution creates constant friction.

A content manager finishes a blog brief in Notion and marks it “Ready for Publish.” Nothing happens in HubSpot until someone manually creates the email campaign, builds the landing page, and sets up the workflow. By the time they get to it, the brief has changed, the launch date has shifted, and the social copy was updated in Notion but nobody told the HubSpot operator.

Campaign reporting suffers the same disconnect. HubSpot tracks opens, clicks, form submissions, and MQL conversions, but the marketing team reviews performance in Notion during weekly standups. Someone has to pull numbers from HubSpot, format them, and paste them into the Notion campaign tracker every week. This manual reporting is tedious, error-prone, and always a day behind.

The result is a marketing organization that plans beautifully but executes with friction, delays, and data that is never quite current.

Why an AI agent, not just automation

A basic Zapier integration can push a new Notion database entry to HubSpot when a status changes. But marketing campaigns are not that simple. A single campaign might involve three email sequences, a landing page, two workflows, and a nurture track. The relationships between these assets are contextual, not formulaic.

An AI agent reads the campaign brief in Notion and understands the intent. It knows that a “Product Launch” campaign needs a different HubSpot workflow structure than a “Webinar Registration” campaign. It can interpret a content calendar entry that says “Send follow-up email 3 days after webinar” and translate that into the correct HubSpot workflow delay and email action, without requiring the marketer to speak in HubSpot’s technical language.

For reporting, the agent does not just copy numbers. It interprets performance data. When open rates drop below the campaign’s target, the agent can flag the underperforming email in the Notion tracker with context: “Email 2 in the onboarding sequence has a 12% open rate versus the 22% target. Subject line A/B test showed variant B performed 40% better. Consider updating.”

This intelligence layer transforms the HubSpot-Notion connection from a data pipe into a strategic marketing assistant.

How it works with ACP

ACP connects to HubSpot via OAuth 2.0 and to Notion via its native OAuth integration. The agent operates with scoped permissions on both sides.

HubSpot tools available: Read and create contacts, companies, and deals. Read and create marketing emails. List and manage workflows. Read campaign analytics (open rates, click rates, bounce rates, form submissions). Create and manage lists for segmentation. Read blog posts and landing pages.

Notion tools available: Read and update database entries. Create new pages with structured properties. Add and modify blocks (text, callouts, tables, embeds). Search across the workspace. Create relation links between databases.

The agent bridges these tools through several core workflows. For campaign planning, it watches the Notion content calendar database for entries that reach a “Ready” status. It reads the full campaign brief, identifies the required HubSpot assets, and either creates drafts or flags missing elements for the team.

For performance reporting, the agent queries HubSpot analytics on a schedule and updates the Notion campaign tracker with fresh numbers, trend indicators, and contextual commentary.

Here is what a typical interaction looks like:

User: Update the Q2 content calendar with this week’s HubSpot performance data.

Agent: I pulled performance data for 4 active campaigns from HubSpot and updated the Notion Q2 Content Calendar:

• “DevTools Launch” email sequence: 3,421 sends, 24.1% open rate (above 20% target), 3.8% CTR. Updated Notion status to “Performing Well.”
• “Enterprise Webinar” registration flow: 187 registrations from 2,100 page views (8.9% conversion). Below the 12% target. I added a callout in Notion suggesting a form simplification test.
• “Customer Stories” nurture: 890 contacts in sequence, 31% open rate, but only 0.9% reply rate. Flagged for content review in Notion.
• “Free Trial” onboarding: 412 new contacts entered this week. Completion rate: 67%. On track.

I also noticed that the “AI Buyer’s Guide” blog post in the Notion calendar is marked “Published” but has no corresponding HubSpot distribution workflow. Want me to draft one?

Governance and security

Marketing data spans customer PII, campaign strategies, and revenue metrics. Keeping this data governed across two platforms requires careful scope management.

HubSpot OAuth scopes: The agent requests crm.objects.contacts.read for contact data, content for blog and landing page access, and automation for workflow management. It does not request crm.objects.contacts.write unless you need the agent to create contacts from Notion form responses. Email sending scopes are never requested by default, so the agent can draft but not send.

Notion permissions: The integration is shared only with specific databases (such as the content calendar and campaign tracker). Internal strategy documents, board decks, and HR databases remain invisible. You control exactly which Notion pages the agent can access by managing the integration’s page shares.

Data handling: Campaign performance metrics are read from HubSpot and written to Notion properties. ACP does not cache analytics data between operations. Contact PII (names, emails) is only accessed when explicitly needed and is not stored in ACP’s infrastructure.

Audit trail: Every HubSpot API call and Notion update is logged with the user identity, timestamp, and specific action. Marketing leadership can review what data the agent accessed, what it wrote, and when. This is particularly important for teams operating under GDPR, where demonstrating controlled access to contact data is a compliance requirement.

Role-based access: Different team members can have different agent configurations. An intern might use the agent in read-only mode to pull reports, while the marketing director’s agent can create HubSpot workflow drafts.

Example use cases

• Content calendar sync: When a Notion content calendar entry moves to “Scheduled,” the agent creates a corresponding HubSpot email draft with the subject line, preview text, and send date from the Notion brief, ready for final review.

• Weekly performance digest: Every Monday morning, the agent populates the Notion campaign dashboard with the previous week’s HubSpot metrics, including trend arrows and notes on significant changes.

• Campaign post-mortem generation: After a campaign completes, the agent pulls full-funnel metrics from HubSpot (sends, opens, clicks, conversions, revenue attributed) and generates a structured post-mortem page in Notion with analysis and recommendations.

• Lead-to-content mapping: The agent cross-references HubSpot contact engagement data with the Notion content database to identify which content assets drive the most MQLs, helping the team prioritize future production.

• Asset checklist enforcement: Before a campaign launches, the agent verifies that every asset listed in the Notion brief (emails, landing pages, workflows, lists) exists in HubSpot and flags any missing pieces.

Getting started

Getting your HubSpot-Notion agent running is straightforward:

1. Sign up at cloud.agenticcontrolplane.com and create a workspace for your marketing team.
2. Connect your tools by authenticating HubSpot and Notion through the Data Sources page. Share your content calendar and campaign tracker databases with the Notion integration.
3. Describe your agent in plain English: “Sync my Notion content calendar with HubSpot campaigns and update performance metrics every Monday.” The agent will confirm which databases and HubSpot objects it will access before starting.