Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To connect MuleSoft to ServiceNow, add the ServiceNow Connector to a Mule project, place an operation in a flow, configure a reusable global connection, and test it. The connector documents Basic Authentication and OAuth 2.0 Authorization Code; OAuth has narrower runtime requirements and does not support connector metadata. Custom and extended parent tables may also need web-service and configuration access enabled in ServiceNow.

What the ServiceNow Connector does

MuleSoft’s ServiceNow Connector links Mule applications with ServiceNow for work such as IT service management (ITSM) synchronization, cross-functional business-process integration, and creating or retrieving records. MuleSoft also describes integrations involving custom tables and operations supplied by installed plugins. Examples include bidirectional worker synchronization between Workday and ServiceNow, service-request migration, employee aggregation, and service-worker migration; these are patterns to adapt to your instance, not ready-made guarantees. See the ServiceNow Connector 6.18 overview.

Check runtime and release compatibility first

The general compatibility entry in MuleSoft’s ServiceNow Connector 6.18 release notes lists Mule 4.1.1 and later, OpenJDK 8, 11, and 17, and ServiceNow API generations through Australia. The release notes identify version 6.18.5 as dated August 10, 2026. Check the connector release notes for the precise release and target API before upgrading or choosing a runtime.

Do not apply the general Mule baseline to every authentication mode: MuleSoft documents OAuth authorization-code support only with Mule 4.1.5 or 4.2.1 and later. Confirm that requirement for your chosen connector release in the connector overview.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Choose an authentication method

Consideration Basic Authentication OAuth 2.0 Authorization Code
Setup Configure the ServiceNow instance or service address and account credentials in the connection fields. Register an application and configure its details, authorization and token endpoints, listener, callback path, and authorize path; run the authorization flow and grant access in ServiceNow.
Runtime support Use the general connector compatibility for the selected release. MuleSoft specifies Mule 4.1.5 or 4.2.1 and later; verify the release notes.
Metadata No metadata limitation is noted in the cited overview. Connector metadata does not work with this authentication type.
Deployment topology Configure the connection fields required by the selected transport. Callback and external callback URL settings may need to reflect a proxy or indirect access path.

Both connection types are documented for ServiceNow Connector 6.18. Refer to MuleSoft’s overview and reference for the applicable fields. Keep credentials and other sensitive values in property placeholders where appropriate, as described in the Anypoint Studio configuration guide.

Configure and test the connector in Anypoint Studio

  1. Confirm prerequisites. Have access to the target ServiceNow instance and Anypoint Platform, and be familiar with Mule flows and global elements. Check the selected connector release’s runtime compatibility before starting.
  2. Create or open a Mule project. Add ServiceNow Connector to the project. Studio adds its namespace and schema location to the XML and the required dependency to the project’s pom.xml.
  3. Add an operation to a flow. Select ServiceNow in the Mule Palette and place the required operation after the flow source.
  4. Create a global configuration. Choose Basic Authentication or OAuth 2.0 Authorization Code and fill the fields required for that connection type and transport.
  5. Configure the connection details. For Basic Authentication, provide the ServiceNow instance or service address and account credentials. For OAuth, supply the instance, registered application details, authorization and token endpoints, HTTP listener configuration, callback path, and authorize path.
  6. Test the connection. Use Test Connection in the global configuration before expanding the flow.
  7. Complete OAuth authorization if selected. Start the Mule application, initiate the OAuth authorization flow, and grant access in ServiceNow. Adjust callback settings for a proxy or indirect URL where applicable.
  8. Check logs if something fails. In Studio, review the app output in the console. A command-line Mule application logs to the OS console and, by default, to MULE_HOME/logs/<app-name>.log, unless logging has been customized.

MuleSoft’s Studio guide describes the setup sequence, connection test, OAuth flow, and logging locations.

Choose an operation and configure table access

The ServiceNow Connector 6.18 reference lists Invoke and Unauthorize. Invoke is the default operation for ServiceNow SOAP invocations; select the relevant Service and Operation in its configuration. For get and getRecords, the reference provides an option to return reference fields as sys_ids, display values, or both. For update, an option controls whether a specific field can be cleared with a null or empty value. See the operation reference for the fields and options.

Custom or extended parent tables

If a custom table or an extended parent table is not available as expected, check its definition in ServiceNow. MuleSoft’s reference says to enable Allow access to this table via web services and Allow configuration options. Also check whether the required operation depends on an installed plugin before changing the Mule flow.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Use the connector for the integration you need

MuleSoft’s examples show the connector used to synchronize ITSM data across SaaS and on-premises systems, connect functions such as HR and procurement, and create or retrieve records. Worker synchronization, service-request migration, employee aggregation, and service-worker migration illustrate possible flow designs; confirm that the relevant tables, operations, and plugins exist in your ServiceNow instance before relying on a pattern.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.