Overview
This node acts as a webhook trigger for Easy!Appointments events. It listens for specific events such as creation, update, or deletion of appointments, customers, providers, and services within the Easy!Appointments system. When one of these events occurs, Easy!Appointments sends a webhook request to this node, which then triggers the connected workflow in n8n.
Common scenarios where this node is beneficial include:
- Automating follow-up emails or notifications when an appointment is created or updated.
- Synchronizing customer or provider data with other systems upon creation or modification.
- Triggering analytics or reporting workflows when services are added or removed.
For example, you could use this node to automatically add new customers from Easy!Appointments into a CRM system whenever a "Customer Created" event is received.
Properties
| Name | Meaning |
|---|---|
| Event | The specific Easy!Appointments event to listen for. Options include: |
| - Appointment Created, Deleted, Updated | |
| - Customer Created, Deleted, Updated | |
| - Provider Created, Deleted, Updated | |
| - Service Created, Deleted, Updated | |
| Webhook Name | The name assigned to the webhook in Easy!Appointments. Defaults to n8n-hook-<event> format. |
| Secret Token | A secret token used to validate incoming webhook requests by matching against a signature header. |
| Verify SSL | Whether to verify SSL certificates on the webhook URL (true/false). |
Output
The node outputs JSON data representing the payload sent by Easy!Appointments for the triggered event. This JSON contains all relevant details about the event, such as appointment information, customer data, or service details depending on the event type.
No binary data output is produced by this node.
Example output structure (simplified):
[
{
"id": "123",
"type": "appointment_create",
"data": {
"appointmentId": "456",
"customerName": "John Doe",
"service": "Consultation",
...
}
}
]
Dependencies
- Requires an API key credential for Easy!Appointments to manage webhook registration.
- The node interacts with the Easy!Appointments API to create, check, and delete webhooks.
- Proper configuration of the webhook URL in Easy!Appointments is handled automatically by the node.
- The user must ensure that the webhook endpoint is accessible from Easy!Appointments servers.
Troubleshooting
- Invalid Signature Error: If the secret token does not match the signature header (
x-ea-signature), the webhook request will be rejected. Ensure the secret token configured in the node matches the one set in Easy!Appointments. - Webhook Not Triggering: Confirm that the webhook was successfully created in Easy!Appointments. The node attempts to create and verify the webhook during activation.
- SSL Verification Issues: If using self-signed certificates or internal endpoints, consider disabling SSL verification via the "Verify SSL" property.
- API Errors During Webhook Management: Network issues or incorrect API credentials can cause failures when creating or deleting webhooks. Verify API access and credentials.
Links and References
- Easy!Appointments Official Website
- Easy!Appointments API Documentation (if available)
- n8n Webhook Trigger Documentation: https://docs.n8n.io/nodes/n8n-nodes-base.webhook/