Automation Suite Overview

Automation Suite Overview

The Automation Suite is the deeper part of Daeda AI.
It makes it easy to work with the AI on your computer against your HubSpot data. You can easily pull down portal data that your AI can analyse to generate ICP reports or answer portal questions. And you can create Write Plans — code-executed changes to your HubSpot portals that must be human-approved inside Daeda AI before they run.

How It Fits Together

Layer
What it does
Lives where
Daeda AI
Workspace, billing, license keys, portal connections, Write Plan review
Inside HubSpot
Automation Suite client (@daeda/mcp-pro)
Local server that syncs portal data and exposes tools to your AI
On your machine
Your AI client
Claude Code, Cursor, or any MCP-compatible client
On your machine
The flow:
Step
What happens
1
An admin installs Daeda AI in HubSpot.
2
The admin creates an MCP license key in Daeda AI > Master Settings.
3
The user adds @daeda/mcp-pro to Claude Code, Cursor, or another MCP client.
4
The MCP client connects with that license key.
5
The first real registration can start the one-time free trial if no paid plan is active yet.
6
The client syncs portal data into a local DuckDB database on the user's machine.
7
The AI queries the local database and can propose Write Plans.
8
Write Plans appear in Daeda AI inside HubSpot for human review and execution.

What You Can Do

Pull Down Portal Data

The Automation Suite mirrors your portal into a local encrypted DuckDB database. Once the initial sync is complete, the AI can answer questions and run analysis without making per-question HubSpot API calls.
Typical reads:
  • Which deals are in closedwon this quarter?
  • Which contacts belong to which companies?
  • What does our pipeline distribution look like across owners?
  • Generate an ICP report from the last 12 months of closed-won deals.

Write Plans

The Automation Suite never silently writes to your portal.
When the AI proposes a CRM change — create a deal, update a contact, merge two records — it builds a Write Plan. The plan is validated, then surfaced in Daeda AI inside HubSpot for a human to review and execute.
Stage
Where
Plan drafted
AI client via build_plan tool
Plan submitted
AI client via submit_plan tool
Plan reviewed
Daeda AI > Write Plans
Plan executed
Daeda AI > Write Plans (after approval)
This is why the Automation Suite is safe to give to AI agents: they cannot bypass human review.

Custom Objects

The Automation Suite can sync, query, and update existing custom objects in your portal. There is one constraint around creating brand-new custom object schemas — see  Custom Objects  for the supported workflow.

Multi-Portal

One workspace can connect multiple HubSpot portals. The Automation Suite can query each connected portal individually and switch between them on demand.

Bring Your Own Key

The Automation Suite respects the OpenRouter key configured in Daeda AI > Other AI Features. Your model selection and cost stay under your control.

Deep Optional Scopes

Every HubSpot object can be explicitly allowed for reading and writing. Scopes are chosen when you generate the install link for a client portal in Daeda AI > Master Settings.
Scope type
Needed for
Read scopes
Querying CRM objects and metadata
Write scopes
Write Plans that create, update, delete, or merge records
Schema write scopes
Property, property-group, and custom-schema changes
Workflow and sequence scopes
Workflow metadata, triggers, and automation operations

Deeper Look At Features

The walkthrough above covers Write Plans, custom object support, and multi-portal workflows in more detail.

Next Steps

Next
Use it for
Install @daeda/mcp-pro in Claude Code, Cursor, or another MCP client
The supported workflow for creating and using custom objects
Understand artifacts, plugins, freshness, and refresh rules
Diagnose setup, sync, and refresh issues