ActionJenkinsUpdated September 2026
How do I trigger a Jenkins build?
Short answer: You can trigger jenkins build in Jenkins by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Jenkins Trigger Jenkins Build action to a workflow, map its 2 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Job Name job_name | string | Required | URL-encoded job name (use %2F for folders) |
Build Parameters (JSON) parameters | string | Optional | JSON object of build parameters |
Sample request
{"job_name": "e.g. my-pipeline or folder%2Fmy-pipeline","parameters": "{\"BRANCH\": \"main\", \"DEPLOY_ENV\": \"staging\"}"}
Returns
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Trigger Jenkins Build.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Trigger Jenkins Build.
What does the Trigger Jenkins Build action do in Jenkins?
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.
What inputs does Trigger Jenkins Build require?
Required: Job Name. Every input accepts a static value or a variable from any upstream node in your workflow.
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 run history shows the failed step with its input and the error message Jenkins returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Trigger Jenkins Build support batch operations?
Run Trigger Jenkins Build inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Jenkins's rate limits.
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.
ActionGet Jenkins Build Status
Returns the current state of a specific build number — queued, building, success, failure, aborted. The standard polling lookup after Trigger Build.
ActionList Jenkins Jobs
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.