Limitations And Constraints

Use this guide to understand what Daeda AI can represent in write plans, when the bridge is required, and where users still need to verify work in HubSpot.

Supported Actions

Daeda AI currently represents 82 HubSpot action types in write plans. The supported-action reference lists each action ID, change type, execution mode, required access, and main details reviewed in the plan.

If the requested HubSpot change is not listed in the supported-action reference, ask for a narrower or related plan that uses a supported action.

Bridge Requirements

The current catalog includes 37 bridge or hybrid action types. These actions need the Daeda Bridge extension connected to the right browser profile and portal before execution.

Bridge-backed work should not run until the extension shows a connected state and the target portal is open in the same browser profile.

Data Readiness

Plans that rely on rich portal context should wait for READY mirrored data. If the connected portal is still BUILDING, PARTIAL, or FAILED, review simple direct changes carefully and avoid context-heavy requests until readiness improves.

Manual HubSpot Review

Daeda AI can prepare and execute supported changes, but users should still inspect important assets in HubSpot after execution. This is especially important for workflows, reports, dashboards, lead scores, schema changes, and destructive operations.

Scope And Permission Limits

A plan can only execute actions that the connected portal and current authorization allow. When a plan shows missing permissions, re-authorize before execution or reject the draft and ask for a narrower plan.