Go High Level Tool in Agent fail

Questions
1

Describe the problem/error/question

I’m using a separated workflow agent to handle the contacts in go High Level. I realized that the node out of the tool works fine, but the same node in a tool with the same parameters doesn’t show nothing. Don’t fail but doesn’t return values.

What is the error message (if any)?

Doesn’t exist results in the tool

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version: Version 1.85.4
  • Database (default: SQLite): SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker on google cloud- Operating system: Linux
2

Hi,

Can you correctly copy and paste in between a code segment so it would display correctly?

thanks
J.

3

I’m sorry. It’s already done. thanks

4

Hi, not sure what the problems is but the Ai selects the right tool (i don’t have a go high level) but i would recommend to use better descriptions for the tools and not leave them on auto. also tell what parameters they require. and your system description is also confusing. sometimes its chequear_contato other times its chequar_usario etc. not sure whether this is the reason why it doesn’t do what it’s supposed to do but its a start.
reg,
J.

5

Thanks for the reply. I understand the point of view, but I think that’s not the main problem. I use the node of GHL out of the tool and it works. But linked to the agent with the same values and of course credentials it doesn’t returns nothing. It’s confusing because I’ve tried lots of prompts and I now that the value to consult is correct but nothing is returned. :frowning:

1 Like
6

Anyone has the same problem??

7

were you able to resolve this? I’m facing the same issue where it’s selecting the node with the correct information but it doesn’t seem to be calling the API or persisting it to GHL

8

Hi flexstay, I couldn’t find to resolve yet. now I am using an agent in order to choose the best path with will find a native node not tool node of GHL. It works, but it should’nt be like that.

9

I have the same issue. For any tool, it gives an error