CRM Views And Cards

Use this capability family for saved index views, record views, and record view cards that shape how teams inspect CRM data.

At A Glance

Supported actions	Bridge or hybrid actions	Access used
8	8	Varies by plan details

Confirm the target portal is correct.
Check the operation names, target assets, and required access.
Resolve missing-permission warnings before execution.
Review operation results after execution.
Confirm object type, columns, filters, card location, and view layout.
Open important CRM views or cards in HubSpot after execution to confirm they render as expected.

Action ID	What it does	Execution	Required access	Main details
`create_index_view`	Create a HubSpot index view.	Requires the Daeda Bridge extension	No additional connected-portal scope	configuration details
`create_record_view`	Create a HubSpot record view.	Requires the Daeda Bridge extension	No additional connected-portal scope	configuration details
`create_record_view_card`	Create a HubSpot record view card.	Requires the Daeda Bridge extension	No additional connected-portal scope	configuration details
`delete_index_view`	Delete a HubSpot index view.	Requires the Daeda Bridge extension	No additional connected-portal scope	view ID, object type ID
`delete_record_view`	Delete a HubSpot record view.	Requires the Daeda Bridge extension	No additional connected-portal scope	view ID, configuration details
`delete_record_view_card`	Delete a HubSpot record view card.	Requires the Daeda Bridge extension	No additional connected-portal scope	card ID
`update_index_view`	Update a HubSpot index view.	Requires the Daeda Bridge extension	No additional connected-portal scope	view ID, object type ID, configuration details
`update_record_view`	Update a HubSpot record view.	Requires the Daeda Bridge extension	No additional connected-portal scope	view ID, configuration details

Create a HubSpot index view. The draft records configuration details for review.

Create a HubSpot record view. The draft records configuration details for review.

Create a HubSpot record view card. The draft records configuration details for review.

Action ID: create_record_view_card
Change type: Create
Execution: Requires the Daeda Bridge extension
Required access: No additional connected-portal scope
Main details reviewed in the plan: configuration details
Planning notes:
- Use COMPANY_DESCRIPTION for company activity digests: recent activity, calls/emails/meetings/notes/tasks, last 30/60/90 days, digest/analyst summary. Set sources, timeframe, summaryLength, showSuggestedActions, and showConversationStarters explicitly.
- Use COMPANY_SUMMARY for company overview sections: quick context, top stakeholders, customer journey, products, tickets, engagement summary. Set every section boolean explicitly; when the user says only, set unrelated sections false.
- For COMPANY_SUMMARY omit revenueProperty and keep customerJourneyProperties empty unless fresh manual evidence proves HubSpot accepts concrete properties in this portal.
- For open associated-ticket cards, filter on concrete ticket hs_pipeline_stage values whose pipeline stage metadata has ticketState OPEN. Do not use ticket hs_is_closed, and do not rely on filterProperties because those are only quick-filter controls.

Delete a HubSpot index view. The draft records view ID, object type ID for review.

Delete a HubSpot record view. The draft records view ID, configuration details for review.

Delete a HubSpot record view card. The draft records card ID for review.

Update a HubSpot index view. The draft records view ID, object type ID, configuration details for review.

Action ID: update_index_view
Change type: Update
Execution: Requires the Daeda Bridge extension
Required access: No additional connected-portal scope
Main details reviewed in the plan: view ID, object type ID, configuration details

Update a HubSpot record view. The draft records view ID, configuration details for review.