Hubspot Endpoint coming back as not found

Questions
1

I keep getting this error (usually in testing)

NodeOperationError: The resource you are requesting could not be found
    at Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Hubspot/V2/HubspotV2.node.js:2540:31)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at Workflow.runNode (/usr/local/lib/node_modules/n8n/node_modules/n8n-workflow/dist/Workflow.js:646:28)
    at /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/WorkflowExecute.js:631:53

I’m calling a Hubspot endpoint (get contact) that I have used in this n8n workflow for a long time, but periodically this error happens. So, the endpoint definitely exists and there’s no reason it should give a “not found” error. I’ve found that I can try this endpoint in a few minutes and it works fine, so there’s a bug somewhere. Any ideas how to even track this down? I can’t imagine that the production Hubspot API is this unreliable that it goes down multiple times a day nearly every day, so I’m currently pointing the finger at n8n.

Thanks,
JMR

3

Hi @jmr123 :wave:

Sorry to hear you’re running into this - can you give us some more details about your workflow? Are you sending over any other properties as well, or alternatively is your workflow pulling in data that sometimes might not exist? If you can provide an example workflow that triggers this error, that’d be helpful!

Can you also fill out this template:

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

I’m using all the default settings for cloud n8n with the latest version (1.0.5). My laptop is MacOS.

This error just happened again in a different workflow, but your comment: “or alternatively is your workflow pulling in data that sometimes might not exist” was the key to figuring this out.

Somehow we had users creating accounts with no emails that went into this flow and we tried to call hubspot to create a user, but there was no email, so Hubspot errors. The error message they send isn’t helpful at all (it makes it sound like it’s a non-existent endpoint), but I can deal with that.

I added in some IFs to handle this case should it arise. Thanks for pointing me in the right direction!

2 Likes
5

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