Response field templates
Response field templates let you reuse text in the fields of an integration method. Create a template once, then use Fill from template while adding or editing an Action Rule or running a response from an incident. The selected values are copied into the form, where you can edit them before saving or running the action.
A field template belongs to one response integration and one method. It fills only the text fields included in the template. You still need to complete any other required fields in the action form.
Create a template
- Open Settings > Responses > Template Management and select Add.
- Enter a name and choose a response type. E-mail and SMS remain available alongside response integrations that support field templates.
- For a response integration, select a method. Enter text in at least one of the displayed fields. Type
$to choose an incident or alert field when the field picker is available. - Select Save. The template appears in Template Management with its response type. You can edit or delete it there.
For example, choose Jira Service Management and create_customer_request to create a template for Summary and Description. A value such as Alert: $GET['TriggeredAlert.Alert.Info'] keeps the field reference for the action to resolve when it runs. Jira Summary and Description are single-line fields, so enter each value on one line.
Use a template in an Action Rule
Open Settings > Alerts & Behaviors > Action Rules. Add a rule or edit an existing one, then choose a configured response integration and a method. If a template exists for that integration and method, Fill from template appears above the method fields. Select a template, review the filled values, complete the remaining required fields, and save the rule. You can change the copied text before saving.
Use a template from an incident
Open an incident and use its response action button to choose a configured integration and method. When a matching template exists, select it from Fill from template. Review or edit the copied values, complete any remaining fields, and submit the response.
Supported response methods
The following methods offer field templates when they contain eligible text fields:
- Ticketing: Jira Service Management
create_customer_request; GLPI and MotaData ServiceOPScreate_ticket. - Logsign actions: Incident
add_task,add_decision, andclose; Commentcomment. - Messages: Microsoft Teams
send_message_in_a_channelandsend_message_in_a_chat; Slack, Telegram, Discord, and Google Chatsend_message; Webexsend_message_to_roomandsend_message_to_person; ZohoCliqpost_to_chatandpost_to_channel. - HTTP responses: Webhook and Restful/JSON API
postandput.
The available fields depend on the selected method. If Fill from template is absent, check that a template exists for the exact integration and method. ServiceDesk Plus and HaloITSM methods do not offer field templates. Playbook response forms do not currently show this picker.
How template changes affect actions
Choosing a field template copies its values into the current form. Saved Action Rules retain those values. Editing or deleting the template later does not update rules that used it. To use revised values in an existing rule, edit the rule and select the template again. Field references such as $GET['TriggeredAlert.Alert.Info'] are resolved when the action runs.
For integration setup and action basics, see Jira Service Management Response Integration via API, Understanding of Fully Automatic Response Technology with Action Rule, and Taking Action to an Incident.