Trigger Jenkins Build: Jenkins action

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.

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 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 Trigger Jenkins Build support batch operations?

Yes. Run Trigger Jenkins Build inside a Loop node to process arrays. Tiny Command handles Jenkins's rate limits automatically so you don't have to throttle manually.

More actions