Action Configurations
Action configurations let you define exactly how an agent can use a specific action. You set which parameters are locked to specific values and which the agent can choose freely.Why Use Action Configurations?
Without configurations, an agent can request any action from its enabled connectors with any parameters. Configurations add guardrails:- Lock parameters — force specific values (e.g., only allow creating issues in a specific repository).
- Constrain values — use wildcard patterns to limit what the agent can pass.
- Bind credentials — link a specific credential to the configuration so the right account is used.
configuration_id in its approval request, Permission Slip validates the action parameters against the configuration’s constraints before processing the request.
Create a Configuration
Open the connector detail page
Navigate to the agent’s config page, then click Configure on the connector.
Fill in the details
- Name — a human-readable label for this configuration.
- Action — select which action this configuration applies to.
- Parameters — set values or constraints for each parameter.
- Credential — optionally bind a stored credential.
- Enabled — toggle whether the configuration is active.
Manage Configurations
Each configuration in the table shows:| Column | Description |
|---|---|
| Name | The configuration’s label |
| Action | Which action type it applies to |
| Parameters | Number of constrained parameters |
| Credential | Which stored credential is bound (if any) |
| Status | Enabled or disabled |