HubSpot Seach Contacts doesn't return results with "Return all" enabled

Questions
1

Describe the problem/error/question

I’m working with the HubSpot node to search for contacts using an email address. However, with the “Return all” option enabled, the node doesn’t return any results even though I’m sure contacts exist. When I disable this option, the contacts are found. This has been happening since I upgraded to 0.228.2.

I realize this is rather a minor issue with an easy workaround solution, just wanted to point out it’s there.

What is the error message (if any)?

The HS node doesn’t return any results with the “Return all” option enabled.

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: 0.228.2
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: W11
2

Hey @antitalent,

Thanks for reporting this one, I have just taken a look but I was not able to reproduce it.

image
image1303×764 91.8 KB

Does the email you are using exist for 2 different contacts maybe?

3

Hi @Jon, thank you. Hm, that’s interesting, all my workflows with this node don’t return any output.

Does the email you are using exist for 2 different contacts maybe?

Nope, the node is working as expected when I turn off the “Return all” option.

Could you please copy the node from my example workflow and test it?

4

Hey @antitalent,

I did try to copy your node but for some reason it had no credentials appearing so wouldn’t work but it looks like it was just because of the edit you made during the post.

5

Yeah I deleted the credentials, I meant to test it with my node but your own credentials. Anyway, they are the same nodes after all so it probably wouldn’t make a difference. May I ask if you’re on 0.228.2?

6

Hey @antitalent,

I am currently on 0.231.0, Give me 2 minutes to downgrade it and I will test on 228.2 as well

7

So I’ve tried the same node but a new one and there’s no such issue. Only for existing nodes.

8

Interesting that sounds like it is an issue with the v1 node, We did release v2 which may have fixed this.

1 Like
9

Thanks @Jon. So I guess I have to replace the nodes with new ones.

1 Like
10

Hey @antitalent,

That might be the quickest option if you use this option often.

11

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