AutomationFlows › Travis CI

n8n workflows for Travis CI.

All n8n workflows that use the Travis CI integration. Each is integration-tagged, privacy-stripped, and importable into your n8n instance in one click.
DevOps
Trigger a Build in Travis Ci When Code Changes Are Push to a Github Repo

Trigger A Build In Travis Ci When Code Changes Are Push To A Github Repo. Uses githubTrigger, travisCi, noOp. Event-driven trigger; 4 nodes.

Github Trigger, Travis CI
DevOps
Trigger a Build in Travis Ci When Code Changes Are Push to a Github Repo (github Trigger)

Trigger a build in Travis CI when code changes are push to a GitHub repo. Uses githubTrigger, travisCi. Event-driven trigger; 4 nodes.

Github Trigger, Travis CI
General
Trigger a Build Using the Travisci Node

Trigger A Build Using The Travisci Node. Uses manualTrigger, travisCi. Event-driven trigger; 2 nodes.

Travis CI
General
Trigger a Build Using the Travisci Node (travis Ci)

Trigger a build using the TravisCI node. Uses manualTrigger, travisCi. Event-driven trigger; 2 nodes.

Travis CI

4 of 4 workflows in this view · Browse all →

FAQ

How many n8n Travis CI workflows are in the catalog?

4 n8n workflows in AutomationFlows currently use the Travis CI integration — triggers, actions, or both.

How do I connect Travis CI in n8n?

After importing the workflow JSON, n8n will prompt for Travis CI credentials on the relevant nodes. AutomationFlows strips credential IDs before publishing — you'll add your own.

Can I combine these with other integrations?

Yes — most Travis CI workflows pair with adjacent tools (Slack alerts, Google Sheets logging, OpenAI summarisation). Browse the integration tags on each workflow page to discover pairings.