--- title: "Travis CI Integration" description: "Manage Travis CI repositories, trigger and control builds and jobs, inspect logs, and configure environment variables from your flows over the Travis CI REST API v3." url: https://flowrunner.ai/integrations/travis-ci date_modified: 2026-08-01T02:40:32-07:00 --- # Travis CI [Developer Tools](https://flowrunner.ai/integrations/category/developer-infrastructure) Manage Travis CI repositories, trigger and control builds and jobs, inspect logs, and configure environment variables from your flows over the Travis CI REST API v3. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 22 actions · API key · available [Travis CI website](https://www.travis-ci.com/) · [Platform Documentation](https://developer.travis-ci.com/) · Capability data verified 2026-08-12 1. A pull request opens and a flow picks it up 2. Agent resolves the repository slug and the branch to build 3. Agent calls Trigger Build on the pull request branch 4. Agent polls Get Build until it reaches a terminal state 5. Agent posts the build state back onto the pull request as a comment 6. An engineer confirms before the agent deactivates a repository during cleanup ## What This Integration Enables FlowRunner agents use Travis CI to run CI from inside a larger flow. An agent can trigger builds on specific branches as part of a deploy or release automation, cancel, restart, or monitor builds and jobs in response to external events, and fetch raw job logs for failure analysis, alerting, or archival. It can manage repository environment variables across projects and activate or deactivate repositories to control which projects Travis CI builds. Repositories are addressed by their owner/name slug. What it does not do on its own is deactivate a repository, because that stops all builds for the project. That confirmation stays with a person. ### Without FlowRunner **Manual CI triggers**: An engineer starts each build from the Travis dashboard **Logs hunted by hand**: Finding a failing job's log means clicking through the UI **Repos toggled loosely**: A repository is deactivated with no record of who decided to stop building it ### With FlowRunner **Triggered builds**: The agent starts the build on the pull request branch automatically **Logs fetched for you**: The agent pulls the failing job log and attaches it to the alert **Confirmed deactivation**: Turning off a repository's builds waits for an engineer to confirm ## Use Case Scenarios ### CI on pull requests A pull request opens. The agent calls Trigger Build on the PR branch to run CI, polls Get Build until it finishes, and posts the resulting state back onto the pull request as a comment. Contributors see the build result on the PR without an engineer starting the build by hand. ### Failure into a tracked bug The agent calls Get Job Log after a failed build and scans it for a recurring failure signature. When it finds one, it opens a tracked bug in the issue tracker with the log excerpt and the repository slug. A flaky or broken build becomes an assigned issue instead of a red mark that scrolls away. ### Repository deactivation with a confirmation gate A cleanup flow finds repositories that have not built in months. The agent lists them with their last build dates and posts them to the platform channel. It does not deactivate them. Only after an engineer confirms does the agent call Deactivate Repository, and it records which repositories it turned off and who approved. ## Human-in-Loop Highlight The human-in-loop moment in Travis CI is the deactivation gate. Triggering builds, restarting jobs, and fetching logs are all safe or reversible, so the agent runs them by rule. Deactivating a repository is different, because it stops Travis CI from building that project until someone turns it back on, and a silently un-built repository can hide a broken pipeline for weeks. When a cleanup flow flags stale repositories, the agent lists them with their last build dates and asks in the platform channel: "These four repositories have not built in 120 days. Confirm which to deactivate?" An engineer confirms. Only then does the agent call Deactivate Repository. The agent runs CI on its own. A person owns the switch that stops a project from building. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 22 actions ### Repositories 6 - **Activate Repository** Enable Travis CI builds for a repository. Requires admin access. - **Deactivate Repository** Disable Travis CI builds for a repository. Requires admin access, and run it behind a human confirmation. - **Get Repository** Retrieve a repository by slug. - **List Repositories** List the repositories the token can access. - **Star Repository** Star a repository. - **Unstar Repository** Unstar a repository. ### Builds 5 - **Cancel Build** Cancel a running build. - **Get Build** Retrieve a build's state and details. - **List Builds** List a repository's builds. - **Restart Build** Restart a completed build. - **Trigger Build** Start a build on a branch. Used to run CI on a pull request branch. ### Jobs 5 - **Cancel Job** Cancel a running job. - **Get Job** Retrieve a job's state and details. - **Get Job Log** Retrieve a job's raw log. Used for failure analysis or archival. - **List Build Jobs** List the jobs in a build. - **Restart Job** Restart a single job. ### Environment Variables 3 - **Create Environment Variable** Set a repository environment variable. Requires admin access. - **Delete Environment Variable** Delete a repository environment variable. - **List Environment Variables** List a repository's environment variables. Private values are not returned. ### Branches & Caches 2 - **List Branches** List a repository's branches. - **List Caches** List a repository's build caches. ### User 1 - **Get Current User** Retrieve the authenticated user. Used as a connection check. ## Frequently Asked Questions ### What can FlowRunner do with Travis CI? FlowRunner agents can run List Repositories, Get Repository, and Activate Repository in Travis CI, plus 19 more actions. ### Does connecting Travis CI to FlowRunner require OAuth? No. Travis CI connects to FlowRunner with an API key, no OAuth flow required. ### Can Travis CI trigger a FlowRunner workflow automatically? Travis CI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Travis CI?** This integration exposes Travis CI to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/travis-ci. Site index: https://flowrunner.ai/llms.txt