The job of this console
Add or rotate an instance, test it, then map. Disable before you yank a secret jobs still use.
Integrations · Connections
Connections
Installed connector instances and credentials — environment config, not the field map and not platform API keys.
Scroll to Flowcharts. Scenario: Add or rotate a connector connection.
Instances
Which environment this connector talks to
Connections hold instances and credentials. They are not the field map and not the platform API key vault.
Integrations → Connections
Route
/integrations/connections
Org flag connectionsEnabled
Integration admin · Admin
Seat at the table
Integration admins with connectionsEnabled. End users never see vendor secrets.
The working rhythm
Create, test, map, schedule jobs, rotate later.
Moments that bring you here
New sandbox. Prod cutover. Credential expiry. After a vendor incident.
ⓘ
Secrets stay here
Do not paste tokens into AI prompts or Work Graph. Admin API keys remain a different console.
Flowcharts
1 — Instance then test
Save credentials, test, map fields next.
flowchart TD
A[Open Connections] --> B[Add / open instance]
B --> C[Credentials]
C --> D[Test]
D --> E[Mapping]
- 1OpenIntegrations → Connections.
- 2InstanceOne environment.
- 3TestBefore jobs.
- 4MapData mapping.
Overview
Connections are installed instances. Marketplace is the catalog of types. API access is integration tokens. Admin API keys are platform developer keys. Mapping is the field contract.
How to use
1. Rotate secrets here
Not in Application Config blobs.
2. Disable beats delete
While jobs still reference the instance.
3. Least privilege
Vendor tokens scoped to needed objects only.