Skip to content

FAQ

Use this FAQ for short answers to common customer and admin questions.

Can Daeda AI Change HubSpot Without Approval?

Section titled “Can Daeda AI Change HubSpot Without Approval?”

No. A write plan stays in draft review until a user opens it in HubSpot, reviews it, chooses Execute, and confirms execution.

Plans are portal-specific. Review the target portal before execution, especially when the account manages several connected portals.

You need the extension for bridge-backed work. The current supported-action catalog includes 37 bridge or hybrid action types.

If a plan includes bridge-backed operations, confirm the extension is connected, the active HubSpot portal matches the plan, and the connected-portal bridge toggle is enabled.

A plan can ask for re-authorization when the requested change needs HubSpot access that has not been granted yet. Approve the access only when it matches the intended work.

Daeda AI shows operation results after execution, but users should not assume every change has a one-click undo. For important changes, inspect HubSpot after execution and ask for a follow-up plan when a correction is needed.

Reject it and ask for a revised plan. Include what was wrong: portal, asset, permissions, operation type, filter logic, or destructive action.

Open the failed plan, review operation results, and check HubSpot for changes that already completed. Retry only when repeating completed operations is safe.

The current catalog includes 82 supported action types. Use the supported-action reference to confirm whether the requested HubSpot work is covered.

Wait for READY when the plan depends on rich portal context. Simple direct changes can still be reviewed, but context-heavy requests should wait until data readiness is clear.