STEP 1
Select Jenkins in workflow
Pick Jenkins app in the workflow builder [4] - just one click to select the app.
Jenkins Integration
Manage Jenkins jobs, builds, nodes, views, plugins, and credentials on a self-hosted CI server. Connect Jenkins events to the tools your engineering teams already use. Start with Watch New Builds, then follow with Get Build Artifact or Get Build Console Output to automate the next step.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Supported triggers and actions for Jenkins integration
Triggers can detect changes in Jenkins and run actions that can create, search or modify data inside Jenkins automatically [3] — exactly how you set them.
- Watch New BuildsTriggers when new Builds.
- Watch Queue ItemsTriggers when queue Items.
- Get Build ArtifactReturns build artifact.
- Get Build Console OutputReturns build console output.
- Get Build Environment VariablesReturns build environment variables.
- Get Build InfoReturns build info.
- Get Build Pipeline StagesReturns build pipeline stages.
- Get Build Test ReportReturns build test report.
- Get Credential ConfigReturns credential config.
- Get Current UserReturns current user.
- Get Jenkins Server InfoReturns jenkins server info.
- Get Job ConfigReturns job config.
- Get Job InfoReturns job info.
- Get Label InfoReturns label info.
- Get Node ConfigReturns node config.
- Get Node InfoReturns node info.
- Get Overall Load StatisticsReturns overall load statistics.
- Get Queue ItemReturns queue item.
- Get View ConfigReturns view config.
- Get View InfoReturns view info.
How to integrate Jenkins in automation workflow?
3 simple steps to make your Jenkins connected with other apps in automation workflows on WEXTL. Up to 10 minutes integration set up.
STEP 2
Connect Jenkins
When prompted, authorize access to Jenkins in WEXTL once. Jenkins credentials are encrypted and never shared with WEXTL. Authorization will be reused in any future API calls [3].
WEXTL wants to integrate with your Jenkins account. Approve?
STEP 3
Build a workflow
Build your workflow with Jenkins yourself or with WEXTL® AI Builder. Connect Jenkins to any available integrations [5], or use HTTP node to go beyond them.
Jenkins
How Jenkins connects and integrates with WEXTL
Save and approve your credentials once — WEXTL® stores authorization information encrypted and reuses the authentication whenever Jenkins app is called in workflows. That allows your developer tools automations to run without your attention, per defined schedule [7]. Explore documentation [6] for a detailed list of fields that Jenkins supports.
The following table illustrates what fields Jenkins integration require during authorization flow inside our workflow builder [4].
Connect Jenkins
Base URL*Text
••••••••
Username*Text
••••••••
Demonstration of Jenkins connection step inside WEXTL Workflow Builder [4].
| Field | Type | Help |
|---|---|---|
Base URLRequired | text | The root URL of your server, for example https://ci.example.com. Include any path prefix your server is served under. No trailing slash. |
UsernameRequired | text | The username the API token belongs to. This is the login name, not the display name. |
API TokenRequired | password | An API token generated at your URL under /me/security. Use an API token, not your account password. |
Connect Jenkins to popular apps on WEXTL
Enter a name of the other app you want to sync with Jenkins below. Click on selected app to explore integration options with Jenkins. If the app you search for is not available in WEXTL yet, you can use HTTP node [10] instead to integrate it directly.
Example automation with Jenkins integration
Select Watch New Builds trigger from Jenkins - this will be a starting point in your automation. Whenever event happens in Jenkins, workflow will start [7] from Watch New Builds node.
Search for Update Build Description, connect it as the next step of integration sequence. You can use filters between Watch New Builds and Update Build Description, so only important data pass from Watch New Builds to the next step. WEXTL gives you full control over the process of Jenkins automation. All parts of workflow are visible on the canvas [4].
Jenkins on WEXTL has 66 modules for creating developer tools automations. Explore Jenkins documentation for more.
Jenkins
Watch New Builds
Cockpit
Performs action
OR
Cockpit
Triggers
Jenkins
Update Build Description
Demonstration of how visual Jenkins automation [6] looks in WEXTL.
Frequently asked questions
Common questions about automating Jenkins in your workflows.
Jenkins has 2 triggers, including "Watch New Builds" and "Watch Queue Items". Triggers are start points of the workflow, and automations may start from them.
Integration has 64 actions, including "Get Build Artifact", "Get Build Console Output", and "Get Build Environment Variables", and more. Refer to our Jenkins Documentation for detailed inputs and outputs.
No. Most automations are built visually on the canvas by picking triggers, actions, and mapping fields. You can add custom JavaScript with Functions when advanced logic is needed — but our customers do that in rare cases [4].
Yes. Connections are authenticated per account, credentials are encrypted at rest, and you can enforce approvals and team-level access controls on any automation.
The Jenkins integration on WEXTL runs directly on its vendor public API — every field name, authentication method, and rate limit is controlled by Jenkins official API and covered in documentation [3]. WEXTL handles the request signing and pagination for you.
Absolutely. Where Jenkins provides native webhooks, you can use instant triggers to eliminate polling delay. For custom webhooks, WEXTL offers Custom Webhook node, so you can start automation whenever Jenkins or any other service sends event to webhook URL.
WEXTL is an AI-first visual canvas. The platform allows you to describe automation in plain text — and AI will wire nodes for Jenkins inside the workflow builder [4]. You can also use built-in workflow nodes (AI Agent, Human in the Loop, Condition, Aggregate Results) in pair with Jenkins modules to craft complex integration flows with branches, filtering, and conditional logic. There are absolutely no limits of what you can build.
References
List of sources used to gather information about the Jenkins integration.
- Jenkins integration source code, module specs and credentials implementation.
- Internal Jenkins integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official Jenkins vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® Visual Workflow Builder, anonymized data from our technical support team.
- WEXTL® Apps Library
- WEXTL® Jenkins App Documentation
- WEXTL® Workflow Scheduler
- WEXTL® HTTP node documentation