Add Attachment
jira.add_attachment
ActionBusiness appsconnection required
Calls the Jira Cloud REST API with the connection's email and API token.
Attach a file to a Jira issue.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Jira
- Secret shape
- {"email", "api_token"}
- Config it needs
- domain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
5 fields, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
issue_key Issue key or numeric id, e.g. PROJ-123. Supports {{ }}. | string | Yes | — | — | — |
filename The name to store the attachment under, including its extension. | string | Yes | — | — | — |
body The file content — plain text, or a base64 blob when content_encoding is 'base64'. | string | Yes | — | — | — |
content_encoding Set to 'base64' when body is a base64 blob (e.g. from a download_archive node). Defaults to the upstream file's encoding, else text. | string | No | — | one of "text", "base64" | — |
content_type MIME type to send the part with, such as 'application/pdf'. Defaults to application/octet-stream for binary. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok True when Jira accepted the call. | boolean | — |
key The issue key the call acted on. | string | PROJ-123 |
attachments[].id The attachment's id. | string | — |
attachments[].filename The stored file name. | string | — |
attachments[].size The attachment size in bytes. | number | — |
attachments[].mimeType The MIME type Jira recorded. | string | — |
attachments[].content URL the attachment can be downloaded from. | string | — |
count How many items this call returned. | number | — |
{
"attachments": [
{
"content": "",
"filename": "",
"id": "",
"mimeType": "",
"size": 0
}
],
"count": 0,
"key": "PROJ-123",
"ok": false
}Notes
- Attachments must be enabled for the site, and the file is bounded by both Jira's own attachment limit and Mantle's inline-binary cap (MANTLE_BINARY_MAX_BYTES).
See Add Attachment run in a workflow.
In a technical demo we add the Jira connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.