Actions19
- Company Actions
- Appointment Actions
- Item Type Actions
- Service Object Actions
- Service Request Actions
- Document Actions
- User Actions
- Report Actions
Overview
This node allows you to create a new appointment in a field service management system. It is useful for scheduling appointments linked to specific contacts, specifying the type of appointment (such as illness or vacation), and defining start and end times. Typical use cases include managing technician schedules, booking client meetings, or tracking employee absences.
For example, you can create an appointment for a contact representing a customer or employee, specify that it is a "Vacation" type, and set the exact start and end date-times for the appointment.
Properties
| Name | Meaning |
|---|---|
| Contact | The contact associated with the appointment. You can select from a searchable list or enter the contact ID directly. |
| Start Date Time | The starting date and time of the appointment. |
| End Date Time | The ending date and time of the appointment. |
| Type | The category of the appointment. Options are: Illness, Vacation, Other, or empty (no type). |
Output
The output JSON contains the data returned by the API after creating the appointment. This typically includes details of the newly created appointment such as its unique identifier, linked contact ID, type, start and end times, and any other metadata provided by the backend service.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Field Service Management API.
- The node makes HTTP POST requests to the endpoint
https://portal.mobilefieldreport.com/odata/Appointmentsto create appointments. - Proper configuration of the API credential within n8n is necessary for successful execution.
Troubleshooting
- Invalid Contact ID: If the contact ID is not numeric or does not exist, the API may return an error. Ensure the contact exists and the ID is correct.
- Missing Required Fields: The Contact property is required. Omitting it will cause the request to fail.
- Date-Time Format Issues: Ensure that the start and end date-time values are valid ISO 8601 strings; otherwise, the API might reject the request.
- Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- API Endpoint Unreachable: Network issues or incorrect API URLs can cause failures. Confirm network connectivity and endpoint correctness.
Links and References
- Field Service Management API Documentation (general reference to the OData API used)
- ISO 8601 Date and Time Format (for date-time formatting guidance)