Until now, every integration (Google Sheets, HubSpot, Email…) only had ONE connection: the main one, shared by the whole tenant. Now an integration can also have several named connections — for example, two different spreadsheets for two departments, or two different mailboxes — each with its own credentials, its own list of allowed actions (none by default: you enable only the ones that connection needs), and its own scope:
What a named connection isUntil now, every integration (Google Sheets, HubSpot, Email…) only had ONE connection: the main one, shared by the whole tenant.
The screen: Integrations → ConnectionsRequirements: Admin or Editor role; sharing an already-created connection also requires the integration-management permission.
Resources with write permissionRequirements: Admin or Editor role.
The 'Email (read)' pieceRequirements: Admin or Editor role.
Full procedure: the 'Invoices by email' templateRequirements: Admin or Editor role; an 'Email (read)' connection to the billing mailbox (section 4), an invoice-extraction connection (an identifier support gives y…
FAQCan I have two named connections of the same integration at once?