When configuring manual event actions using a URL, only a limited set of macros is supported. According to the documentation (Supported macros by location), the following event macros are currently available in this context:

• {EVENT.ID}
• {EVENT.NAME}
• {EVENT.NSEVERITY}
• {EVENT.SEVERITY}
• {EVENT.STATUS}
• {EVENT.VALUE}

Reference:
https://www.zabbix.com/documentation/current/en/manual/appendix/macros/supported_by_location

However, event tag macros are not supported, specifically:

{EVENT.TAGS.<tag_name>} 

This prevents passing event tag values to external systems when executing manual actions via URL.

Use case

In many integrations, external systems (for example ServiceNow, Jira, or other ITSM tools) create tickets and store the ticket identifier as an event tag.

Example event tag:

Tag: incident
Value: INC0012345 

Administrators may want to create a manual event action URL that opens the corresponding incident in the external system.

Example desired URL:

https://servicenow.example.com/nav_to.do?uri=incident.do?sysparm_query=number={EVENT.TAGS.incident}

Expected resolved result:

https://servicenow.example.com/nav_to.do?uri=incident.do?sysparm_query=number=INC0012345

Currently this is not possible because {EVENT.TAGS.<tag_name>} cannot be resolved in manual event action URLs.

Benefits

• Easier integration with ITSM systems (ServiceNow, Jira, etc.)
• Enables linking events directly to external incidents
• Improves usability of manual event actions
• Provides consistency with existing event tag macro usage in notifications