fix(intercom): send last_seen_at as unix seconds when upserting contacts - #1452
Open
tevaum wants to merge 1 commit into
Open
fix(intercom): send last_seen_at as unix seconds when upserting contacts#1452tevaum wants to merge 1 commit into
tevaum wants to merge 1 commit into
Conversation
tevaum
marked this pull request as ready for review
August 10, 2026 15:02
Author
|
Let me know if a GH issue is also needed. I can create one with details and logs of the specific problem I'm having on my instance. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
last_seen_atas an integer unix timestamp increateOrUpdateContact, matching the event andupdateLastSeenOnEveryEventpaths in the same fileWhy
Intercom's contacts API rejects the ISO-8601 string with
400 parameter_invalid("'last_seen_at' must be a Unix timestamp in seconds (integer), got String"), so every
identifyevent carrying an email failed to create or update its contact. The payload isused for both
POST /contactsandPUT /contacts/:id, so contact sync fails in bothbranches. Observed on 2.8.5 and reproduced on current
newjitsu.