Issue Station
Sign In
Tools hereToolbox

n8n - 💡(How to fix) Fix Update User in Intercom through nodes keeps giving 404 error [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
n8n-io/n8n#28580•Fetched 2026-04-17 08:54:49
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
thomaslaureys-bitthomaslaureys-bit
Participants
n8n-assistant[bot]n8n-assistant[bot]thomaslaureys-bitthomaslaureys-bit
Timeline (top)
commented ×1labeled ×1mentioned ×1subscribed ×1

Error Message

Describe the problem/error/question

When setting up a node to update a user in Intercom I keep getting an 404 error.

What is the error message (if any)?

"type": "error.list"

  • error: all

Code Example

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.
RAW_BUFFERClick to expand / collapse
<!-- Please follow the template below. Skip the questions that are not relevant to you. -->

Describe the problem/error/question

When setting up a node to update a user in Intercom I keep getting an 404 error.

The resource you are requesting could not be found Request failed with status code 404

I am using the exact same flow for updating a company in Intercom and that works flawless with the same credentials.

What is the error message (if any)?

Problem in node ‘Update Company in Intercom‘ The resource you are requesting could not be found

Please share your workflow/screenshots/recording

<img width="1403" height="853" alt="Image" src="https://github.com/user-attachments/assets/7c1485e4-bf8e-497c-80bc-ea59709229fa" /> 
(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)
⚠️ WARNING ⚠️ If you have sensitive data in your workflow (like API keys), please remove it before sharing.

Share the output returned by the last node

{ "errorMessage": "The resource you are requesting could not be found", "errorDescription": "Request failed with status code 404", "errorDetails": { "rawErrorMessage": [ "Request failed with status code 404" ], "httpCode": "404", "errorData": { "errors": [ { "code": "not_found", "message": "The requested resource does not exist; check your path and try again" } ], "type": "error.list" } }, "n8nDetails": { "nodeName": "Update Company in Intercom", "nodeType": "n8n-nodes-base.intercom", "nodeVersion": 1, "resource": "user", "operation": "update", "time": "16/04/2026, 15:00:58", "n8nVersion": "2.16.1 (Cloud)", "binaryDataMode": "filesystem", "stackTrace": [ "NodeApiError: The resource you are requesting could not be found", " at ExecuteContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1158:9)", " at processTicksAndRejections (node:internal/process/task_queues:104:5)", " at ExecuteContext.httpRequestWithAuthentication (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/node-execution-context/utils/request-helper-functions.ts:1531:11)", " at ExecuteContext.intercomApiRequest (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/Intercom/GenericFunctions.ts:30:10)", " at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-nodes-base@file+packages+nodes-base_@[email protected]_asn1.js@5_8da18263ca0574b0db58d4fefd8173ce/node_modules/n8n-nodes-base/nodes/Intercom/Intercom.node.ts:381:23)", " at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:8)", " at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1224:11)", " at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1672:27", " at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@opentelemetry+exporter-trace-otlp_2d19a9be2839cb42cd2e8c9cacd05d5a/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2324:11" ] } }

Debug info

core

  • n8nVersion: 2.16.1
  • platform: docker (cloud)
  • nodeJsVersion: 24.14.1
  • nodeEnv: production
  • database: sqlite
  • executionMode: regular
  • concurrency: 50
  • license: enterprise (sandbox)

storage

  • success: all
  • error: all
  • progress: false
  • manual: true
  • binaryMode: filesystem

pruning

  • enabled: true
  • maxAge: 720 hours
  • maxCount: 25000 executions

client

  • userAgent: mozilla/5.0 (macintosh; intel mac os x 10_15_7) applewebkit/537.36 (khtml, like gecko) chrome/147.0.0.0 safari/537.36
  • isTouchDevice: false

Generated at: 2026-04-16T12:53:51.339Z

extent analysis

TL;DR

The most likely fix is to verify the user ID or path being used in the Intercom update request to ensure it matches the expected format and exists.

Guidance

  • Check the user ID being passed to the Intercom update node to ensure it is correct and properly formatted.
  • Verify that the user exists in Intercom and that the ID matches the one being used in the request.
  • Compare the configuration and input of the working "Update Company in Intercom" node with the non-working "Update User in Intercom" node to identify any differences.
  • Ensure that the authentication credentials and permissions are correctly set up for updating users in Intercom.

Example

No code example is provided as the issue seems related to configuration or data rather than code.

Notes

The error message "The resource you are requesting could not be found" suggests that the issue is likely related to the user ID or path being incorrect. The fact that updating a company works with the same credentials implies that the authentication is correct, but there might be a difference in how user IDs are handled or formatted.

Recommendation

Apply a workaround by double-checking the user ID and path formatting, and ensure that the user exists in Intercom before attempting to update. This approach is recommended because it directly addresses the likely cause of the error without requiring significant changes or upgrades.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#API rate limit#retriever error#indexing error#inference speed

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING