mfr - Field Service Management icon

mfr - Field Service Management

Field service management app for scheduling technicians.

Actions19

Overview

This node interacts with a Field Service Management system to retrieve detailed information about a specific Service Request. It supports fetching a single Service Request either by its internal ID or by an external ID, and allows expanding related entities such as service objects, customer details, reports, items, appointments/contacts, steps, comments, and stock movements. This is useful in scenarios where you need to integrate or automate workflows involving service requests, for example, pulling detailed service request data into a CRM, triggering follow-up actions based on service request status, or generating reports.

Properties

Name Meaning
Search Service Request Allows selecting the Service Request either from a searchable list or by directly entering its ID.
External ID Optionally specify an External ID to fetch the Service Request instead of using the internal ID.
Expand Choose related entities to expand and include in the response. Options include: Service Objects, Customer, Reports, Items, Appointments/Contacts, Steps, Comments, Stock Movements.

Output

The output JSON contains the full details of the requested Service Request, including any expanded related entities as specified by the "Expand" property. The structure corresponds to the Service Request object model from the Field Service Management API, potentially enriched with nested arrays or objects for expanded fields like associated service objects, customer info, reports, etc.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Field Service Management system's OData API.
  • The node makes HTTP GET requests to endpoints under https://portal.mobilefieldreport.com/odata/ServiceRequests.
  • Proper configuration of the API authentication credential within n8n is necessary.

Troubleshooting

  • Common issues:
    • Providing an invalid or non-existent Service Request ID or External ID will result in no data or an error.
    • Incorrect API credentials or expired tokens will cause authentication failures.
    • Using unsupported or misspelled values in the "Expand" field may lead to incomplete data or errors.
  • Error messages:
    • Authentication errors typically indicate misconfigured or missing API credentials.
    • 404 Not Found errors suggest the specified Service Request does not exist.
    • 400 Bad Request errors may occur if query parameters (like $expand or $filter) are malformed.
  • Resolutions:
    • Verify the correctness of the Service Request ID or External ID.
    • Ensure the API key credential is valid and has appropriate permissions.
    • Double-check the spelling and validity of expansion options.

Links and References

Discussion