Add Attachment - BlinkOps Documentation

Adds one or more attachments to an issue. Attachments are posted as multipart/form-data (RFC 1867). Note that:

The request must have a X-Atlassian-Token: no-check header, if not it is blocked. See Special headers for more information.
The name of the multipart/form-data parameter that contains the attachments must be file.

This operation can be accessed anonymously. Permissions required:

Browse Projects and Create attachments project permission for the project that the issue is in.
If issue-level security is configured, issue-level security permission to view the issue.

Parameters

Parameter	Description
File Identifier	The file identifier of the attachment. A file identifier represents a file created or referenced earlier in the workflow (for example, from a file action or another step that produces a file). See Using with Files in Workflows for more details.
File Name	The name of the file.
Issue ID Or Key	The ID or key of the issue. Can be obtained via the `List Issues` action.

Example Output

[
	{
		"self": "<string>",
		"id": "<string>",
		"filename": "<string>",
		"author": {
			"self": "<string>",
			"name": "<string>",
			"key": "<string>",
			"emailAddress": "<string>",
			"avatarUrls": {
				"48x48": "<string>",
				"24x24": "<string>",
				"16x16": "<string>",
				"32x32": "<string>"
			},
			"displayName": "<string>",
			"active": true,
			"timeZone": "<string>"
		},
		"created": "2024-10-30T08:03:29",
		"size": 768,
		"mimeType": "<string>",
		"content": "<string>"
	}
]

Workflow Library Example

Add Attachment with Jira Data Center and Send Results Via Email

Preview this Workflow on desktop

​Parameters

​Example Output

​Workflow Library Example

Parameters

Example Output

Workflow Library Example