Salesforce date field sync issues | Community
Skip to main content
Answered

Salesforce date field sync issues

  • September 10, 2026
  • 1 reply
  • 73 views

Hi, does anyone have a current workaround for syncing date fields from Salesforce to Intercom without the date shifting due to timezone differences?

We’re sending renewal messaging from Intercom using a Renewal Date field mapped from Salesforce. Unfortunately, the date is syncing as one day earlier than the date in Salesforce. Intercom Support explained that this is because the sync occurs at UTC 0, which is causing the incorrect renewal date to appear in our customer notices.

Has anyone found a way to prevent this timezone conversion? Or is the best workaround to create a secondary Renewal Date field in Salesforce that adds one day to the actual renewal date and map that field to Intercom instead?

Best answer by melzayat

Hi ​@Lorena Vigil ! 

If you'd rather not maintain a +1 day shadow field in Salesforce, another option could be a small side sync (Zapier, Workato, or a Flow + Apex callout) that pushes renewal_date to Intercom via the API as a DD/MM/YYYY string instead of letting the native Salesforce app handle it.
Intercom explicitly documents that format as timezone-agnostic... It won't get translated the way a Unix timestamp does, so it sidesteps the rollback entirely.

Trade-off is you'd be managing that one field outside the standard native integration, so worth weighing against just keeping the +1 day approach if the maintenance isn't worth it for one field. 

    1 reply

    melzayat
    Innovator ✨
    Forum|alt.badge.img+2
    • melzayat
    • Innovator ✨
    • Answer
    • September 10, 2026

    Hi ​@Lorena Vigil ! 

    If you'd rather not maintain a +1 day shadow field in Salesforce, another option could be a small side sync (Zapier, Workato, or a Flow + Apex callout) that pushes renewal_date to Intercom via the API as a DD/MM/YYYY string instead of letting the native Salesforce app handle it.
    Intercom explicitly documents that format as timezone-agnostic... It won't get translated the way a Unix timestamp does, so it sidesteps the rollback entirely.

    Trade-off is you'd be managing that one field outside the standard native integration, so worth weighing against just keeping the +1 day approach if the maintenance isn't worth it for one field. 

    Mel Zayat - Book time with me to review your Intercom and CS workflows: https://calendar.app.google/7DD4MHxouqcEcopc8
    Terms & ConditionsAccessibility statement