Reference · built on requestConnectorField service & CMMS

Salesforce Field Service

Work orders, service appointments, resources, and territories from Salesforce Field Service through the platform's REST and SOAP APIs.

Request accessPricing ↗

About

Salesforce Field Service adds work orders, service appointments, service resources, territories, and scheduling to the Salesforce platform. Work orders describe the work and link to assets, cases, accounts, and entitlements. Service appointments are the visits, with arrival windows and scheduled and actual times. Service resources, crews, skills, absences, and territory memberships describe who can do the work and where. All of these are standard objects reachable through the SOAP and REST APIs and SOQL, and the FSL managed package adds scheduling, optimization, and the Appointment Bundling REST APIs.

Fibric reads those objects, polls changes with getUpdated(), and proposes appointment updates, resource assignments, and work order changes. A dispatcher approves each proposal before the record is written.

This is a reference listing. It documents what Fibric would read from Salesforce Field Service and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • WorkOrder and WorkOrderLineItem records with their Asset, Case, Account, and Entitlement lookups, through REST and SOQL
  • ServiceAppointment records: ArrivalWindowStartTime and EndTime, scheduled and actual times, and status, with getUpdated() and getDeleted() for change polling
  • ServiceResource, ServiceCrew, AssignedResource, ServiceResourceSkill, ResourceAbsence, and ServiceResourceCapacity records
  • ServiceTerritory, ServiceTerritoryMember, OperatingHours, and TimeSlot records that say where and when work can happen
  • WorkType templates with durations and SkillRequirement records
  • MaintenancePlan, Asset, ProductRequest, and ProductItem records from the preventive maintenance and inventory data models
  • Shift, TimeSheet, and TimeSheetEntry records

Proposed actions

  • Target capability: propose a ServiceAppointment update, such as a new arrival window or status, through update() on the object
  • Target capability: propose an AssignedResource record that assigns a ServiceResource or a Crew resource to an appointment
  • Target capability: propose a WorkOrder or WorkOrderLineItem create or update, including its WorkType
  • Target capability: propose bundling or unbundling service appointments through the Appointment Bundling REST APIs
  • Target capability: propose a ResourceAbsence or ResourcePreference record for the dispatcher to approve

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reassign when a technician is absent

    A new ResourceAbsence overlaps AssignedResource records. The operator lists the affected ServiceAppointments, finds resources with the required skills in the territory, and proposes new assignments for approval.

    With Field Dispatch

  • Keep the customer's arrival window honest

    ActualStartTime on the previous appointment runs late. The operator compares it to the next ArrivalWindowStartTime and proposes a window update and a customer notice.

    With Service Window

  • Generate work from maintenance plans on time

    MaintenancePlan records and their assets are read. When a plan's next date approaches, the operator proposes the WorkOrder and its WorkType for approval.

    With Service Interval

  • Age out stalled work orders

    Work orders and line items past your age threshold are listed with their appointments and status. The operator proposes the next action and records it on the work order.

    With Work Order Aging

Requirements

  • A Salesforce org with Field Service enabled under Setup > Field Service Settings, which exposes the standard field service objects
  • The Field Service managed package (FSL namespace) and the matching FSL permission set, such as FSL Agent, for scheduling features
  • An external client app, or an existing connected app, with OAuth settings enabled for API integration
  • Object and field permissions on WorkOrder, ServiceAppointment, ServiceResource, and related objects for the integration user
Authentication
OAuth 2.0 through an external client app or an existing connected app in your Salesforce org; Salesforce restricts creating new connected apps as of Spring '26 and recommends external client apps.

Limits

  • Appointment Bundling REST APIs allow 1000 calls per 24 hours plus 50 per engineer license, 10 concurrent calls, and one Start Batch per territory-hour
  • Appointment Bundling APIs are not supported in Gov Cloud and need API version 54.0 or later
  • Scheduling and optimization run inside the FSL managed package; this listing reads their results and proposes records, it does not run the optimizer

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Salesforce Field Service ↗

Questions and answers

Do I need the Field Service managed package?
Not to read the objects. Enabling Field Service under Setup > Field Service Settings exposes the standard objects to the SOAP and REST APIs. Scheduling, optimization, and the FSL Apex namespace come from the managed package, and users need an FSL permission set such as FSL Agent to book appointments.
How does the connector learn about changed appointments?
ServiceAppointment supports getUpdated() and getDeleted(), so the connector polls for records changed since its last read. Its fields include ArrivalWindowStartTime, ArrivalWindowEndTime, ActualStartTime, ActualEndTime, and ActualDuration, which is set automatically when the actual times are first filled.
What limits apply to appointment bundling?
The Appointment Bundling REST APIs allow 1000 calls within 24 hours, plus 50 per engineer license, with 10 concurrent calls; Start Batch is one call per hour per territory. They need API version 54.0 or later and are not supported in Gov Cloud.
Ask about Salesforce Field Service

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Salesforce Field Service through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy