Multiple items input, just one output

Describe the issue/error/question

I have a ClickUP node that has an input of multiple items (ex: 8) and has to do a search by key to return a task if it exists or empty result if not. The problem is that ClickUP node gets executed only for the first item, and I need all of them to know if I need to create tasks or update existing ones.
I have “Always output data” checked in the node, but it just runs for the first item.

What is the error message (if any)?

Please share the workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 1.9.0
  • Database you’re using (default: SQLite):
  • Running n8n with the execution process [own(default), main]:
  • Running n8n via [Docker, npm,, desktop app]: desktop

Hi @Cristi_Milea, so if I’m understanding correctly you’re clickup node only finds a task for one of the inputs and you would expect it to return 7 “empty items” in addition to that. Is that correct? I think the Always Output Data option does not help you here because it only helps when the node does not have any item.

One approach that you could try is to have another merge node in which you add the output data of the clickup node to each of the 8 items. This way you could look if the item has the additional field or not and still have all 8 items.

Hi @Niklas_Hatje , thank you for the response.

From my understanding reading the docs, if a node has an input of N items, it will be executed N times. So, I was expecting for the ClickUp node to be executed 8 times, having an input of 8 items.

Did I understand wrong?

No that is correct @Cristi_Milea. The node does indeed get executed 8 times in your example. But apparently it only find one item that matches your filter criteria. For the other 7 times it will not return any data and thus only have 1 item after executing.

Always output data is a little weird to understand here, as it seems to only output data once the node has 0 items (after all its executions), not for every run. It’s mainly there to prevent your workflow from stopping at that node.

So In your case I’d go with something like this

1 Like

Thank you, that worked!
I agree, “always output data” is difficult to understand.

1 Like

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