Actions38
- Appointment Actions
- Availability Actions
- Category Actions
- Customer Actions
- Provider Actions
- Secretary Actions
- Service Actions
- Settings Actions
- Unavailability Actions
- Working Plan Actions
Overview
The Easy!Appointments node for n8n allows you to interact with the Easy!Appointments API, specifically to create new appointments. This is useful in automated workflows where you need to schedule appointments programmatically based on triggers or data from other systems (e.g., booking a meeting when a form is submitted, syncing appointments from another calendar, or automating reminders).
Practical examples:
- Automatically create an appointment when a customer fills out a web form.
- Integrate with CRM tools to book follow-up meetings.
- Schedule service appointments based on incoming support tickets.
Properties
| Name | Type | Meaning |
|---|---|---|
| Additional Fields | Collection | A set of optional fields to define the details of the appointment. Each field below can be included as needed: |
| Start | String | Start date and time of the appointment (format: YYYY-MM-DD HH:MM:SS) |
| End | String | End date and time of the appointment (format: YYYY-MM-DD HH:MM:SS) |
| Location | String | Location of the appointment |
| Color | String | Color code for the appointment |
| Status | String | Status of the appointment |
| Notes | String | Notes for the appointment |
| Customer ID | String | ID of the customer |
| Provider ID | String | ID of the provider |
| Service ID | String | ID of the service |
All fields are optional but at least one should typically be provided to create a meaningful appointment.
Output
The output will be a JSON object representing the created appointment as returned by the Easy!Appointments API. The structure depends on the API response, but it generally includes all the properties sent in the request plus additional metadata such as the appointment's unique ID and timestamps.
Example output:
{
"id": 123,
"start": "2024-07-01 10:00:00",
"end": "2024-07-01 11:00:00",
"location": "Main Office",
"color": "#FF0000",
"status": "confirmed",
"notes": "First consultation",
"customerId": "456",
"providerId": "789",
"serviceId": "1011",
// ...other fields as provided by the API
}
No binary data is produced by this operation.
Dependencies
- External Service: Requires access to an Easy!Appointments instance with its API enabled.
- Credentials: You must configure
easyAppointmentsApicredentials in n8n, including:- Base URL (without trailing slash)
- Username
- Password
Troubleshooting
Common issues:
Missing or incorrect credentials: If the base URL, username, or password are missing or incorrect, authentication will fail.
- Error message: "Base URL is required" or HTTP 401/403 errors.
- Resolution: Double-check your credential settings in n8n.
Invalid input data: If required fields for your business logic are missing (e.g., no start/end time), the API may reject the request.
- Error message: API-specific error messages about missing or invalid fields.
- Resolution: Ensure all necessary fields are provided in "Additional Fields".
API endpoint not reachable: Network issues or wrong base URL.
- Error message: Connection refused, timeout, or DNS errors.
- Resolution: Verify the API URL and network connectivity.
Unexpected API changes: If the Easy!Appointments API changes, the node may not work as expected.
- Resolution: Check API documentation and update the node if necessary.