Add Conditional Logic to Automation Actions

What is the challenge?

Currently, Aha!’s automation only supports conditions on the trigger—not on the actions. This creates a need to duplicate automations for each variation, such as routing Epics to different Jira projects based on the assigned team.

What is the impact?

Managing multiple near-identical automations increases maintenance overhead, clutters the automation interface, and introduces risk of inconsistency across teams and workflows.

Describe your idea

Enhance the automation engine by allowing conditional logic within the action section. For example:

Trigger: When Epic Status changes to "Ready to Develop"

Actions:

• Send to Jira Integration A (If Epic Team = Team A)

• Send to Jira Integration B (If Epic Team = Team B)

This would allow a single automation rule to cover multiple routing scenarios based on field values like team, user assignment, or a certain related record, streamlining setup and reducing duplication.