Providers
A provider instance is a configured connection. There are two kinds.
Subject providers
Section titled “Subject providers”These supply the subjects a view queries and the catalog a provider_action step calls.
| Settings label | Subject |
|---|---|
| Jira | Ticket |
| GitHub Issues | Ticket |
| Azure DevOps Work Items | Ticket |
| Manual (Ticket) | Ticket |
| Bitbucket | Pull request |
| GitHub Pull Requests | Pull request |
| Azure DevOps Pull Requests | Pull request |
| Confluence | Documentation |
| Manual (Documentation) | Documentation |
GitHub and Azure DevOps are separate instances for issues and for pull requests. Each instance has its own id, display name, config, and secretKey. The secret value is stored in the OS credential store, not on the workflow. See Data handling.
Catalog action ids are declared by each provider. One shared operation is update_ticket_description, which replaces a ticket description with markdown on providers that implement it.
Test connection on Manage → Providers checks the instance with the key you entered.
Agent providers
Section titled “Agent providers”Agent steps call an agent instance. The settings screen offers:
- Claude
- Cursor
- DeepSeek (labeled Experimental)
defaultAgentInstanceId is used when an agent step does not name an instance. maxConcurrent caps how many agent steps for that instance run at once. When it is omitted, the cap is 2.