mfr - Field Service Management icon

mfr - Field Service Management

Field service management app for scheduling technicians.

Actions19

Overview

This node operation creates a new Service Request in a field service management system. It allows users to specify details such as the request name, associated service objects, customer, appointments, and other metadata. This is useful for automating the creation of work orders or service tickets that technicians will act upon.

Typical scenarios include:

  • Automatically generating service requests from external triggers (e.g., customer support forms).
  • Creating service requests based on predefined templates to standardize work orders.
  • Scheduling appointments and associating them with service requests programmatically.

Example: A company receives a maintenance request via a web form and uses this node to create a corresponding service request with linked service objects and scheduled appointments.

Properties

Name Meaning
Name The name/title of the service request. Required.
Service Objects JSON array specifying service objects related to the request. Format example: [ { "Id": "231" }, { "Id": "231" } ].
Service Request Template Name or ID Optionally create the service request from an existing template by selecting from a list or specifying an ID.
State Status of the service request. Options: ReadyForScheduling, Created, Scheduled, Released, or empty (no state).
Description Text description providing additional details about the service request.
Search Customer Locator to select the customer by name or ID. Supports searching from a list or entering an ID directly.
Appointments JSON array defining appointments linked to the service request. Format example: [ { "ContactIds": ["60357836802", "60357836804"], "StartDateTime": "2025-05-14T14:50:00.000Z", "EndDateTime": "2025-05-21T14:50:00.000Z" } ]
External ID An external identifier for the service request, useful for integration with other systems.
Due Date Range End Date/time indicating the end of the due date range for the service request.
Cost Center Name or ID Identifier or name of the cost center associated with the service request.
Qualifications Name or ID Identifier or name of qualifications required or associated with the service request.

Output

The output JSON contains the response from the API after creating the service request. This typically includes all properties of the newly created service request such as its unique ID, name, state, linked service objects, appointments, and any other metadata returned by the backend.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the Field Service Management API.
  • The node makes HTTP POST requests to the endpoint https://portal.mobilefieldreport.com/odata/ServiceRequests.
  • Some properties load options dynamically via API calls (e.g., service request templates), so internet access and valid credentials are necessary.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has permissions to create service requests.
  • Invalid JSON format: For Service Objects and Appointments fields, ensure the JSON arrays are well-formed and follow the expected structure.
  • Missing required fields: The Name property is mandatory; omitting it will cause the API to reject the request.
  • Invalid IDs: When specifying customers or templates by ID, verify the IDs exist and are correct.
  • API rate limits or downtime: If requests fail intermittently, check API availability and consider retry logic.

Links and References

Discussion