Authentication
This provider requires authentication.- service_now_base_url: The base URL of the ServiceNow instance (required: True, sensitive: False)
- username: The username of the ServiceNow user (required: True, sensitive: False)
- password: The password of the ServiceNow user (required: True, sensitive: True)
- client_id: The client ID to use OAuth 2.0 based authentication (required: False, sensitive: False)
- client_secret: The client secret to use OAuth 2.0 based authentication (required: False, sensitive: True)
- ticket_creation_url: URL for creating new tickets (required: False, sensitive: False)
- itil: The user can read/write tickets from the table (mandatory) (Documentation)
In workflows
This provider can be used in workflows. As “step” to query data, example:- blogpost.yml
- clickhouse_multiquery.yml
- create_service_now_ticket_upon_alerts.yml
- update_service_now_tickets_status.yml
Topology
This provider pulls topology to Keep. It could be used in correlations and mapping, and as a context for alerts and incidents.Provider Methods
The provider exposes the following Provider Methods. They are available in the AI Assistant.- get_incidents Fetch all incidents from ServiceNow (view, scopes: itil)
-
get_incident_activities Get work notes and comments from a ServiceNow incident (view, scopes: itil)
incident_id: The incident number (e.g. INC0010001) or sys_id.limit: Maximum number of activity records to return.
-
add_incident_activity Add a work note or comment to a ServiceNow incident (action, scopes: itil)
incident_id: The incident number (e.g. INC0010001) or sys_id.content: The text content to add.activity_type: Either ‘work_notes’ or ‘comments’. Defaults to ‘work_notes’.
Connecting with the Provider
- Ensure that the ServiceNow instance is accessible via API.
- Provide the necessary API credentials (
instance_urlandapi_token) in the provider configuration.
Additional
KEEP_SERVICENOW_PROVIDER_SKIP_SCOPE_VALIDATIONenvirnomental variable in the backend allows to bypass scope validation.

