🚀 Jira Automation – Can we keep everything within one rule?

[AtlaBeacon]

Hi Atlassian experts 👋
I'm exploring the capabilities of Jira Automation and have a question:
Let’s say we want to retrieve all users belonging to a specific group using the Send web request action.
Once we get the API response, can we then loop through each user and perform additional actions (e.g., calling another API per user) —
all within a single automation rule, without having to trigger another rule via webhook?
I'd love to hear from others who have tried similar setups — is it feasible using advanced branching and smart values alone?
Any insights or creative solutions are very welcome! 🙏

[Bill Sheboy · Accepted solution]

Hi @AtlaBeacon -- Welcome to the Atlassian Community!

Simple, short answer: yes, that is possible using an Advanced Branch over the initial web response values, and...

• Such branches are limited to 100 items
• Branches over more-than-one-thing process in parallel and asynchronously, with no predictable ordering, and no guarantee of when they will complete until the last rule step.  Specifically, steps in the rule shown after the branch will start before the branch completes.
• I have recently learned there are memory / resource limits to branching, and so if your initial web response is large the rule could halt part way through because of the amount of data passed to each iteration
• Similarly, for larger branch counts and processing, the rule could encounter other automation limits for time, load, etc. which lead to throttling of rules

Kind regards,
Bill

[AtlaBeacon]

Hi @Bill Sheboy ,

Thank you for response!

Can you please give me more details on how you say this is possible?

-------------

I'll explain specifically what I'm trying now.

Execute the following API in JiraAutomation.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-groups/#api-rest-api-3-group-member-get

When you run it, you will of course get a response in Smart Value.

{{webhookResponse.body}}

The data I want to use is the following, as described in the response in the official documentation.

"values": [ { "accountId": "5b10a2844c20165700ede21g", "accountType": "atlassian", "active": true, "avatarUrls": {}, "displayName": "Mia", "emailAddress": "mia@example.com", "key": "", "name": "", "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a2844c20165700ede21g", "timeZone": "Australia/Sydney" }, { "accountId": "5b10a0effa615349cb016cd8", "accountType": "atlassian", "active": false, "avatarUrls": {}, "displayName": "Will", "emailAddress": "will@example.com", "key": "", "name": "", "self": "https://your-domain.atlassian.net/rest/api/3/user?accountId=5b10a0effa615349cb016cd8", "timeZone": "Australia/Sydney" } ]

I want to loop through only this account ID.

In that case, what kind of Advanced Branch rule configuration is needed?

Thank you for your support.

Regards,
AtlaBeacon

[Bill Sheboy]

First thing: successfully using automation rules requires learning and experimentation. 

I recommend trying things, and if you run into challenges, post images of your rule, the audit log details, and explain what is not working as expected.  This will increase the chances the community can help you be successful.

For the endpoint you note, you saw what is returned, including how a values list containing the attribute accountId.

In the rule after the Send Web Request action to call the endpoint, you could iterate over the list values like this with an Advanced Branch.  This is quite similar to what is shown in the documentation.

• action: Send Web Request
• Advanced Branch
  • smart value: {{webResponse.body.values.accountId}}
  • variable name: varAccountId
    • some action using {{varAccountId}}
    • ...

[AtlaBeacon]

Hi @Bill Sheboy 

I solved it with your method.

Thank you for your support.

Regards,
AtlaBeacon