One rich card for every integration: HubSpot first, your own systems next

Integration messages in Polybase now share one versioned card format, one renderer and one durable delivery service. HubSpot events arrive as rich cards with a title, subtitle, fields and actions, linked to the CRM record they came from. Cards follow native chat styling and count as read once they have been viewed, so an integration channel no longer stays permanently unread.

The same format is open to your own systems. Create a channel API key in the channel's integration settings and POST a JSON payload with a provider name, an accent colour and one or more cards. Actions can be links or a request to summarise with the Polybase assistant. Deliveries are stored before they are acknowledged and deduplicated by event id, so a retried webhook never produces two messages.

Two platform changes round this out. MCP access to a channel is now an explicit sharing grant, separate from access inside Polybase, and personal grants stay out of tenant exports. And for managed deployments that run many workspaces on separate hosts, an optional OAuth callback broker lets Google and Microsoft connections share one registered callback without moving tokens or tenant data; self-hosted installations keep their own callback unchanged.