Description

I’m using the Jobber → New Request trigger in Zapier, and under the Visits section the Start At and End At fields are consistently wrong:

• A visit scheduled in Jobber for April 18 2025 at 1:00 PM (America/New_York)

• Trigger output shows Start At: 2025-04-18T04:00:00Z

• Even though that’s UTC, 1 PM EDT should map to 2025-04-18T17:00:00Z (or 16:00:00Z if EST), not 04:00:00Z 

• Similarly, an end time of 3:00 PM becomes 2025-04-19T03:59:59Z instead of the correct UTC equivalent

Steps to Reproduce

1. In Jobber, create a test job with a single visit on 2025‑04‑18 at 1:00 PM.

2. In Zapier, set up a Jobber → New Request trigger (or your GraphQL webhook) and fetch the sample data.

3. Inspect the startAt and endAt fields in the test output.

Expected vs. Actual

• Expected: startAt ≈ 2025-04-18T16:00:00Z – 17:00:00Z (based on EDT)

• Actual: startAt = 2025-04-18T04:00:00Z

• Expected: endAt ≈ same-day afternoon UTC

• Actual: endAt = next day 03:59:59Z

 What I’ve Tried

• Verified my Zapier account timezone is set to America/New_York

• Confirmed the Jobber account timezone is also America/New_York

• Deleted/re-created the Zap and re-ran the test sampling

• Looked at Jobber+Zapier integration docs—no mention of special overrides

• Checked GraphQL best‑practices on ISO8601DateTime fields (they should include your offset)

• Noted community threads on Zapier timezone quirks (e.g., full-date vs. date-only conversions)

Questions for the Community

• Has anyone else seen Jobber’s startAt/endAt come back as 04:00:00Z (or 3:59:59Z) instead of the actual scheduled time?

• Could Jobber’s API be omitting the timezone offset on startAt so Zapier treats it as UTC midnight?

• Is there a known workaround or a hidden Zapier setting to force the correct offset?

• Failing that, any pointers on using Formatter by Zapier to reliably shift from 04:00Z → local time?

Thanks in advance for any insights or fixes!