Knowledge Base Articles
Knowledge Base Articles
Breadcrumbs

Jira automation rule with a Tempo API call (web request) isn't working

Symptom

A Jira automation rule that calls the Tempo API (for example, using the "Send web request" action to create or update a worklog) fails or returns an unexpected result. Common signs:

  • The rule's audit log shows a failed web request action or an error status code (such as 400, 401, 403, or 404).

  • The rule runs but no data is created or changed in Tempo.

  • The rule doesn't trigger, or smart values in the request body aren't resolved.

Cause

Jira automation is a native Atlassian feature, and Tempo doesn't provide support for building, configuring, or troubleshooting automation rules. Failures usually come from one of these:

  • The API request is incorrect (wrong endpoint, headers, authentication token, or body format).

  • The automation rule is misconfigured (trigger, conditions, smart values, or permissions).

Tempo can only help confirm that the Tempo API call itself is valid.

Resolution

    1. Test the API call outside Jira first. Send the same request in Postman (or a similar API client) using the same endpoint, headers, authorization token, and body.

    2. If the call fails in Postman, the problem is in the request. Check the following against the Tempo API documentation:

      • The endpoint and HTTP method

      • The API token (valid, not expired, and with the right permissions)

      • The Authorization: Bearer <token> header

      • The JSON body and required fields

    3. If the call succeeds in Postman, the request is valid, and the issue is in the automation rule. Review the rule's audit log and the smart values used in the request, then contact Atlassian:

    4. If the call still fails in Postman and you've verified the above, contact Tempo Support with the request (with the token removed), the response, and the status code.