Skip to content
← Back to documentation
Technical Reference

ServiceNow

Enterprise IT service management platform for incident, change, and service request management

CategoryProductivity
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect ServiceNow with Flows360

Enterprise IT service management platform for incident, change, and service request management

Use the ServiceNow connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 17 actions and 3 triggers.

Available actions

  • Create Record
  • Update Record
  • Get Record
  • Find Records
  • Delete Record
  • Add Comment or Work Note
  • Resolve or Close Incident
  • Attach File to Record
  • Plus 9 additional declared actions.

Available triggers

  • New Record
  • Updated Record
  • New Comment or Work Note

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: ServiceNow
  • Package: @activepieces/piece-service-now@0.3.0
  • Exact artifact digest: sha256:bba0c21256ff798aad61bb0eb22dafb16c9a90a8d8cbdc675333ec48b53f1ddd
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Record (create_record), Create a new record in a specified table Classification: read.
  • Update Record (update_record), Update an existing record in a specified table Classification: read.
  • Get Record (get_record), Retrieve a specific record by its ID Classification: read.
  • Find Records (find_record), Search for records in a table using a query Classification: read.
  • Delete Record (delete_record), Delete a record from a specified table Classification: read.
  • Add Comment or Work Note (add_comment), Append a customer-visible comment or an internal work note to a record (incident, request, problem, change, etc.) Classification: read.
  • Resolve or Close Incident (resolve_incident), Move an incident to Resolved or Closed with a close code and resolution notes Classification: read.
  • Attach File to Record (attach_file_to_record), Upload and attach a file to a record Classification: read.
  • Find File (find_file), List or download file attachments from a record Classification: read.
  • Delete Attachment (delete_attachment), Delete an attachment by its sys_id Classification: read.
  • Get Catalog Item (get_catalog_item), Retrieve full details of a catalog item including its variable definitions. Use this before "Submit Catalog Request" to discover the variables expected by the item. Classification: read.
  • Submit Catalog Request (submit_catalog_item), Order a catalog item. Submits a service catalog request and returns the resulting request number. Classification: read.
  • Search Knowledge Articles (search_knowledge_articles), Search published knowledge base articles using free text. Requires the Knowledge API plugin to be active. Classification: read.
  • Get Knowledge Article (get_knowledge_article), Retrieve the full content of a knowledge article by sys_id Classification: read.
  • Send Email (send_email), Send an email through your ServiceNow instance using the Email API. Requires the email outbound capability to be configured. Classification: read.
  • Count Records (count_records), Return the number of records in a table that match an optional encoded query (uses the Aggregate API) Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Record, polling.
  • Updated Record, polling.
  • New Comment or Work Note, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objectsNot published
Supported actionsNot published
Triggers3

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Instance URL Required
  • Username Required
  • Password Required · protected credential

Triggers

New Record · Poll

Triggers when a new record is created in a table

Inputs

  • table · string
  • filter · string
Updated Record · Poll

Triggers when a record is updated in a table

Inputs

  • table · string
  • filter · string
New Comment or Work Note · Poll

Triggers when a new comment or work note is added to a record in the selected table

Inputs

  • table · string
  • entry_type · string
  • record_sys_id · string

Setup

Setup

  1. Add the ServiceNow connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Instance URL (instanceUrl), required.
  • Username (username), required.
  • Password (password), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-service-now@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 17 actions and 3 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required ServiceNow connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-service-now@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.