Skip to main content
Workflows act as the person who runs them. Most integrations read that person’s credentials from their Secrets Locker (Dashboard → Secrets Locker). Values are encrypted at rest and never returned by the API, and a run only ever sees the secrets of the tools it calls. Two integrations connect through sign-in instead: Google, with your Google login, and Slack, which an org admin can connect for everyone. Organization → Integrations in the web app has step-by-step setup for Slack, Discord, GitHub, Jira and Trello, including the Trello token link and the exact secret names.
1

Add the secrets

Open the Secrets Locker and add each name exactly as written above (for example JIRA_API_TOKEN). The Locker shows only a short hint of each value afterwards.
2

Describe a workflow that uses them

“Read issue 23 in acme/api and summarize it in my Jira ticket OPS-7.” When you generate a workflow, the response lists required_secrets, so you can see what it will use before it runs.
3

Run it

If a credential is missing or wrong, the step fails once with a message naming the secret and where to get it, for example “Jira rejected the login. Check JIRA_EMAIL is the Atlassian account the API token belongs to…”.

​
GitHub tokens

A fine-grained token limited to the repositories you want is best. Give it read access to Metadata, Contents, Issues, Pull requests, Commit statuses and Checks. Add Pull requests: write only if workflows should post reviews or comments. Classic tokens need the repo scope. If your organization uses SAML single sign-on, authorize the token for it on GitHub (Settings → Personal access tokens → Configure SSO).

​
Server-wide fallbacks

Self-hosting? The same names work as environment variables on the API (see env.example). A person’s Locker entry always wins over the server’s value, and an org’s Slack connection wins over both for Slack.

Tool integrations

Every tool, its parameters and outputs

Developer workflows

GitHub, Jira and Trello together