Hello Atlassian Community,
We are currently configuring an automated Jira Service Management (JSM) intake workflow for an automotive fleet repair desk.
When an agent creates an asset ticket with a UK registration plate, a Jira Automation rule triggers an outgoing Webhook GET request to an external UK vehicle lookup API (regchecker.co.uk) to automatically populate custom fields (e.g., MOT Expiry, Fuel Type, Engine Size).
System Architecture & Automation Setup:
- Data Source: (
regchecker.co.uk) - Mechanism: Jira Automation Rule -> Send Webhook (
HTTP GET) -> Target Endpoint(regchecker.co.uk/?vrn=){{issue.customfield_10012}}) -> Map JSON response to JSM custom fields. - Environment: Jira Service Management Cloud.
Technical Issue / Query:
- Jira Webhook Execution Timeout: Intermittently, Jira Automation marks the execution as
Failed (504 Gateway Timeout) or Execution taking longer than 5000ms, even though direct browser/Postman queries respond under 200ms. - JSON Array Field Parsing in Smart Values: When parsing the returned nested MOT advisory logs via Jira Smart Values (
{{webhookResponse.body.advisories}}), null arrays cause the remaining custom asset fields to fail updating.
Troubleshooting Steps Taken:
- Verified that raw backend responses from
regchecker.co.uk complete within 200ms outside Atlassian Cloud infrastructure. - Added explicit
Headers: Accept application/json inside the Jira Webhook configuration.
Has anyone experienced intermittent Webhook timeouts or JSON array mapping failures when calling external REST APIs inside Jira Cloud Automation rules? Any tips on optimizing Smart Value JSON parsing?
Thanks in advance!