mfr - Field Service Management icon

mfr - Field Service Management

Field service management app for scheduling technicians.

Actions19

Overview

This node integrates with a field service management system to create a new company record. It allows users to define detailed company information including name, location, support contacts, notes, and optionally specify if the company is a physical person (individual). When creating a company as a physical person, a main contact must be provided.

Common scenarios for this node include:

  • Automating the creation of customer or client companies in a field service management platform.
  • Synchronizing company data from other systems such as CRMs or ERPs.
  • Creating new company records during onboarding workflows or lead generation processes.

Practical example:

  • A technician scheduling workflow where a new client company is created automatically when a service request is initiated for a previously unknown customer.

Properties

Name Meaning
Name The official name of the company to be created. This is a required field.
Location A collection of address-related fields describing the company's location: Address, Postal code, City, State, Country, and a boolean indicating if the location is valid.
Support Telephone The telephone number for the company's support line.
Support Fax The fax number for the company's support line.
Support Mail The email address for the company's support line.
Note Additional notes or comments about the company.
External ID An external or ERP identifier for the company. If not provided, the system will generate one automatically.
Is Physical Person Boolean flag indicating whether the company is actually a single individual (true) or a company entity (false). Defaults to false. If true, a Main Contact must be defined and the company name will be set to that contact's full name.
Main Contact A collection defining the main contact person for the company. This creates a new contact rather than linking an existing one. At minimum, Last Name is required. Other optional fields include First Name, Email, Telephone, Mobile Phone, Is User, External ID, Gender, Fax, Note, Company ID, and Job Title.

Output

The node outputs JSON data representing the newly created company object as returned by the field service management API. This typically includes all properties of the company record such as its unique ID, name, location details, support contacts, notes, and any generated external IDs.

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 platform's API.
  • The node makes HTTP POST requests to the platform's OData endpoint for companies (https://portal.mobilefieldreport.com/odata/Companies).
  • Proper network access to the platform's API endpoint is necessary.

Troubleshooting

  • Missing Required Fields: The "Name" property is mandatory. Omitting it will likely cause the API to reject the request.
  • Invalid Location Data: Providing incomplete or invalid location fields may result in errors or unexpected behavior.
  • Is Physical Person Flag: If set to true but no Main Contact is provided, the API may return an error because the main contact is required in this case.
  • Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • API Endpoint Unreachable: Network issues or incorrect endpoint URLs can cause request failures.
  • Error Messages: The node throws errors received from the API. Common messages might relate to validation failures or authentication problems. Review the error message details and verify input data and credentials accordingly.

Links and References

Discussion