Automation - have ELSE call another Automation?

[Darryl St_ Pierre]

We currently have an Automation that assigns a team to newly created tickets based on different attributes. The Automation is nearing its limit of 65 components, and I expect we will hit that limit soon.

My idea is to break the existing Automation into smaller parts, but I can only do that if there's a way to have the final ELSE statement call the next Automation. Or maybe there's a different way to approach this...

Essentially the Automation is a number of IF/ELSE statements assigning the Team field based on Request Type, or Application selection, or combination of both, or combination of both plus the reporter's Department. This is all designed to get specific ticket submissions directly to Level 2 support by the correct team. The final ELSE sends everything left to a Level 1 support group.

We have 17 different teams, more than a dozen Request Types, and a large number of applications which results in this very long Automation. Management's desire is to have the team assignment automated, so if there's any way to accomplish this with either a different process or "linked" automations that would be great.

[Andrea Robbins]

This is not OOTB functionality - but there is a work around. If you have the other automation rule that you want to trigger have a webhook trigger, your original automation rule can send a post request with the data the other rule needs to do whatever it needs to do.

Step 1: Create your secondary rule where the trigger is the webhook one. Use that secret in step 2.

Step 2: Create your original rule with a Send Web Request Component that sends the data to the secondary automation rule. Be sure to use the secret in the header with header name: X-Automation-Webhook-Token. Just paste the secret for the value no
"Basic" prefix or encoding of any type is needed

Step 3: Save & test!

Here's an example POST body within my original rule where I was doing a lookupIssue action and wanted to send it to the other rule (but you can also do it via the URL as well)

{
"data": {
"issues": [
"{{lookupIssues.first}}"
]
}
}

[Andrea Robbins]

After re-reading your post, I do advise actually using assets here. You can create mapping assets so if it is a particular department, request type, etc, it is auto assigned to a team.

Example irl I did:

For onboarding, I had a policy asset that said if the user was from x department, then it required y sort of access, and then I would create linked tasks per access required.

Your use case is simpler - just edit a ticket field! I think that would be easiest