Skip to content

Commit adac18a

Browse files
authored
Merge pull request #7404 from segmentio/joeynmq-patch-5
Add info about resolving a 404 error in Intercom
2 parents d4b1da3 + 8d133a6 commit adac18a

File tree

1 file changed

+5
-0
lines changed
  • src/connections/destinations/catalog/actions-intercom-cloud

1 file changed

+5
-0
lines changed

src/connections/destinations/catalog/actions-intercom-cloud/index.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,3 +47,8 @@ If a company is created without an attached user, the company does not appear on
4747

4848
### Why isn’t a user getting attached to a company?
4949
When you use the Identify Company action, Segment creates or updates a company's information. In the same action, Segment also attaches the user in your group call to that company. If the user doesn't exist in Intercom when the action runs, Segment creates or updates the company but can't attach the user. Ensure the user is created in Intercom first.
50+
51+
### Why do I get a 404 Not Found error when sending Track events to Intercom?
52+
A `404 Not Found` error typically occurs when attempting to update a user in Intercom who does not yet exist in the system. This can happen if an Identify event, which includes the corresponding `userId`, was not sent before the Track event that resulted in the `404` error.
53+
54+
To resolve this, ensure that Identify events are sent **before** Track events to ensure proper processing and avoid errors.

0 commit comments

Comments
 (0)