.png)
ServiceNow Field Service Management Integration Guide
Connect ServiceNow Field Service Management with enterprise applications through REST and SOAP APIs, outbound callbacks, imports, attachments, and orchestrated Martini workflows.
ServiceNow Field Service Management integration options at a glance
ServiceNow Field Service Management primarily integrates through the ServiceNow platform REST API, including Table API, attachment, import, and related API families. SOAP services remain available for existing enterprise environments, while outbound REST messages, business rules, Flow Designer, and scripted logic can provide configured callbacks for selected FSM events. Import Sets, Transform Maps, batch requests, and asynchronous processing support larger data loads. OAuth 2.0, Basic Authentication, mutual TLS, and other configured authentication options may be available by instance and API. Martini can consume these interfaces, expose authenticated endpoints for callbacks, orchestrate workflows, transform related objects, and manage retries and checkpoints.
| Integration point | Supported by ServiceNow Field Service Management? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | The Table API and other ServiceNow REST APIs can query, create, update, and delete accessible FSM records, including Work Orders, Work Order Tasks, users, locations, and assets. | Martini can consume ServiceNow REST APIs, generate reusable integration assets from API definitions where applicable, map payloads, expose API façades, and orchestrate multi-step workflows. |
| SOAP APIs | Yes | ServiceNow SOAP web services and scripted SOAP services support existing enterprise applications that require SOAP contracts. | Martini can consume SOAP services and transform XML responses or requests into canonical models and downstream payloads. |
| Webhooks / outbound callbacks | Limited | Outbound REST messages, business rules, Flow Designer, IntegrationHub, notifications, or scripted logic can send requests for configured FSM events and conditions. | Martini can expose an authenticated REST endpoint, validate callback payloads, trigger workflows, and apply idempotency and retry handling. Coverage is event-specific rather than universal. |
| Bulk / async / batch APIs | Limited | Import Set APIs, Transform Maps, REST batch patterns, and asynchronous processing support initial loads, scheduled synchronization, and higher-volume updates. | Martini can partition data, submit batches or imports, monitor responses, reconcile rejected rows, and persist checkpoints for restartable processing. |
| File / attachment APIs | Yes | Attachment operations support photographs, technician reports, inspection files, invoices, permits, and service-completion evidence associated with ServiceNow records. | Martini can retrieve or upload binary content separately from JSON, transform metadata, associate files with target records, and prevent duplicate transfers. |
| Import and export APIs | Yes | Import Sets and Transform Maps load external data into ServiceNow tables and apply configured transformation logic for controlled bulk processing. | Martini can prepare import payloads, invoke import endpoints, map source data, inspect transform errors, and reconcile completion status. |
| Authentication | Yes | OAuth 2.0, Basic Authentication, mutual TLS, certificate-based authentication, and other token-based mechanisms may be available depending on the instance, API, and security policy. | Martini can keep environment-specific credentials in secrets, configure authenticated API consumption, and expose protected endpoints for ServiceNow callbacks. |
| Database access | No | Direct access to the underlying ServiceNow SaaS database is not a normal customer integration method. | Martini should use ServiceNow APIs, imports, approved exports, or reporting interfaces rather than direct database connectivity. |
How ServiceNow Field Service Management exposes data and business events
ServiceNow REST APIs
ServiceNow's platform REST APIs, including the Table API and related API families, provide the primary way to access and modify FSM tables. Exact tables, fields, ACLs, and business behavior depend on the instance release, installed products, scope, and customization.
Martini implementation pattern
Martini implementation pattern: Martini consumes the relevant REST endpoints in workflows, applies encoded queries and pagination, maps ServiceNow objects to a canonical model, and writes to target systems or exposes a controlled API façade. A versioned Scripted REST API may be preferable when the underlying table model should not be exposed as a long-term contract.
Implementation sequence
ServiceNow SOAP APIs
ServiceNow supports SOAP web services and scripted SOAP services for existing consumers that require XML-based contracts. REST is generally preferred for new integrations.
Martini implementation pattern
Martini implementation pattern: Martini consumes the required SOAP service, transforms XML into the integration's canonical model, applies validation and business rules, and routes the result to ServiceNow or another enterprise system.
Implementation sequence
ServiceNow outbound callbacks
ServiceNow can initiate outbound REST requests through configured outbound REST messages, business rules, Flow Designer, IntegrationHub, notifications, or scripted logic. These are selected-event callbacks rather than universal webhook coverage.
Martini implementation pattern
Martini implementation pattern: Martini exposes a protected REST endpoint, validates the event identifier and ServiceNow sys_id, retrieves current data when the notification is incomplete, and launches an asynchronous workflow with duplicate detection.
Implementation sequence
ServiceNow import and batch processing
Import Set APIs, Transform Maps, REST batch patterns, and asynchronous processing support controlled bulk loads and higher-volume synchronization. Transform errors and completion status must be reconciled.
Martini implementation pattern
Martini implementation pattern: Martini partitions source data, submits import or batch requests, tracks job and row outcomes, and produces reconciliation results for rejected or duplicate data.
Implementation sequence
ServiceNow attachment APIs
ServiceNow attachment operations support files associated with FSM records, including photographs, technician reports, inspection evidence, and customer documents.
Martini implementation pattern
Martini implementation pattern: Martini synchronizes record metadata separately from binary content, retrieves or uploads attachments, applies file and security rules, and records source attachment identifiers to make transfers idempotent.
Implementation sequence
Common ServiceNow Field Service Management integration patterns
Pattern 1: Synchronize Work Orders and Work Order Tasks
When to use this pattern
Use this pattern when ServiceNow FSM and an external field-service, customer-service, ERP, or operations application need aligned work and task data. It supports scheduled incremental retrieval and controlled relationship ordering.
Integration direction
Example Mapping
| ServiceNow Field Service Management Field | Canonical Field | Target Field |
|---|---|---|
| sys_id | sourceWorkId | External Work ID |
| number | workOrderNumber | Case or service order number |
| short_description | workSummary | Subject |
| state | workStatus | Status |
Martini implementation pattern
A scheduled Martini workflow queries changed Work Orders and Work Order Tasks using sys_updated_on with an overlap window, resolves Locations, Assets, and assignments, maps state values, and upserts the target records. It stores source and target identifiers, retries transient failures, and routes validation or ACL errors to an exception path.
Martini capabilities used
- workflows
- API consumption
- scheduling
- data mapping
- business rules
- error handling
Pattern 2: Create field work from a service request
When to use this pattern
Use this pattern when a CRM or customer application needs to request field execution without writing directly to ServiceNow tables. Martini centralizes validation, relationship creation, and response handling.
Integration direction
Example Mapping
| ServiceNow Field Service Management Field | Canonical Field | Target Field |
|---|---|---|
| customerId | customerReference | Account or Contact reference |
| serviceAddress | location | Location |
| equipmentId | assetReference | Asset |
| requestedWork | workDescription | short_description |
Martini implementation pattern
A Martini API receives the request, validates required fields and authorization, resolves ServiceNow references, creates the Work Order, creates dependent Work Order Tasks, and returns the ServiceNow sys_id and number. The workflow uses idempotency keys and compensating or exception handling when child creation fails.
Martini capabilities used
- API exposure
- workflows
- data mapping
- business rules
- API consumption
- error handling
Pattern 3: Propagate FSM status notifications
When to use this pattern
Use this pattern when selected Work Order or Work Order Task transitions must update customer-facing, financial, collaboration, or operational systems quickly.
Integration direction
Example Mapping
| ServiceNow Field Service Management Field | Canonical Field | Target Field |
|---|---|---|
| sys_id | serviceTaskId | External task identifier |
| state | executionStatus | Message status |
| assigned_to | assignedTechnician | Notification recipient |
| sys_updated_on | changedAt | Event timestamp |
Martini implementation pattern
ServiceNow sends configured outbound REST callbacks to a Martini endpoint. Martini authenticates and validates the event, deduplicates by event and sys_id, optionally retrieves the current object, applies routing rules, and updates the target or sends a notification. Failed deliveries are logged and retried only when safe.
Martini capabilities used
- API exposure
- webhook consumption
- workflows
- business rules
- idempotency
- monitoring
Pattern 4: Distribute technician completion evidence
When to use this pattern
Use this pattern when completed service work, notes, photographs, inspection reports, or signatures must reach billing, document, customer, or asset-management systems.
Integration direction
Example Mapping
| ServiceNow Field Service Management Field | Canonical Field | Target Field |
|---|---|---|
| work_order | serviceOrderReference | Service order |
| work_notes | completionNotes | Service notes |
| attachment.sys_id | sourceFileId | External document key |
| completed_at | completionDate | Service completion date |
Martini implementation pattern
A callback or scheduled workflow identifies completed Work Order Tasks, retrieves related record data and attachments, validates file metadata, maps completion and cost information, and delivers files and metadata to the target. Checksums and source identifiers prevent duplicate files, while rejected records enter an operational exception flow.
Martini capabilities used
- workflows
- API consumption
- file handling
- data mapping
- business rules
- error handling
Applications commonly integrated with ServiceNow Field Service Management
ServiceNow FSM can participate in broader service, finance, workforce, collaboration, and field-operations landscapes. The exact ownership model depends on the customer's configuration, but Martini can coordinate these exchanges without requiring every application to understand ServiceNow table structures.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize accounts, cases, customer information, and field-service completion status between customer-facing operations and FSM execution. | Salesforce → Martini → ServiceNow Field Service Management | Expose a Martini API for service requests, validate and map Salesforce data into Work Orders and Work Order Tasks, then return status and completion updates through REST calls or selected callbacks. |
| SAP S/4HANA | Exchange service orders, equipment, materials, inventory, labor, completion, billing, and cost information. | SAP S/4HANA → Martini → ServiceNow Field Service Management | Use REST or approved SAP interfaces on one side and ServiceNow REST or import APIs on the other, with canonical mappings, sequencing for parent and child work, and retryable financial updates. |
| Oracle Field Service | Coordinate scheduling, dispatch, mobile execution, and service status when both field-service platforms are present. | Oracle Field Service → Martini → ServiceNow Field Service Management | Define system ownership for assignments and status, transform Work Assignment and Work Order data, and use idempotent updates to prevent scheduling conflicts or duplicate work. |
| Microsoft Dynamics 365 | Move cases, accounts, contacts, assets, and service requests into FSM and return execution or completion status. | Microsoft Dynamics 365 → Martini → ServiceNow Field Service Management | Receive a Dynamics request through a Martini API or scheduled API workflow, resolve ServiceNow references such as Location and Asset, create related objects, and publish completion results. |
| Jira | Link engineering issues, field defects, maintenance tasks, and escalations across development and field operations. | Jira → Martini → ServiceNow Field Service Management | Map Jira issue identifiers to Work Orders or Work Order Tasks, apply routing rules, and synchronize state changes using REST APIs with duplicate detection and exception handling. |
| NetSuite | Exchange customer, parts, billable work, fulfillment, and completed-service information for financial or operational processing. | NetSuite → Martini → ServiceNow Field Service Management | Use a scheduled or event-triggered workflow to map service completion and parts data, validate financial fields, and write results to NetSuite and ServiceNow with cross-reference identifiers. |
| Workday | Use worker, organizational, and cost-center data to maintain operational ownership and selected ServiceNow user information. | Workday → Martini → ServiceNow Field Service Management | Retrieve approved worker or organization changes, resolve ServiceNow User and group relationships, and apply least-privilege updates with reconciliation reporting. |
| Slack | Deliver selected assignment, escalation, or completion notifications to operational teams. | ServiceNow Field Service Management → Martini → Slack | Receive configured ServiceNow outbound callbacks, apply notification rules, format a concise message, and send it to Slack while recording delivery status and preventing duplicate notifications. |
How to build a ServiceNow Field Service Management integration in Martini
Objective
Configure ServiceNow access using an approved authentication method and a dedicated least-privilege integration user.
Instructions in Martini
- Store OAuth, Basic Authentication, certificate, or other approved credentials in environment-specific secrets.
- Confirm roles, ACLs, application scope, domain separation, and access to required FSM tables and APIs.
- Separate development, test, and production configuration.
Objective
Select the trigger that matches the required freshness, volume, and delivery guarantees.
Instructions in Martini
- Use a Martini API for inbound service requests or ServiceNow callbacks.
- Use a scheduler for incremental synchronization based on sys_updated_on.
- Use imports or batches for controlled high-volume processing.
Objective
Collect the required ServiceNow objects and related data without broad or unbounded queries.
Instructions in Martini
- Use filtered REST or SOAP requests and request only required fields where supported.
- Implement pagination and retrieve parent objects before dependent tasks or assignments.
- Retrieve attachments separately from ordinary JSON data.
Objective
Coordinate calls, relationships, transformations, business rules, and downstream operations in a reusable Martini workflow.
Instructions in Martini
- Resolve Locations, Users, Assets, and Work Orders before creating dependent objects.
- Use conditional routing for state, ownership, and validation outcomes.
- Persist watermarks, identifiers, event keys, and processing status.
Objective
Translate ServiceNow table-oriented payloads into stable canonical and target-specific models.
Instructions in Martini
- Map sys_id values separately from display values and record numbers.
- Normalize state, reference, timestamp, address, and attachment metadata.
- Apply required JSON, XML, or file transformations for each target.
Objective
Enforce business and operational rules before writing data or propagating notifications.
Instructions in Martini
- Validate mandatory fields, allowed states, ownership, and relationship order.
- Apply idempotency keys for creates and deduplication for callbacks.
- Decide whether ServiceNow business rules and downstream side effects are expected.
Common ServiceNow Field Service Management data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Work Order | Represents field service work requested for a customer, account, asset, or location. | Salesforce, SAP S/4HANA, Microsoft Dynamics 365, NetSuite | Martini retrieves or creates Work Orders through REST or import APIs, maps identifiers and state values, and maintains cross-system references. |
| Work Order Task | Represents executable work associated with a Work Order and often assigned to a field agent or crew. | Oracle Field Service, Salesforce, Microsoft Dynamics 365, SAP S/4HANA | Martini creates or updates tasks after the parent Work Order exists, resolves assignments, and handles state and duplicate updates idempotently. |
| Work Assignment | Represents assignment and scheduling information for work allocated to field personnel. | Oracle Field Service, Slack, Microsoft Dynamics 365 | Martini maps assignment identifiers, personnel, schedules, and status while applying ownership and conflict rules. |
| Location | Represents a customer site, service address, or operational location. | Salesforce, SAP S/4HANA, Microsoft Dynamics 365, Oracle Field Service | Martini resolves Location references using stable identifiers, normalizes address fields, and avoids relying on display names as unique keys. |
| User | Represents agents, dispatchers, managers, integration users, and other ServiceNow users. | Workday, Salesforce, Microsoft Dynamics 365 | Martini synchronizes only approved user attributes, applies least-privilege rules, and resolves user references for assignments. |
| Asset | Represents equipment or customer assets associated with service work; some implementations also use configuration items. | SAP S/4HANA, Salesforce, Microsoft Dynamics 365, NetSuite | Martini maps asset identifiers, ownership, location, and lifecycle data and validates references before creating related work. |
Authentication and security considerations
Authentication and authorization
ServiceNow may support OAuth 2.0, Basic Authentication, mutual TLS, certificate-based authentication, and other configured token mechanisms depending on the instance, API, and security policy. Martini should use environment-specific secrets rather than embedding credentials in workflows.
- Use a dedicated ServiceNow integration user with least-privilege roles and table permissions.
- Review ACLs, field permissions, application scope, OAuth scopes, and domain separation.
- Protect Martini callback endpoints with authentication, authorization, payload validation, and transport security.
- Audit integration changes separately from interactive user activity.
Operational considerations for ServiceNow Field Service Management integrations
Reliability and lifecycle considerations
- Respect instance transaction quotas, rate limits, node capacity, pagination, and licensed usage.
- Use filtered queries, selected fields, bounded batches, and persisted watermarks rather than unbounded Table API requests.
- Use sys_id-based idempotency, overlap windows for timestamps, and duplicate detection for callbacks and attachments.
- Distinguish ACL, authentication, validation, rate-limit, transient server, and business-rule failures.
- Retry transient failures only, capture response bodies and correlation identifiers, and route rejected records to an exception workflow.
- Validate tables, fields, choice values, mandatory fields, reference behavior, and state transitions after ServiceNow upgrades or customizations.
- Test with the same plugins, scoped applications, ACLs, and business rules that will operate in production.
Why use Martini instead of scripts or point-to-point integrations?
Maintainable integration orchestration
Point-to-point scripts can become difficult to govern when Work Orders, tasks, assignments, assets, locations, attachments, and downstream systems must be coordinated. Martini provides reusable workflows and APIs for orchestration, mapping, validation, business rules, checkpointing, and error handling while allowing the ServiceNow integration to remain based on documented APIs and configured callbacks.
- Centralize cross-system contracts instead of exposing every consumer to ServiceNow table details.
- Combine real-time callbacks with scheduled incremental synchronization when event coverage is incomplete.
- Reuse authentication, mapping, validation, retry, and monitoring patterns across integrations.
- Support REST, SOAP, JSON, XML, batch, and attachment processing within one integration design.
- Keep deployment-specific secrets and configuration separate from workflow logic.
Frequently asked questions
ServiceNow FSM can be integrated through the ServiceNow platform REST API, including Table API and attachment or import APIs, as well as SOAP services for established consumers. Configured outbound REST messages, business rules, Flow Designer, and scripted logic can send selected callbacks. Import Sets, Transform Maps, batch processing, and scheduled incremental synchronization support larger or recurring data exchanges.
Yes. Martini can consume ServiceNow REST and SOAP APIs, call import and attachment operations, expose authenticated REST endpoints for configured ServiceNow callbacks, and orchestrate workflows that map Work Orders, Work Order Tasks, Locations, Users, Assets, and related data.
No. A dedicated ServiceNow connector is not required. Martini can use ServiceNow's confirmed native REST APIs, SOAP services, outbound REST messages, import mechanisms, attachment APIs, and configured authentication methods.
Lonti does not charge an additional per-connector or per-vendor fee to integrate ServiceNow FSM. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from ServiceNow, cloud infrastructure, or other third-party systems depending on subscription, usage, and deployment model.
REST APIs are generally the primary choice for new integrations, with a governed Scripted REST API useful when a stable business contract or custom validation is required. SOAP remains relevant for existing consumers, while outbound REST callbacks, import mechanisms, batch processing, and attachment APIs address selected event, volume, and file requirements.
Yes, for configured events or flows. ServiceNow can send outbound REST requests through outbound REST messages, business rules, Flow Designer, IntegrationHub, notifications, or scripted logic. Coverage is implementation-specific rather than universal, so the event, payload, authentication, retry, and replay behavior should be explicitly designed.
Use ServiceNow sys_id as the stable source identifier, maintain cross-reference identifiers, and resolve reference fields rather than relying on display names. Synchronize parent Work Orders before Work Order Tasks, use a persisted sys_updated_on watermark with an overlap window, and make downstream creates and callback processing idempotent.
Yes. Martini can expose a controlled REST API that validates consumer requests, hides underlying ServiceNow table structures, applies business rules, orchestrates Work Order and Work Order Task creation, and returns a governed response. This can reduce direct coupling between external applications and a customized ServiceNow data model.
Related Martini documentation
Workflows
Security
Integrate ServiceNow Field Service Management with Martini
Use Martini to connect ServiceNow Field Service Management with enterprise applications through governed APIs, workflows, transformations, callbacks, imports, and secure operational processes.