Short answer: Drop the "Jira → Search Issues (JQL)" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
JQL Query jql | string | Required | Jira Query Language expression to filter issues |
Max Results maxResults | string | Optional | Maximum number of issues to return (max 100) |
Start At startAt | string | Optional | Index of the first result for pagination (0-based) |
Fields fields | string | Optional | Comma-separated list of fields to include in response. Leave empty for all. |
{"jql": "e.g. project = PROJ AND status = \"In Progress\" ORDER BY created DESC","maxResults": "50","startAt": "0","fields": "e.g. summary,status,assignee,priority"}
{"total": 42,"issues": [{"key": "PROJ-123","fields": {"status": {"name": "In Progress"},"summary": "Fix login redirect","priority": {"name": "High"}}}],"startAt": 0,"maxResults": 50}
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.
Triggered by anything in the catalog. Free tier available. No credit card.