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.
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 |
{"job_name": "e.g. my-pipeline or folder%2Fmy-pipeline","parameters": "{\"BRANCH\": \"main\", \"DEPLOY_ENV\": \"staging\"}"}
{"success": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.