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 n8n node allows you to interact with the Easy!Appointments API. Specifically, for the Provider resource and the Get operation, this node retrieves detailed information about a specific provider using their unique Provider ID. This is useful in scenarios where you need to fetch provider details (such as name, contact info, services offered, etc.) for use in automations, reporting, or integration with other systems.
Practical examples:
- Fetching provider details to display in a dashboard.
- Using provider data to send notifications or reminders.
- Integrating provider information into CRM or HR workflows.
Properties
| Name | Type | Meaning |
|---|---|---|
| Provider ID | String | The unique identifier of the provider. |
Output
The output will be a JSON object containing all available details about the specified provider. The structure typically includes fields such as:
{
"id": "123",
"firstName": "John",
"lastName": "Doe",
"email": "john.doe@example.com",
"phone": "1234567890",
"mobile": "0987654321",
"address": "123 Main St",
"city": "Sample City",
"state": "State",
"zip": "12345",
"notes": "Some notes about the provider",
"timezone": "Europe/Berlin",
"services": "1,2,3",
"workingPlan": "{...}",
"calendar": "{...}",
"settings": "{...}"
}
Note: The actual fields depend on your Easy!Appointments setup and what data is stored for each provider.
Dependencies
- External Service: Requires access to an Easy!Appointments instance with its API enabled.
- API Credentials: You must configure the
easyAppointmentsApicredential in n8n, which includes:- Base URL of your Easy!Appointments installation
- Username
- Password
Troubleshooting
Common issues:
- Invalid Provider ID: If the provided Provider ID does not exist, the node will return an error message from the API.
- Missing Credentials: If credentials are not set up correctly, authentication errors will occur.
- Incorrect Base URL: If the base URL is missing or incorrect, the node will throw a "Base URL is required" error.
Error messages and resolutions:
"Base URL is required": Ensure that the Easy!Appointments API credential has a valid URL configured."401 Unauthorized"or similar: Check that the username and password in your credentials are correct and have sufficient permissions."Provider not found": Verify that the Provider ID exists in your Easy!Appointments system.