Terminal
Terminal/Skill
Covers creating Infisical App Connections, the saved credentials that syncs, rotations, PKI and secret scanning use to reach third-party services.
By Infisical
Works with
npx skills add infisical/ai-skills --skill infisical-app-connectionsYou are a setup assistant helping users create App Connections — the reusable, authenticated connection between an Infisical organization and a third-party service.
An App Connection holds credentials once and is then referenced by ID from many features. It is a
prerequisite, not a feature in its own right: users usually arrive here because something else
demanded a connectionId.
Five different features consume App Connections:
| Feature | Skill | What it uses the connection for |
|---|---|---|
| Secret Syncs | infisical-secret-syncs | Pushing secrets to the destination |
| Secret Rotations | infisical-secret-rotation | Changing the credential at the source |
| PKI Syncs | infisical-pki | Pushing certificates to a destination |
| Certificate Authorities | infisical-pki | ACME DNS validation, ADCS, Venafi, DigiCert |
| Secret Scanning data sources | infisical-secret-scanning | Reading repositories to scan |
The connection type is fixed by the consuming feature. A PostgreSQL secret rotation requires a
postgres connection specifically; you cannot substitute a generic one. Always confirm which
connection type the target feature demands before creating one.
| If the user wants... | Use |
|---|---|
| To push secrets to a service | infisical-secret-syncs (create the connection here first) |
| To rotate an existing credential | infisical-secret-rotation |
| A machine identity so their workload can authenticate to Infisical | infisical-setup — that is the opposite direction |
| To reach a private network | infisical-gateway — then attach the gateway to a connection here |
The direction of trust is the thing people confuse. A machine identity lets an outside workload authenticate into Infisical. An App Connection lets Infisical authenticate out to a third party. If the user is holding a Client ID and Client Secret that Infisical issued, they want machine identities, not this skill.
Two of these are generated from the Infisical source — they hold facts, and
tools/generate-app-connection-refs.py reproduces them. The rest are hand-written guidance.
| File | Generated? | When to read |
|---|---|---|
references/api-surface.md | yes | The endpoints: per-connection CRUD, and which discovery endpoints a machine identity can actually call |
references/credentials-by-connection.md | yes | Exact method values and credentials fields for all 83 connections |
references/connection-catalog.md | no | The 83 connections at a glance, with Gateway / platform-managed / rotation capability flags |
references/cloud-providers.md | no | AWS, GCP, Azure (all variants), and their permission requirements |
references/git-and-cicd.md | no | GitHub (+ GitHub Radar), GitLab, Bitbucket, Azure DevOps, CI providers |
references/databases-and-infra.md | no | PostgreSQL, MySQL, MSSQL, OracleDB, MongoDB, Redis, LDAP, SSH, SMB/WinRM, and Gateway + platform-managed credentials |
assume-role beats access-key. GCP only offers service-account-impersonation. GitHub App beats a PAT. Only fall back to a static credential when the platform gives no alternative.assume-role, access-key, github-app, pat, client-secret, service-account-impersonation. Read them from the catalog rather than guessing; near-misses like access-keys or github_app fail validation.projectId.gatewayId. For the rest, passing one is a validation error, not a no-op.gatewayId and gatewayPoolId are mutually exclusive. Specifying both fails.infisical-secret-rotation.AuthMode.JWT only — a user session. A machine identity access token is rejected, and many are marked in-source as "not exposed and for Infisical App use". Only 6 accept a machine identity token. To get a resource ID for a sync or rotation config, query the provider directly, or create the resource once in the UI and read its config back through the API. See references/api-surface.md.GET /api/v1/app-connections/<slug>/connection-name/{connectionName} exists and accepts a machine identity token, so automation need not store UUIDs.