Infisical

Import secrets from an Infisical Cloud folder. One way only: we never write back.

Connection

What	This provider
Vendor	Infisical
Key	`infisical-secrets`
Availability	`available`. You can connect it today.
Credential we hold	`infisical-identity`
Values read back	yes
Activation	`immediate`

Direction	What it does
`import`	We read names and values out of the store into your environment.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`

How syncs work says what each one does.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`clientId`	Client ID	secret; we mask it here and seal it	yes
`clientSecret`	Client Secret	secret; we mask it here and seal it	yes	From a machine identity with Universal Auth. We exchange these for a short-lived token and never store one.

You set these when you connect. Every mapping on the connection shares them.

Field	Label	Kind	Required	Advanced	What it is
`region`	Region	choice	yes	yes	Which Infisical Cloud region holds the project. One of United States, Europe. Starts at `us`.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`projectId`	Project ID	text	yes	no	From the project's URL in Infisical.
`environment`	Environment	text	yes	no	The environment slug to read from.
`secretPath`	Folder	text	no	yes	One folder per sync. We do not walk subfolders, so two of them can hold the same name. Starts at `/`.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`identity:login`	every direction	yes	The machine identity cannot mint a token, so nothing can be read.
`secrets:read`	`import`	yes	Import cannot read any values.