Wrong number of executions using Zendesk Search User Node and Always Output Data

[Rafael_Serrano]

Describe the problem/error/question

I’m building a workflow to update the user database in Zendesk. Basically, I search for an email using the Zendesk Search User Node and will perform different actions if the user is present or not, therefore I switched the “Always Output Data” flag to generate an empty response (same number of items in and out). However, this is not happening and the Zendesk seems to stop executing after first empty response. Is this a bug or am I missing something?

Please share your workflow

This is a simplified version of my workflow. “Edit Fields1” returning a JSON array with 3 emails, first one not present in Zendesk, the other two are, i.e. [“[email protected]”,"[email protected]","[email protected]"].

Share the output returned by the last node

Zendesk just returns empty response item.

Information on your n8n setup

• n8n version: 1.47.0
• Database (default: SQLite): Postgres
• n8n EXECUTIONS_PROCESS setting (default: own, main):
• **Running n8n via (Docker, npm, n8n cloud, desktop app): ** docker
• Operating system: N/A

[ria]

Hi @Rafael_Serrano

Thanks for posting here and welcome to the community!

I recreated your scenario and gave it 3 email addresses of which only 2 exist in Zendesk. Those 2 items were returned successfully.

If you toggle the Always Output Data option it will only make sure that your workflow has output even if none of the emails was found.

It does not mean it will return NULL for that one email that couldn’t be found. (i.e. 3 items in > 3 items out will not happen - This is by design.)

What are you trying to achieve? Perhaps you could use a Merge node if you rely on having the unfound email addresses?

[Rafael_Serrano]

Hi, thanks for the clarification. I was actually trying to get that 3 in, 3 out, but as you said this is by design, so the alternative is to use the merge node as you pointed out.

Thank you!