TravisCI n8n integrationAutomate TravisCI with n8n.
Five operations, one resource, and every one of them is a gesture you can fire from a workflow. The TravisCI n8n integration sits entirely on the Build resource: cancel, get, get many, restart, trigger. No TravisCI trigger ships with n8n, so the workflow starts somewhere else and calls Travis when it has a reason to.
Verified Trustpilot reviews · AI, automation & growth agency
What does the TravisCI n8n integration actually give you?
TravisCI runs the builds. n8n is where the rest of the tooling already lives. The node bridges the two with five operations on a single resource, Build: cancel, get, get many, restart and trigger. It ships with n8n, so there is nothing to install, and one API token credential covers every workflow you write afterwards.
Read the node as three moves rather than a field list. Everything a team does with Travis from a workflow comes down to starting a build, reading builds back, or stopping and replaying one. Pick the move first, the operation follows.
Starting a build. A push picked up through the GitHub node lands in n8n, and Trigger a build fires Travis on the repository slug and the branch you name. The same move works from a Schedule Trigger for a nightly run, or from an n8n Webhook that a third-party service calls, since the workflow does not have to start in Travis at all.
Reading builds back. There is no TravisCI trigger node in n8n, so a workflow that wants to know what Travis has been doing polls for it: Schedule Trigger on whatever interval fits, then Get many builds with Return All switched on so the node walks every page of the API instead of stopping at Limit. The rows then go wherever the team actually looks, a tab in Google Sheets, a table in Postgres, or a message in Slack.
Stopping and replaying. Cancel a build and Restart a build both hang on one value, the Build ID, which is why they pair so well with a small approval flow: someone clicks, the workflow already holds the ID, the node does the rest. Worth knowing before you build: none of the five operations marks a field as required, so n8n will run the node with whatever you hand it. Filling the fields is on you, not on the validator.
And when the node runs out of room, the HTTP Request node calls any endpoint of the Travis CI API with the very same credential through predefined authentication. If you are still weighing n8n itself, the n8n review covers that separately.
How do you connect TravisCI to n8n?
- 01
Generate the API token in Travis CI
You need a Travis CI account first. Once you have one, the token lives under Account Settings, in the API Token section. If you would rather stay in a terminal, the Travis CI command line client generates one too. That token is the only secret n8n asks for, so treat it like a password and copy it somewhere safe before you leave the page.
- 02
Save the credential once in n8n
Open the Credentials menu in n8n, create a Travis CI credential and paste the value into the API Token field. A credential is stored at the n8n level, not inside a workflow, which means you set it up once and pick it from a dropdown in every workflow you write afterwards. Same story whether you run n8n Cloud or your own instance.
- 03
Drop the node in and run one operation
Add the TravisCI node to a canvas, select the credential in its list, and leave the resource on Build since that is the only one the node exposes. Get many builds is the friendliest first test: it reads rather than writes, and it tells you in one execution whether the token is accepted. Then look at the output shape before you wire the next step.
What can the TravisCI node do?
The TravisCI node exposes 5 operations across 1 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.
Build
5 operationsCancel a build
build.cancelWhat you see in n8n
Notes & use cases
Sends a cancel order for a build that is still running, from inside the workflow that decided it should stop.
Key parameters
- Build ID: the value that uniquely identifies the build you want stopped. The node does not flag it as required, so pass it deliberately, usually from the step before with an expression such as
{{ $json.field }}.
Get a build
build.getWhat you see in n8n
Notes & use cases
Pulls one build back into the workflow so the steps after it have something concrete to read.
Key parameters
- Build ID: the value that uniquely identifies the build you are asking about.
- Include: a list of attributes to eager load, written the way the placeholder shows,
build.commit. Ask for the attributes you actually intend to use downstream.
Get many builds
build.getAllWhat you see in n8n
Notes & use cases
Returns a list instead of a single item, which is what you want for reporting, exports and any scheduled sweep.
Key parameters
- Return All: on, n8n walks every page of the API and brings back all the builds; off, Limit caps how many items come back.
- Order:
ascordescfor the direction of the response. - Sort By:
created_at,finished_at,id,numberorstarted_at. - Include: attributes to eager load, such as
build.commit.
Restart a build
build.restartWhat you see in n8n
Notes & use cases
Asks Travis to restart a build you already hold the identifier for, without anyone going back to the interface.
Key parameters
- Build ID: the value that uniquely identifies the build to restart. It travels well from a previous node as
{{ $json.field }}, which is how a one-click restart flow usually gets wired.
Trigger a build
build.triggerWhat you see in n8n
Notes & use cases
Starts a build on the repository and branch you name, which makes this the operation most workflows end on.
Key parameters
- Slug: same as
{ownerName}/{repositoryName}, for instancen8n-io/n8n. - Branch: the branch requested to be built, such as
master. - Message: the Travis CI status message attached to the request, useful for saying who or what asked for this build.
Need help automating TravisCI with n8n?
A person reads every message.