Skip to content

Start building

Integration · Developer

AI agents for Bitrise

Run and watch mobile CI on Bitrise: list apps and their workflows, start a build or pipeline on a branch with environment variables, follow its status, read its log and artifacts, and abort it.

Actions
8
Read
6
Write
2

Actions

What your agents can do in Bitrise

Run and watch mobile CI on Bitrise: list apps and their workflows, start a build or pipeline on a branch with environment variables, follow its status, read its log and artifacts, and abort it, with a personal or workspace access token.

Read 6

Look things up. Nothing changes.

  • List apps

    Lists the Bitrise apps (projects) the token can see, as data.

  • List an app's workflows

    Lists the names of the workflows in an app's bitrise.yml, as data.

  • List an app's builds

    Lists an app's builds, newest first, as data: each with slug, build_number, status.

  • Get a build

    Reads one build: status and status_text, branch, commit_hash, triggered_workflow, when it was triggered, started and finished, abort_reason, credit_cost, the machine and stack.

  • Get a build's log

    Reads a build's log: while it runs, the newest log_chunks (each chunk of text and its position).

  • List a build's artifacts

    Lists the files a build produced (IPA, APK, AAB, test reports …), as data.

Write 2

Create, change or send.

  • Start a build

    Starts a workflow (or a pipeline) for an app on a branch, tag or commit, with optional environment variables like [{"key": "DEPLOY_ENV", "value": "staging"}] and a commit message to show.

  • Abort a buildDeletes data

    Stops a running or waiting build, with a reason shown on the build.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

API key

Paste an API key from your Bitrise account.

What you enter

  • Access token

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Bitrise data

    Ask a question in plain words. The agent can list apps, list an app's workflows or list an app's builds in Bitrise, then answers with what it found.

  • 02

    Let an agent update Bitrise

    Have the agent start a build in Bitrise as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Bitrise and Slack: it can list apps in Bitrise and post a summary to a Slack channel in the same run.

FAQ

Bitrise and MyDeepAgents

Can MyDeepAgents connect to Bitrise?

Yes. The Bitrise connector has 8 actions: 6 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Bitrise?

Paste an API key from your Bitrise account. You'll need: Access token. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Bitrise without asking?

Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.

Can I use Bitrise in workflows as well as agents?

Yes. Every Bitrise action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Bitrise to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.