Integrations
A connection is a credential penv holds for a store it can mirror your values into or read them out of.
A connection is a credential penv holds for somewhere else. Once penv holds it, you can map one of your environments onto one place over there and move values in either direction. The places range from a hosting platform to a pipeline's own settings.
Every page in this section is generated from the provider's own descriptor, so what you read is what the console does.
Connections and Connect are opposites
| Section | Who holds the credential | What moves |
|---|---|---|
| Integrations | penv holds one for the other system | Values, in or out |
| Connect a platform | Nobody holds one | A token that proves who a machine is |
Nothing appears under both.
Reading a connection page
Each one states the vendor, the key the API stores, whether it can read values back, and when a written value reaches the running app. It then lists the fields the console asks for, with the same helper text you see on screen, and the permissions penv probes for when it verifies. The connection and mapping tables also mark which fields the console keeps behind its Advanced disclosure.
A page marked planned describes a card the console shows and cannot connect yet.
Start here
- How syncs work: what each direction does, the conflict policies, preview then apply.
- Connect methods: the five ways a credential or a grant reaches penv.
- Integrations in the console: where you do all of it.
The list beside this page groups every provider under its vendor, in catalog order. The console's grid shows fewer cards than this list: where a newer provider replaces an older one, the grid renders the newer card alone and offers the older one beneath it as an escape hatch.