Thanks for reaching out about formatting the start_time from the Calendly API for use in Jira Automation!

You're correct that the Calendly API v2 returns timestamps in ISO 8601 format with microseconds and a Z to indicate UTC—for example:
2025-06-25T05:00:00.000000Z

Jira, on the other hand, expects timestamps in a slightly different ISO 8601 format without microseconds and with an explicit UTC offset, like:
2020-08-18T02:40:37.0+0000

To make the Calendly start_time compatible, you'll need to reformat it before passing it into your Jira Automation logic. Here's a general approach you can use:

Option 1: Use Jira Smart Value Formatting

If you're passing the raw value into Jira via webhook, you can try formatting the value using Jira's Smart Value date functions, like this:

{{webhookData.start_time.convertToDate.format("yyyy-MM-dd'T'HHss.SZ")}}

Note: Jira may not support microseconds, so you might need to trim .000000Z from the end of the start_time string using string manipulation before formatting.

Option 2: Pre-process the timestamp externally

If Jira Smart Values can't handle the conversion directly, consider passing the timestamp through a small middleware (e.g. a webhook, Zapier, or AWS Lambda) that:

1. Converts 2025-06-25T05:00:00.000000Z → 2025-06-25T05:00:00.0+0000

2. Sends the formatted timestamp to Jira Automation in the format it expects

While implementing this logic on your end is out of scope for Calendly Support, feel free to reach out to our team if you have questions—we're here to support you and will help to the best of our ability!

You can contact us via live chat (look for the blue chat bubble in the lower right when logged into a paid Calendly account), or email us at support@calendly.com.