Supported HubSpot Actions
This reference lists the HubSpot capability families Daeda AI can represent in write plans. Open a family guide for action IDs, review notes, common request examples, bridge requirements, and access details.
Summary
Section titled “Summary”| Area | Actions | Bridge-only | Hybrid | Access used |
|---|---|---|---|---|
| Activities | 10 | 0 | 0 | crm.objects.contacts.write |
| CRM Views And Cards | 8 | 8 | 0 | Varies by plan details |
| CTAs | 3 | 3 | 0 | Varies by plan details |
| Custom Objects And Associations | 9 | 2 | 0 | crm.objects.companies.write, crm.objects.contacts.write, crm.objects.custom.write, crm.objects.deals.write, crm.schemas.custom.read, tickets |
| Forms | 3 | 0 | 0 | forms |
| Lead Scoring | 3 | 3 | 0 | Varies by plan details |
| Lists And Segmentation | 8 | 0 | 0 | cms.membership.access_groups.write, crm.lists.write |
| Pipelines | 3 | 0 | 0 | crm.objects.companies.write, crm.objects.contacts.write, crm.objects.custom.write, crm.objects.deals.write, crm.schemas.deals.write, tickets |
| Properties And Schema | 6 | 0 | 2 | crm.objects.companies.write, crm.objects.contacts.write, crm.objects.custom.write, crm.objects.deals.write, crm.schemas.companies.write, crm.schemas.contacts.write, crm.schemas.deals.write, tickets |
| Records | 5 | 0 | 0 | crm.objects.companies.write, crm.objects.contacts.write, crm.objects.custom.write, crm.objects.deals.write, tickets |
| Reports And Dashboards | 6 | 6 | 0 | Varies by plan details |
| Sales Content | 6 | 6 | 0 | Varies by plan details |
| Sequences | 4 | 3 | 0 | automation.sequences.enrollments.write, automation.sequences.read |
| Workflows | 8 | 4 | 0 | automation, crm.objects.custom.read |
Actions marked as bridge-backed need the Daeda Bridge extension connected to the right HubSpot portal. Hybrid actions can use the bridge for some plan details. Other actions can run without the browser extension.
How To Use These Guides
Section titled “How To Use These Guides”- Start with the family that matches the HubSpot area the user wants to change.
- Confirm whether the plan needs the bridge before execution.
- Review the family checklist before approving destructive, schema, automation, content, or reporting work.
- Use the action ID when comparing a visible plan operation with the supported-action reference.