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, when using the Provider resource and the Create operation, this node enables you to create a new provider (such as a staff member or service provider) in your Easy!Appointments system.
Common scenarios:
- Automating onboarding of new staff/providers into your appointment scheduling system.
- Integrating HR or CRM systems with Easy!Appointments to keep provider lists up-to-date.
- Bulk creation of providers from external data sources.
Practical example:
You could use this node in a workflow that triggers whenever a new employee is added to your HR database, automatically creating a corresponding provider profile in Easy!Appointments.
Properties
| Name | Type | Meaning |
|---|---|---|
| Additional Fields | Collection | A group of optional fields to set details for the new provider. See below for options. |
Fields within "Additional Fields":
| Name | Type | Meaning |
|---|---|---|
| First Name | String | First name of the provider |
| Last Name | String | Last name of the provider |
| String | Email address of the provider | |
| Phone | String | Phone number of the provider |
| Mobile | String | Mobile number of the provider |
| Address | String | Address of the provider |
| City | String | City where the provider is located |
| State | String | State where the provider is located |
| ZIP | String | ZIP code of the provider's location |
| Notes | String | Any notes about the provider |
| Timezone | String | Provider's timezone |
| Services | String | Comma-separated list of service IDs assigned |
| Working Plan | String | JSON string describing working plan |
| Calendar | String | Calendar settings in JSON format |
| Settings | String | Provider-specific settings in JSON format |
Output
- The output will be a JSON object representing the newly created provider as returned by the Easy!Appointments API.
- The structure of the output depends on the API response, but typically includes all submitted fields plus any additional metadata or IDs generated by the system.
Example output:
{
"id": 123,
"firstName": "John",
"lastName": "Doe",
"email": "john.doe@example.com",
"phone": "1234567890",
"mobile": "0987654321",
"address": "123 Main St",
"city": "Metropolis",
"state": "NY",
"zip": "10001",
"notes": "New provider",
"timezone": "America/New_York",
"services": "1,2,3",
"workingPlan": "{\"monday\":{\"start\":\"09:00\",\"end\":\"17:00\"}}",
"calendar": "{}",
"settings": "{}"
}
Note: Actual fields may vary depending on what you provide and the API's response.
Dependencies
- External Service: Requires access to an Easy!Appointments instance with API enabled.
- API Credentials: You must configure the
easyAppointmentsApicredential in n8n, including:- Base URL (e.g.,
https://your-easyappointments-instance.com/api/v1) - Username
- Password
- Base URL (e.g.,
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 Easy!Appointments API credentials in n8n.
- Error message:
Invalid field formats: Some fields (like
workingPlan,calendar,settings) expect valid JSON strings.- Error message: API may return validation errors if the JSON is malformed.
- Resolution: Ensure these fields contain properly formatted JSON.
Required fields not provided: While all fields are technically optional for this operation, your Easy!Appointments configuration may require certain fields (like email).
- Error message: API returns a validation error.
- Resolution: Check API documentation or your instance's requirements.
Network issues: If n8n cannot reach your Easy!Appointments server, requests will fail.
- Resolution: Ensure network connectivity and correct API endpoint.