Skip to content

fix(intercom): send last_seen_at as unix seconds when upserting contacts - #1452

Open
tevaum wants to merge 1 commit into
jitsucom:newjitsufrom
tevaum:fix/intercom-last-seen-at-unix-seconds
Open

fix(intercom): send last_seen_at as unix seconds when upserting contacts#1452
tevaum wants to merge 1 commit into
jitsucom:newjitsufrom
tevaum:fix/intercom-last-seen-at-unix-seconds

Conversation

@tevaum

@tevaum tevaum commented Aug 10, 2026

Copy link
Copy Markdown

What

  • Send last_seen_at as an integer unix timestamp in createOrUpdateContact, matching the event and updateLastSeenOnEveryEvent paths in the same file
  • Add mocked create/update tests asserting the payload Intercom receives

Why

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
identify event carrying an email failed to create or update its contact. The payload is
used for both POST /contacts and PUT /contacts/:id, so contact sync fails in both
branches. Observed on 2.8.5 and reproduced on current newjitsu.

@tevaum
tevaum marked this pull request as ready for review August 10, 2026 15:02
@tevaum

tevaum commented Aug 10, 2026

Copy link
Copy Markdown
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant