ServiceNow Field Mapping
Field mapping allows for fields from FireHydrant to be mapped with fields in ServiceNow tickets. ServiceNow is complex and highly configurable, so sometimes custom mappings need to be made between FireHydrant's incident fields and ServiceNow's ticket fields.
Ticket types with custom fields need to be mapped to FireHydrant incident fields.
Prerequisites
- You will need to have installed ServiceNow integration.
Default Mappings
By default before any custom field mapping, the following items will be synchronized between FireHydrant and ServiceNow automatically or based on different tabs/settings:
- Title/Summary - The name of the incident or follow-up will automatically sync with the summary (short description) in ServiceNow
- Description - The description of the incident or follow-up ticket will automatically sync with the same (long description) in ServiceNow
- Status/Milestone - This is mapped according to the Incident Tickets and Follow Ups tabs
- Assignee - FireHydrant will automatically find matching user(s) with the same email address between both tools to automatically assign a user to the ticket in ServiceNow.
The above mappings are bi-directional, so changes in one tool will propagate and synchronize changes in the other tool.
When do I need to configure custom mappings for fields?
There are multiple scenarios where you must configure field mappings for FireHydrant to be able to create tickets in your project(s):
- When you have custom, required fields - If a specific project has any required fields that are not set automatically, especially if they are custom issue fields, then you'll need to configure them in FireHydrant so we know what to set for those fields
How to configure field mapping
Outbound Field Mapping (FireHydrant to ServiceNow)

ServiceNow outbound field mapping
- Navigate to the ServiceNow settings page and click on the project you'd like to configure, then selet the Field Mapping tab.
- Click '+ Add mapping' to create a new mapping.
- A drawer will come out on the right where you can select between two choices:
- Basic mapping allows you to always set fields in ServiceNow to the same values.
- Advanced mapping allows conditional logic to map different fields to different values in ServiceNow based on various parameters within FireHydrant.
Note:
Field mappings for a project and its tickets are evaluated and applied upon every incident update. For example, if you have a condition to "set ServiceNow ticket Severity field to
SEV1
whenever the incident is isSEV1
, otherwise default toSEV3
," this will evaluate each time you make updates on the incident so that if the severity is escalated/de-escalated, the field in ServiceNow will change accordingly.
- You can select a ServiceNow field once you've selected between basic vs. advanced mapping.
- If Basic, you can set the field's value, and this will apply each time you create the ticket and whenever any detail on the incident is updated.
- If Advanced, you can select conditions and values that should apply when those conditions are met, along with an Else default value if no conditions are met.
- For values, you will see the following:
- You can choose between preset FireHydrant parameters and "Use a custom value." If you select Custom Value, you can input any value you'd like, and the field will also support Template Variables. Note that what you can insert as a custom value will depend on the field's settings in ServiceNow.
- Once this field's mapping has been configured to your liking, click Save to persist. Rinse and repeat these steps for all fields you'd like to map.
Advanced mapping conditions
The following conditions are available for configuring advanced if/else if/else rules in ServiceNow Field mapping:
- Current severity - Current incident's severity
- Current milestone - Current incident's milestone
- Incident name
- Incident number
- Incident description
- Ticket priority - Priority of the Follow-up created on FireHydrant (not Incident)
- Ticket tags - Tags of the Follow-up created on FireHydrant (not Incident)
- Incident impacted infrastructure - Which Service Catalog components are impacted on an incident
- [Custom Fields] - Any Incident Custom Fields configured by users
- Entered [milestone] at - If timestamp for the specified milestone exists and has been filled in
Inbound Field Mapping (ServiceNow to FireHydrant)

ServiceNow inbound field mapping
Inbound field mapping allows you to control how ServiceNow ticket fields map back to FireHydrant incident fields. This is especially useful when you have custom fields in ServiceNow that need to be mapped to a specific field in FireHydrant
To configure inbound field mapping:
- Navigate to your integrations page, and select the ServiceNow integration
- Click on the project you want to set up inbound field mapping for
- Navigate to the Inbound Field Mapping tab
- Click the '+ Add mapping' button
- In the drawer that appears:
- Select the FireHydrant field you want to create the inbound field mapping for
- Select the corresponding ServiceNow field
- Click Save to persist your changes
Important notes about inbound field mapping:
- Inbound field mapping is only available for basic mapping and not advanced mapping
- Repeat the process to add additional field mappings as needed
- Test your inbound field mapping via your Runbook step
Common ServiceNow field mappings
Impact and Urgency matrix
ServiceNow uses a matrix for impact and urgency to visually represent the priority of an incident or issue by considering both the severity of its potential impact on business operations ("impact") and the time sensitivity of resolving it ("urgency"), allowing for a more nuanced assessment of how quickly a problem needs to be addressed based on its potential consequences.
You can set up field mapping in FireHydrant to match your ServiceNow impact and urgency matrix, Using custom fields in FireHydrant.
- Create Impact and Urgency custom fields
- In the FireHydrant UI navigation, select Settings and then Incident settings. On the top right, click "+ Add custom field".
- Display name (required): Set the display name to be either Impact or Urgency
- Help text: A helpful description for completing the field that appears in tooltips in the web and Slack for your responders
- Type (required): set this to be the
Multi-select
type.- Enter the following values for
1
,2
, and3
- Enter the following values for
- Field Settings: Specifies whether the field is required and/or should be immediately visible on the declaration form for users.
- In the FireHydrant UI navigation, select Settings and then Incident settings. On the top right, click "+ Add custom field".
- Set up Impact and Urgency field mapping
- Navigate to the ServiceNow settings page and click on the project you'd like to configure, then the Field Mapping tab.
- Click '+ Add mapping' to create a new mapping.
- A drawer will come out on the right; select the Basic Mapping option
- Select either Impact or Urgency from the ServiceNow dropdown
- Map that field to the custom field set up from the FireHydrant dropdown
- Custom Fields in FireHydrant will be prepended with "Incident". Impact will display as Incident Impact in the dropdown.

Mapping Impact and Urgency using Custom Fields
Impacted Service
Note:
This requires for you to have set up the ServiceNow integration in FireHydrant to link with the SNOW CMDB table. See ServiceNow instructions or ServiceNow CMDB for more information.
It's typical for customers to use the SNOW CMDB to track infrastructure and services. FireHydrant's Catalog can synchronize with the ServiceNow CMDB and also automatically mark the correct services as impacted on an incident.

Inbound field mapping
- Configure inbound mapping - This enables choosing an impacted service on the ServiceNow incident and automatically marking the same linked service as impacted in FireHydrant.
- Navigate to Settings > Integrations list > ServiceNow and select the project you want to map.
- In the project settings, go to the Inbound Field Mapping tab and add click "+ Add mapping."
- In the drawer, choose Incident impacted infrastructure for the FireHydrant field and Service for the ServiceNow field. Then click "Save."

Outbound field mapping
- Configure outbound mapping - This enables choosing an impacted service in a FireHydrant incident and automatically marking the same linked service as impacted in ServiceNow
- Navigate to Settings > Integrations list > ServiceNow and select the project you want to map.
- In the project settings, go to the Outbound Field Mapping tab and add click "+ Add mapping."
- In the drawer, choose Service for the ServiceNow field and Incident impacted infrastructure for the FireHydrant field. Then click "Save."
Updated 3 days ago