Flashduty Docs
中文EnglishRoadmapAPI官网控制台
中文EnglishRoadmapAPI官网控制台
  1. Webhooks
  • Introduction
  • On-call
    • Getting Started
      • Quick start
      • FAQ
      • Product Comparison
    • Incidents
      • What is an Incident
      • View Incidents
      • Handle Incidents
      • Escalations and Assignments
      • Custom Fields
      • Custom Actions
      • Alert Noise Reduction
      • Past Incidents
      • Outlier Incidents
    • Configure On-call
      • Channels
      • Integrate Alerts
      • Alert Noise Reduction
      • Escalation Rules
      • Label Enrichment
      • Schedules
      • Templates
      • Service Calendars
      • Preferences
      • Alert Routing
      • Silence and Inhibition
      • Filters
      • Notifications
      • Alert Pipeline
    • Advanced Features
      • Referencing Variables
      • Dynamic Assignment
      • Insights
      • War-room
    • Integrations
      • Alerts integration
        • Standard Alert Integration
        • Email Integration
        • Nightingale/FlashCat Integration
        • Prometheus Integration
        • Grafana Integration
        • Zabbix Integration
        • Uptime Kuma Integration
        • Alibaba Cloud ARMS Integration
        • Alibaba Cloud Monitor CM Event Integration
        • Alibaba Cloud Monitor CM Metrics Integration
        • Alibaba Cloud SLS Integration
        • AWS CloudWatch Integration
        • Azure Monitor Integration
        • Baidu Cloud BCM Integration
        • Huawei Cloud CES Integration
        • Influxdata Integration
        • Open Falcon Integration
        • PagerDuty Integration
        • Tencent BlueKing Integration
        • Tencent Cloud CLS Integration
        • Tencent Cloud Monitor CM Integration
        • Tencent Cloud EventBridge
        • OceanBase Integration
        • Graylog Integration
        • Skywalking Integration
        • Sentry Integration
        • Jiankongbao Integration
        • AWS EventBridge Integration
        • Dynatrace Integration
        • Huawei Cloud LTS Integration
        • GCP Integration
        • Splunk Alert Events Integration
        • AppDynamics Alert Integration
        • SolarWinds Alert Events Integration
        • Volcengine CM Alert Events Integration
        • Volcengine CM Event Center Integration
        • Volcengine TLS Integration
        • OpManager Integration
        • Meraki Integration
        • Keep Integration
        • ElastAlert2 Alert Integration
        • StateCloud Alert Events
        • Guance Alert Events
        • Zilliz Alert Events
        • Huawei Cloud APM Alerts
        • zstack integration
        • Monit Alert Integration
        • RUM Alert Integration
      • Change integration
        • Standard Change Event
        • Jira Issue Events
      • IM integration
        • Feishu (Lark) Integration Guide
        • Dingtalk Integration
        • WeCom Integration
        • Slack Integration
        • Microsoft Teams Integration
      • Single Sign-On
        • Authing Integration
        • Keycloak Guide
        • OpenLDAP Guide
      • Webhooks
        • Alert webhook
        • Incident webhook
        • Costom action
        • ServiceNow Sync
        • Jira Sync
      • Other
        • Link Integration
  • RUM
    • Getting Started
      • Introduction
      • Quick start
      • FAQ
    • Applications
      • Applications
      • SDK Integration
      • Advanced Configuration
      • Analysis Dashboard
    • Performance Monitoring
      • Overview
      • Metrics
      • Performance Analysis
      • Performance Optimize
    • Error Tracking
      • Overview
      • Error Reporting
      • Issues
      • Source Mapping
      • Error Grouping
      • Issue States
      • Issue Alerting
    • Session Explorer
      • Overview
      • Data Query
    • Session Replay
      • View Session Replay
      • Overview
      • SDK Configuration
      • Privacy Protection
    • Best Practice
      • Distributed Tracing
    • Others
      • Terminology
      • Data Collection
      • Data Security
  • Platform
    • Teams and Members
    • Permissions
    • Single Sign-On
  • Terms
    • Terms of Service
    • User Agreement/Privary Policy
    • SLA
    • Data Security
  1. Webhooks

ServiceNow Sync

Through ServiceNow sync webhook, Flashduty incidents are associated and synchronized with ServiceNow Incidents to achieve integration between Flashduty and ServiceNow.

In ServiceNow#

Create User#

Create a user to connect to the ServiceNow instance for Incident sync and updates. Skip this step if you already have an available user.
1.
Log in to the ServiceNow instance console, select ALL, enter USERS and select Organization-Users.
2.
Click New to create a new user.
3.
In the edit page, enter flashduty in the User ID field.
4.
Keep Password needs reset, Web service access only, and Internal Integration User unchecked.
5.
Submit and save.
2025-09-24-16-19-47

Configure User#

User Role Description
itil: The main usage scope of this role in Flashduty is limited to field retrieval in ServiceNow Incident Table and does not involve any other operations.
personalize_dictionary: This role in Flashduty is primarily used only for field retrieval from ServiceNow Incident Tables, and does not involve any other operations.
For more information about the permission scope of these two roles, please refer to the ServiceNow official documentation
1.
On the user list page, find the newly created flashduty user and go to the configuration page.
2.
In the edit page, click Set Password to set a password.
3.
Click Roles to add personalize_dictionary and itil roles (If custom field mapping configuration is not required, the personalize_dictionary permission does not need to be retained).
4.
Click Update to update the configuration.
2025-09-24-16-29-05
2025-09-24-16-29-58

In Flashduty#

Configure Integration#

Enter the username/password and instance name configured above into the integration information on the left and click Next to configure.
Integration Name: Define a name for the current integration.
Management Team: When a management team is selected, only team members and tenant administrators can edit this integration.
Channel: Select the channel where this integration takes effect.
Sync Direction:
To_ServiceNow: Sync Flashduty incidents to ServiceNow.
From_ServiceNow: Sync ServiceNow Incidents to Flashduty.
Two-way: Bidirectional sync between Flashduty and ServiceNow.
Trigger Mode:
Auto Trigger: Requires configuration of corresponding conditions, Flashduty will automatically sync incidents that meet the conditions to ServiceNow.
Manual Trigger: Requires manual triggering of ServiceNow sync in the More Actions section of the incident details page (the integration configuration name is the trigger name).
Severity Mapping:
ServiceNow's Priority is determined by the combined values of Impact and Urgency, so you can refer to ServiceNow's Priority Lookup Rules for configuration.
Only when the Urgency of a ServiceNow Incident changes will it trigger an update to the Flashduty incident severity.
Since Flashduty cannot obtain ServiceNow's Impact and Urgency lists while following the principle of least privilege, only default values are provided. If you need to customize the mapping relationship, please contact technical support.
Custom Field Mapping: You can map tags or custom fields from incidents to corresponding text fields in ServiceNow tickets, enabling automatic information filling. This feature supports synchronizing common contextual information (such as service name, instance address, metric name, etc.) to ServiceNow for easier subsequent troubleshooting and tracking.
Only supports target fields of single-line text or multi-line text types.
Supports extracting values from incident tags (such as service, instance) or custom attributes.
If the source field is empty, the target field will also remain empty and will not overwrite existing content.
Mapping configurations are managed centrally in integration settings, eliminating the need for manual entry each time.

In ServiceNow#

When sync direction is set to From_ServiceNow or Two-way, additional configuration is required in ServiceNow to sync ServiceNow Incidents to Flashduty. When syncing to Flashduty, there are two methods available, choose based on your actual needs.

Manual Sync#

This method relies on ServiceNow's UI Action and Script Include configuration. The effect achieved by following the steps below: When creating or updating an Incident, you can see a button to send sync requests in the function area. Triggering this button will sync the current Incident content to Flashduty. Note that if the request fails when triggered, please retry (retry interval should be greater than 10 seconds).

Configure UI Action#

1.
Log in to the ServiceNow instance console, select ALL, enter UI Actions and select System Definition-UI Actions.
2.
Click New to create a new Action.
3.
Enter Send To Flashduty in Name, select Incident in Table.
4.
Keep Form button, Active, Show insert, Show update, Client, List v2/3 Compatible checked.
5.
Enter onClick(); in Onclick.
6.
Enter the following in Script:
7.
Submit and save.

Configure Script Include#

1.
Log in to the ServiceNow instance console, select ALL, enter Script Includes and select System Definition-Script Includes.
2.
Click New to create a new Script Include.
3.
Enter IncidentWebhookHelper in Name, select All application scopes in Accessible from.
4.
Keep Client callable and Active checked.
5.
Enter the following content in Script, where you need to add the integration push URL in request.setEndpoint:
Note: The body configures default receiving fields. If you have custom fields that need to be synced to Flashduty, you need to manually add content to the body. For example, if you want to add a field named: test_001 (this field name can be obtained when adding custom fields in the integration configuration, do not use the field name displayed in the ServiceNow Incident form), then you need to add to the body: test_001: current.getDisplayValue("test_001").
6.
Submit and save.
7.
Return to the Script Includes list and continue creating.
8.
Click New to create a new Script Include.
9.
Enter IncidentWebhookHelperAjax in Name, select All application scopes in Accessible from.
10.
Keep Client callable and Active checked.
11.
Enter the following content in Script:
12.
Submit and save.

Auto Sync#

This method relies on ServiceNow's Business Rules configuration. Using this method, you can automatically sync Incidents to Flashduty when there are new or update events.

Configure Business Rules#

1.
Log in to the ServiceNow instance console, select ALL, enter Business Rules and select System Definition-Business Rules.
2.
Click New to create a new Business Rule.
3.
Enter Send To Flashduty in Name, select Incident in Table.
4.
Keep Advanced and Active checked.
5.
In the When to run section, select async in When, keep Insert and Upsert checked, configure others as needed.
6.
In the Advanced section, enter the following content in Script, where you need to add the integration push URL in endpoint:
Note: The body configures default receiving fields. If you have custom fields that need to be synced to Flashduty, you need to manually add content to the body. For example, if you want to add a field named: test_001 (this field name can be obtained when adding custom fields in the integration configuration, do not use the field name displayed in the ServiceNow Incident form), then you need to add to the body: test_001: current.getDisplayValue("test_001").
7.
Submit and save.

Sync Information#

Form Fields#

ServiceNowFlashdutyNotes
Short_descriptionTitleTitle
DescriptionDescriptionDescription
Additional commentsCommentsComments
StateProgressProgress
UrgencySeveritySeverity
OthersCustom FieldsCustom Fields

Status Mapping#

ServiceNowFlashdutyNotes
NewTriggerTrigger
In ProgressProcessingProcessing
On HoldSnoozedDefault snooze 2 hours
ResolvedCLosedCLosed
ClosedCLosedCLosed
CanceledCLosedCLosed

Priority Mapping#

Only when ServiceNow's Urgency value changes will it affect Flashduty's Severity
ServiceNowFlashdutyNotes
LowInfoInfo
MediumWarningWarning
HighCriticalCritical

QA#

Can the UserID be customized when creating a new ServiceNow user?
Yes, it can be customized. The documentation uses "flashduty" as the UserID to better identify that this user is used for Incident synchronization.
Getting 401 error when configuring integration
A 401 error is generally caused by an incorrect password. Please check if the password is correct, or reset a new password (when setting the password, do not check the "Password needs reset" option).

添加官方技术支持微信

在这里,获得使用上的任何帮助,快速上手FlashDuty

微信扫码交流
修改于 2025-10-03 02:58:44
上一页
Costom action
下一页
Jira Sync
Built with