ActionTravis CiUpdated June 2026

How do I check a Travis CI build status?

Short answer: You can get build in Travis Ci by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Travis Ci Get Build action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Get Build in Travis Ci — start free All 1 Travis Ci actions

Get Build in Travis Ci — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
ID id	string	Required	ID

Sample request

{
  "id": "{{trigger.id}}"
}

Returns

{}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Get Build.

What does the Get Build action do in Travis Ci?

Fetches a Travis CI build by ID with its current state, duration, branch, and commit. Use it for status badges, post-deploy gates, or to surface build details in a chat notification.

What inputs does Get Build require?

Required: ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Travis Ci returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Build support batch operations?

Yes. Run Get Build inside a Loop node to process arrays. TinyCommand handles Travis Ci's rate limits automatically so you don't have to throttle manually.

How do I check a Travis CI build status?

The fields this action accepts.

Apps that pair well as the trigger for Get Build.

Questions about Get Build.