Merging Binary + JSON

Describe the problem/error/question

I’m trying to get both Binary Data and JSON data to a node (Jira attachment creation), and it seems I can only get one or the other to be accessible at the node. In this configuration, I can only access the data. Even though I can see the JSON and Data both.

What is the error message (if any)?

No error message, other than the Jira node telling me either the ticket doesn’t exist or it didn’t get binary data.

Please share your workflow

Snippet of relevant area. (I posted the workflow below but it’s not showing up)

Share the output returned by the last node

The output is the error it usually is either issue not found or no binary data.

Information on your n8n setup

  • n8n version: 0.236.3
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): own? (Default)
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: Not sure

Hi @Donomoto ,
unfortunately I cannot see your workflow (there’s a temp problem with workflows embedding) but I can try to help you anyway.

In the Jira node add Issue Attachment you can only attach one file at a time.
So the best solution is to have 2 items with the 2 files you want to attach (JSON + Binary Data) and have the Jira node running 2 times and do the 2 attachments separately.

If you want to attach the JSON file you have to use the Move Binary Data node. Pay attention to set the File Name to something ending with .json.

I copy below a demo workflow, let me know if it helps.

1 Like

Hi @giulioandreinil,

I apologize for the confusion. The merging of the two was meant to be for the input data into the Jira node. I’m trying to take the output of a DB query, and use that to set the issue ID, and use the binary data from another node to be the attachment itself. Here’s a picture of the workflow I’m attempting:

I am new to n8n, and could just be doing something fundamentally wrong. When I do the above, it seems the Jira node can access the binary data, but not {{ $json.ticket_id }}

Thank you for your response!

Hi @Donomoto ,
to make this easier you can leave the node structure as you have, but in the Jira Software node you can refer directly to the ID in the Postgres node by writing {{ $('Postgres') }}.
This will go and look for the ID directly in the Postgres node (and not in the Merge node).

I attach an example workflow below.

Let me know if this helps.


This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.