Trigger Build
travis.trigger_build
ActionBusiness appsconnection required
Calls the Travis CI API with the connection's credentials.
Ask Travis CI to build a branch, optionally overriding the config.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Travis CI
- Secret shape
- the API token, or {"api_token": "…"}
- Config it needs
- base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
6 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
repository The repository as its 'owner/name' slug, or its numeric Travis repository id. | string | Yes | — | — | rails/rails |
branch The branch to build; Travis has no default and refuses a request without one. | string | Yes | — | — | main |
message A status message to attach to the request instead of the commit message. | string | No | — | — | Nightly build triggered by Mantle |
sha Build this exact commit rather than the branch's current head. | string | No | — | — | d6d0e5f7a2e6a8b6a5f5d0b1c2e3f4a5b6c7d8e9 |
merge_mode How 'config' is combined with the repository's .travis.yml; Travis defaults to deep_merge_append. | string | No | — | one of "deep_merge_append", "deep_merge_prepend", "deep_merge", "merge", "replace" | deep_merge_append |
config Build configuration merged over the repository's .travis.yml. | object | No | — | — | {"script":"make test"} |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"branch": "main",
"config": {
"script": "make test"
},
"merge_mode": "deep_merge_append",
"message": "Nightly build triggered by Mantle",
"repository": "rails/rails",
"sha": "d6d0e5f7a2e6a8b6a5f5d0b1c2e3f4a5b6c7d8e9"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
status Travis's request status; 'pending' means it was queued. | string | — |
request_id The request id, which Travis assigns immediately. | number | — |
remaining_requests How many API-triggered builds the account may still make in this window. | number | — |
branch The branch the build was requested for. | string | — |
repository The repository the request was made against. | object | — |
request The full request resource Travis returned. | object | — |
{
"branch": "",
"remaining_requests": 0,
"repository": {},
"request": {},
"request_id": 0,
"status": ""
}Notes
- Travis answers with a queued request, not a build: no build id exists yet. Poll travis.list_builds for the branch to pick the build up.
Related Travis CI nodes
See Trigger Build run in a workflow.
In a technical demo we add the Travis CI connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.