Start free
ActionJenkinsUpdated June 2026

What Jenkins jobs are configured?

Short answer: You can list jenkins jobs in Jenkins by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jenkins List Jenkins Jobs action to a workflow, map its 0 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Jenkins Jobs in Jenkins — start free All 4 Jenkins actions
List Jenkins Jobs in Jenkins — start free
Sample request
{}
Returns
{
  "jobs": [
    {
      "url": "https://jenkins.example.com/job/my-project/",
      "name": "my-project",
      "color": "blue",
      "lastBuild": {
        "number": 42,
        "result": "SUCCESS"
      }
    }
  ]
}

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

Triggered by

Apps that pair well as the trigger for List Jenkins Jobs.

Any of these apps can fire this action as part of a workflow.

Gmail → Jenkins
1 Gmail triggers
Slack → Jenkins
13 Slack triggers
Google Sheets → Jenkins
2 Google Sheets triggers
HubSpot → Jenkins
18 HubSpot triggers
FAQ

Questions about List Jenkins Jobs.

What does the List Jenkins Jobs action do in Jenkins?
Returns every job visible on the Jenkins instance organised by folder. Useful for resolving job paths at workflow setup or for inventorying the CI configuration.
What inputs does List Jenkins Jobs require?
List Jenkins Jobs has no required inputs. Sensible defaults are applied if you leave fields blank.
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 Jenkins 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 List Jenkins Jobs support batch operations?
Yes. Run List Jenkins Jobs inside a Loop node to process arrays. TinyCommand handles Jenkins's rate limits automatically so you don't have to throttle manually.
More actions

Other Jenkins actions.

Action
Get Jenkins Build Log
Returns the full stdout/stderr of the build as plain text. For "post error log to Slack on deploy failure" diagnostic workflows. For very long logs, use the progressiveText endpoint via HTTP action for streaming.
Action
Get Jenkins Build Status
Returns the current state of a specific build number — queued, building, success, failure, aborted. The standard polling lookup after Trigger Build.
Action
Trigger Jenkins Build
Starts a job optionally with parameters. Returns a queue item ID; the actual build number assigns when the queue dequeues. For "Linear issue moved to staging → trigger deploy job" or "external event → CI run" workflows.
List Jenkins Jobs in Jenkins — start free