Travis CI

Manage repositories, builds, and jobs with the Travis CI API.

Detail	Value
Category	CI/CD
Base URL	https://api.travis-ci.com
Authentication	Bearer Token
Endpoints	8
Connector key	travis-ci

Using Travis CI in a workflow

1. Go to Connections and click New Connection.
2. Pick Travis CI from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /user	Get current user
GET /repos	List repositories
GET /repo/{slug}	Get repository details
GET /repo/{slug}/builds	List builds
GET /build/{id}	Get build details
POST /build/{id}/cancel	Cancel a build
POST /build/{id}/restart	Restart a build
POST /repo/{slug}/requests	Trigger a build

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /user

Get current user

Detail	Value
Operation ID	cicd.getCurrentUser
Method	GET
Path	/user

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Travis CI connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.getCurrentUser.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Travis CI API reference.

GET /repos

List repositories

Detail	Value
Operation ID	cicd.listRepositories
Method	GET
Path	/repos

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Travis CI connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.listRepositories.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Travis CI API reference.

GET /repo/{slug}

Get repository details

Detail	Value
Operation ID	cicd.getRepository
Method	GET
Path	/repo/{slug}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Travis CI connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.getRepository.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Travis CI API reference.

GET /repo/{slug}/builds

List builds

Detail	Value
Operation ID	cicd.listBuilds
Method	GET
Path	/repo/{slug}/builds

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Travis CI connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.listBuilds.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Travis CI API reference.

GET /build/{id}

Get build details

Detail	Value
Operation ID	cicd.getBuild
Method	GET
Path	/build/{id}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Travis CI connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.getBuild.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Travis CI API reference.

POST /build/{id}/cancel

Cancel a build

Detail	Value
Operation ID	cicd.cancelBuild
Method	POST
Path	/build/{id}/cancel

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Travis CI connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.cancelBuild.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Travis CI API reference.

POST /build/{id}/restart

Restart a build

Detail	Value
Operation ID	cicd.restartBuild
Method	POST
Path	/build/{id}/restart

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Travis CI connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.restartBuild.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Travis CI API reference.

POST /repo/{slug}/requests

Trigger a build

Detail	Value
Operation ID	cicd.triggerBuild
Method	POST
Path	/repo/{slug}/requests

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Travis CI connection from the Connection dropdown.
3. In the Operation dropdown, select cicd.triggerBuild.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Travis CI API reference.