Overview
This node acts as a trigger for Easy!Appointments webhook events. It listens to various event types from the Easy!Appointments system, such as creation, update, or deletion of appointments, customers, providers, services, and other entities. When one of these events occurs, the node receives the webhook payload and triggers the connected workflow in n8n.
Common scenarios where this node is beneficial include:
- Automating follow-up actions when an appointment is created or updated.
- Synchronizing customer or provider data with other systems upon changes.
- Reacting to administrative changes like new admins or deleted service categories.
- Monitoring availability or blocked periods to update calendars or notify staff.
Practical example: Automatically send a confirmation email to a customer whenever a new appointment is created or updated by triggering a workflow on the "Appointment Created/Updated" event.
Properties
| Name | Meaning |
|---|---|
| Event | The specific Easy!Appointments event to listen for. Options include creation, update, or deletion of admins, appointments, customers, providers, secretaries, service categories, services, blocked periods, and unavailability periods. |
| Webhook Name | The name assigned to the webhook within Easy!Appointments. |
| Secret Token | A secret token used to validate incoming webhook requests to ensure they originate from Easy!Appointments. This is optional but recommended for security. |
| Verify SSL | Whether to verify SSL certificates when Easy!Appointments calls the webhook URL. Defaults to true. |
Output
The node outputs the JSON payload received from the Easy!Appointments webhook request in the json field of the output data. This payload contains detailed information about the triggered event, such as the entity affected (e.g., appointment, customer) and its data.
If the secret token validation fails, the node outputs a JSON object indicating an invalid signature, including expected and received tokens and header data.
No binary data output is produced by this node.
Dependencies
- Requires an active Easy!Appointments account with API access.
- Needs an API key credential configured in n8n to authenticate requests to Easy!Appointments.
- The node interacts with Easy!Appointments' webhook management API to create, check, and delete webhooks automatically.
- Network connectivity must allow Easy!Appointments to reach the n8n webhook URL.
- Optional: If using the secret token feature, the same token must be configured in Easy!Appointments webhook settings.
Troubleshooting
- Webhook not triggering: Ensure that the webhook URL is accessible from Easy!Appointments and that the webhook has been successfully created. Check if the correct event is selected.
- Invalid signature error: Occurs if the secret token set in the node does not match the token sent by Easy!Appointments in the
x-ea-tokenheader. Verify that both tokens are identical. - SSL verification issues: If Easy!Appointments cannot verify the SSL certificate of the webhook URL, consider disabling SSL verification in the node properties (not recommended for production).
- Webhook creation failure: Could be due to incorrect API credentials or network issues. Review API key permissions and connectivity.
- Duplicate webhooks: The node checks for existing webhooks by name and URL before creating new ones to avoid duplicates. If multiple webhooks exist with the same name but different URLs, manual cleanup may be required.