Set Validity End Date in Docebo Connect from Salesforce

Hi ​@michaelp , welcome to Docebo!

When I've deployed Salesforce-to-Docebo Connect flows for organizations with similar requirements, this exact timezone/date-shift issue comes up almost every time.

Here is how to resolve both issues:

1. The "Day Before" Issue (Begin Validity) You are right on the money, it is a UTC conversion issue. Docebo stores all date parameters strictly in UTC. When Salesforce sends a local date (e.g., midnight in your local timezone), Docebo processes the conversion and it shifts backward into the previous day. The Fix: In Docebo Connect (Workato), switch your "Date Begin Validity" mapping field to Formula mode. Force the timezone to UTC and format it as a string so Docebo receives exactly what it expects. You'll want to use a formula similar to: [Your Salesforce Date Field].to_time.in_time_zone("UTC").strftime("%Y-%m-%d %H:%M:%S")

2. Date End Validity Not Setting When the Docebo API silently ignores an End Date payload from Connect, it usually comes down to one of two things:

• Course Settings Conflict (Most Likely): Check the course in the Docebo UI (Course Management > Properties > Advanced Settings > Time Options). If the course is configured to use "Days of validity" (e.g., valid for 30 days after enrollment), the system will automatically override and ignore any explicit End Date you send through Connect.

• Format Mismatch: Ensure you are applying the exact same string formatting formula to the End Date as you are to the Begin Date.

Here is a helpful Help Center article that explicitly breaks down how Docebo processes Start and End validity dates strictly in UTC, which mirrors exactly how the backend handles your Connect payloads: Activating and managing the Enrollment rules app

Give that Workato formula a try and double-check those specific course Time Options, and you should see both dates locking in correctly!