mfr - Field Service Management icon

mfr - Field Service Management

Field service management app for scheduling technicians.

Actions19

Overview

This node operation retrieves multiple service requests from a field service management system via an OData API. It is useful for scenarios where you need to list or analyze many service requests, such as generating reports, monitoring workload, or integrating service request data into other systems.

For example, you might use this node to:

  • Fetch all open service requests filtered by certain criteria (e.g., status or customer).
  • Retrieve a limited number of recent service requests for dashboard display.
  • Expand related entities like qualifications to get more detailed information in one call.

Properties

Name Meaning
Limit Maximum number of service requests to return. Must be at least 1.
Fetch All Results Boolean flag indicating whether to fetch all available service requests regardless of the limit. If set to true, the node ignores the "Limit" property and retrieves all matching records.
Filter An OData filter string to restrict which service requests are returned based on conditions. For example, filtering by status or date. Documentation: https://www.odata.org/documentation/odata-version-3-0/url-conventions/
Expand Allows expanding hidden or related fields in the response. Currently supports expanding "Qualifications". This means additional related data can be included inline with each service request.

Output

The output is a JSON array where each element represents a service request object retrieved from the API. Each object contains the standard fields of a service request plus any expanded related entities if requested.

If the "Expand" option includes "Qualifications", the qualifications related to each service request will be included in the output objects.

No binary data is output by this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Field Service Management API.
  • The node makes HTTP GET requests to the endpoint https://portal.mobilefieldreport.com/odata/ServiceRequests.
  • Supports OData query parameters $top, $skip, $filter, and $expand to control pagination, filtering, and expansion of related entities.

Troubleshooting

  • Issue: No results returned despite expecting some service requests.

    • Cause: The filter condition may be too restrictive or incorrect.
    • Solution: Verify the OData filter syntax and try removing or simplifying the filter to confirm data availability.

  • Issue: Node times out or runs slowly when fetching many records.

    • Cause: Large datasets require multiple paginated requests.
    • Solution: Use the "Fetch All Results" option carefully; consider limiting the number of results or applying filters to reduce data volume.

  • Issue: Authentication errors.

    • Cause: Invalid or missing API key credential.
    • Solution: Check that the API key credential is correctly configured and has necessary permissions.

  • Error message: "Request failed" or similar HTTP error.

    • Cause: Network issues, invalid parameters, or server-side problems.
    • Solution: Review the request parameters, ensure network connectivity, and check API service status.

Links and References

Discussion