Extend webhook triggers so they can fire on additional field updates

Aha! webhooks can currently be triggered only by changes to a set of standard fields (name, description, status, assigned user, dates, etc.). Many teams rely heavily on tags, record links but changes to these fields cannot currently trigger an update event.

Not being able to trigger webhooks on tags, record links, or custom fields creates several operational issues:

• Missed automation events when key fields change, causing sync issues or stale data in downstream systems.

• Increased manual effort: teams must update additional fields purely to force a webhook trigger.

Extend webhook triggers so they can fire when any of the following change:

1. Additional standard fields, such as:

   • Tags

   • Record links (dependencies, related records)

   
   

2. Custom fields, including:

   • Predefined choice lists

   • Tags

   • Text fields

   • Numeric fields

   • Custom record link fields

Ideally, this should be implemented as either:

• (A) additional selectable fields in the webhook “Selected Activities” section, or

• (B) an option to trigger the webhook on any field change (standard or custom) - for volume/bandwidth/load reasons I can understand why this my not be desirable.

This enhancement would dramatically improve Aha!’s integration capabilities with non-native, custom built integrations and middleware.