Integrations Overview
Understand the provider connections Bilbis needs before it can run pipelines.
What this means
Integrations are the external services Bilbis uses to do work for your organization. Before Bilbis can write code or open an MR/PR, it needs credentials for the providers involved in that workflow.
Bilbis uses a bring your own key model, often shortened to BYOK. For the security and cost model behind that setup, see BYOK.
When to use it
Use the Integrations page when you need to:
- Add the first LLM provider so agents can reason and write code.
- Add the first Git provider so Bilbis can clone, branch, push, and open MRs/PRs.
- Replace an expired or revoked key.
- Validate whether a saved credential still works.
- Configure Jira for ticket-triggered pipelines.
Before you start
You need an owner or admin role to manage organization-wide integrations.
For the first successful pipeline, your organization needs:
| Requirement | Why Bilbis needs it |
|---|---|
| LLM provider | Lets the agents plan and write code. |
| Git provider | Lets Bilbis read the repo, push a branch, and open an MR/PR. |
| Product | Groups repositories under shared automation settings. |
| Repository | Gives the pipeline a target codebase. |
Provider types
| Provider | What it is used for |
|---|---|
| Anthropic | LLM provider for agent work. |
| OpenAI | LLM provider for agent work. |
| GitLab | Git provider for repositories, branches, and merge requests. |
| GitHub | Git provider for repositories, branches, and pull requests. |
| GitHub App | Reserved for GitHub-style access. In the current app it is treated like a token-shaped credential. |
| SendGrid | Email delivery for self-hosted or customer-owned email workflows. |
| Cloudflare | Cloudflare-owned workflows where your organization supplies a key. |
| Jira | Ticket workflow integration. Jira is configured through the dedicated Jira card, not the generic credential dialog. |
Steps
- In Bilbis, open Settings.
- Open Integrations.
- Select Add credential for regular provider keys, or use the dedicated Jira setup area for Jira.
- Choose the provider.
- Add a clear label, such as
Production GitHuborAnthropic team key. - Paste the API key or token.
- Save the credential.
Bilbis validates a newly saved credential when it can. The credential list then shows whether the provider is reachable or whether validation failed.
What happens next
After a credential is saved, it becomes available to pipelines in that organization. Users do not see the secret value again. They can see the provider, label, last four characters when available, validation status, and last validation time.
Problems and fixes
| Problem | What to check |
|---|---|
| New pipeline form says setup is incomplete | Confirm you have at least one LLM credential, one Git credential, one product, and one repository. |
| Credential validation fails | Check that the token is active, has the right provider permissions, and was copied without extra spaces. |
| Jira does not appear in the generic credential picker | Use the dedicated Jira configuration card. Jira needs both a credential and workflow settings. |
| Pipelines fail after deleting a credential | Add a replacement credential for the same provider before running more pipelines. |