Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a ServiceNow location.

ServiceNow

Create a ServiceNow Destination

1. Click the + icon on the Nexset that will be sent to the ServiceNow destination, and select the Send to Destination option from the menu.

2. Select the ServiceNow connector from the list of available destination connectors. Then, select the credential that will be used to connect to your ServiceNow instance, and click Next; or, create a new ServiceNow credential for use in this flow.

3. In Nexla, ServiceNow destinations can be created using pre-built endpoint templates, which expedite destination setup for common ServiceNow endpoints. Each template is designed specifically for the corresponding ServiceNow endpoint, making destination configuration easy and efficient.
   • To configure this destination using a template, follow the instructions in Configure Using a Template.

   ServiceNow destinations can also be configured manually, allowing you to send data to ServiceNow endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
   • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common ServiceNow endpoints. Each template is designed specifically for the corresponding ServiceNow endpoint, making destination setup easy and efficient.

• To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

  Create new Incident

  This endpoint template allows you to create a new incident in your ServiceNow instance using records from a Nexset. This endpoint inserts a new record into the incident table in the default namespace (now) using the latest version of the ServiceNow API. Use the custom REST configuration to access a different namespace or version.

  • This endpoint sends data as JSON in the request body to create a new incident in your ServiceNow instance. Each record from your Nexset will be sent as a separate API request to create a new incident. The request body should contain the incident data in the format required by the ServiceNow API, including incident details, description, priority, and other incident properties.

  This endpoint sends data as JSON in the request body to create a new incident in your ServiceNow instance. Each record from your Nexset will be sent as a separate API request to create a new incident. The request body should contain the incident data in the format required by the ServiceNow API, including incident details, description, priority, assignment, and other incident properties.

  This endpoint inserts a new record into the incident table in the default namespace (now) using the latest version of the ServiceNow API. Use the custom REST configuration to access a different namespace or version. The incident structure must match the ServiceNow API's expected format.

  For detailed information about incident creation, request body formats, and available incident properties, see the ServiceNow REST API documentation.

  Create new CSM Case

  This endpoint template allows you to create a new CSM (Customer Service Management) case in your ServiceNow instance using records from a Nexset. This endpoint inserts a new record in the default namespace using the latest version of the ServiceNow API. Use the custom REST configuration to access a different namespace or version.

  • This endpoint sends data as JSON in the request body to create a new CSM case in your ServiceNow instance. Each record from your Nexset will be sent as a separate API request to create a new case. The request body should contain the case data in the format required by the ServiceNow API, including case details, description, priority, and other case properties.

  This endpoint sends data as JSON in the request body to create a new CSM case in your ServiceNow instance. Each record from your Nexset will be sent as a separate API request to create a new case. The request body should contain the case data in the format required by the ServiceNow API, including case details, description, priority, assignment, and other case properties.

  This endpoint inserts a new record in the default namespace using the latest version of the ServiceNow API. Use the custom REST configuration to access a different namespace or version. The case structure must match the ServiceNow API's expected format.

  For detailed information about CSM case creation, request body formats, and available case properties, see the ServiceNow REST API documentation.

  Create new Record in Table

  This endpoint template allows you to create a new record in a selected table in your ServiceNow instance using records from a Nexset. This endpoint inserts a new record in the default namespace (now) using the latest version of the ServiceNow API. Use the custom REST configuration to access a different namespace or version.

  • Enter the Table Name in the Table Name (select or type) field. This should be the name of the ServiceNow table into which you want to insert records (e.g., incident, sys_user, cmdb_ci). The table name determines which table will receive the new records. You can find available table names by using the "List Tables" data source endpoint.

  This endpoint sends data as JSON in the request body to create a new record in a selected table in your ServiceNow instance. Each record from your Nexset will be sent as a separate API request to create a new record. The request body should contain the record data in the format required by the ServiceNow API for the specific table.

  This endpoint inserts a new record in the default namespace (now) using the latest version of the ServiceNow API. Use the custom REST configuration to access a different namespace or version. The table name can be found by using the "List Tables" data source endpoint or in your ServiceNow instance documentation. The record structure must match the ServiceNow API's expected format for the specific table.

  For detailed information about record creation, request body formats, and available table properties, see the ServiceNow REST API documentation.

Configure Manually

ServiceNow destinations can be manually configured to send data to any valid ServiceNow API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the ServiceNow API after each call to a new Nexla webhook data source.

API Method

1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

2. Select the API method that will be used for calls to the ServiceNow API from the Method pulldown menu. ServiceNow API typically uses POST method for creating resources.

Data Format

3. Select the format in which the Nexset data will be sent to the ServiceNow API from the Content Format pulldown menu. ServiceNow API expects JSON format for all requests.

API Endpoint URL

4. Enter the URL of the ServiceNow API endpoint to which data will be sent in the URL field. This should be the complete URL to your ServiceNow endpoint, using your Instance URL from the credential (e.g., {instance_url}/api/now/table/{table_name}, {instance_url}/api/now/v2/table/{table_name}). Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The ServiceNow API endpoint URL should use your Instance URL from the credential and point to the endpoint where you want to create records. The endpoint URL should include the appropriate API path (e.g., /api/now/table/ for table endpoints). You can test the endpoint using the Test button after configuring the URL.

Request Body

5. Configure the request body that will be sent to the ServiceNow API. The request body should contain the resource data formatted as JSON, with field names matching the ServiceNow API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the ServiceNow API's expected format for the specific table or endpoint you're using. ServiceNow API uses specific structures for different tables (incidents, cases, custom tables, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the ServiceNow REST API documentation.

Save the Destination

6. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.