Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Jira Cloud, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands.
All connector references · Connect an account · AI setup and shared results
Find issues using a Jira JQL expression.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Jira Cloud connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
| JQL | text | Required. Jira search expression such as project = DEMO ORDER BY updated DESC. Use accessible projects and valid Jira fields. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| Cursor | text | Optional. Continuation value from nextPageToken. Omit for the first page. Copy it unchanged and keep the same filters. Twidget text limit: 32,768 characters; provider-specific limits may be lower. |
| Limit | number | Optional. Maximum items requested in this page. Omit for 25; use a whole number from 1 to 100. The provider may return fewer items. |
Result
Returns issues with nextPageToken and/or isLast when supplied by Jira. Reuse the same JQL and put nextPageToken into Cursor to continue.
Example
Choose your Jira Cloud Account and add Search issues. Set JQL = "project = DEMO ORDER BY updated DESC"; Limit = 10. Leave Cursor unset for the first page. These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Check site access, JQL, required project fields and issue types. The sample Fields object may need extra fields for your project. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Read a Jira issue by key or ID.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Jira Cloud connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
| Issue | text | Required. Issue key such as DEMO-1, or its issue ID. The connection needs access to that project. Twidget text limit: 8,192 characters; provider-specific limits may be lower. |
Result
Returns id, key and fields accessible to the connected user.
Example
Choose your Jira Cloud Account and add Get issue. Set Issue = "DEMO-1". These are illustrative values: replace example IDs and addresses with your own permitted test values. Inspect the returned result before continuing.
Errors and limits
Check site access, JQL, required project fields and issue types. The sample Fields object may need extra fields for your project. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Create an issue using the target project’s field structure.
Inputs
| Input | Type | How to use it |
|---|---|---|
| Account | Account | Required. Choose a saved Jira Cloud connection from this workspace’s account selector. Create or reconnect it in Settings > Connectors first. Do not paste a password, API key or token into this field. |
| Fields | object | Required. Object of Jira field IDs, for example {"project":{"key":"DEMO"},"summary":"Demo request","issuetype":{"name":"Task"}}. Add any fields required by your project; rich descriptions need Jira document format. Supply an object, not text containing an object; all inputs together must fit within 64 KiB. |
Result
Returns id, key and self for the new issue. Required project fields and permitted issue types must be satisfied.
Example
Choose your Jira Cloud Account and add Create issue. Set Fields = {"project":{"key":"DEMO"},"summary":"Demo request","issuetype":{"name":"Task"}}. These are illustrative values: replace example IDs and addresses with your own permitted test values. An intended live run creates/changes data or sends a message; inspect its receipt before repeating it.
Errors and limits
Check site access, JQL, required project fields and issue types. The sample Fields object may need extra fields for your project. Reconnect an unavailable connection in Settings > Connectors. Isolated tests and live debugging do not contact external services; Use live data is needed for an intended live call. If rate-limited, wait before retrying. Total input is limited to 64 KiB and results to 2 MiB; use smaller pages, narrower filters or less depth when too large. Calls wait up to 30 seconds, or less if the workflow reaches its own time limit. A timeout does not prove that a create/send failed, so check the provider before repeating it.
Isolated tests and live debugging do not call connected providers. Enable Use live data only when you intend to contact the account. Writes, messages and AI requests can change real data or incur provider charges. A successful connection check does not prove access to every action. These examples explain the command contract; they are not evidence of a completed live provider request.
Dropbox commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Dropbox, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [All ...
Google Gemini commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Google Gemini, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands....
Mailchimp commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Mailchimp, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [Al...
Perplexity commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → Perplexity, select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [A...
xAI (Grok) commands
Use these commands from an endpoint, server function or event. Choose Add Command → Connector → xAI (Grok), select the action, then choose an Account. Selecting an account reveals the remaining inputs. When the command returns a result, open OUTPUT and use Return as to name it for later commands. [A...
