Actions17
Overview
This node integrates with a calendar system to book appointments programmatically. It allows users to create new calendar appointments by specifying details such as the calendar, location, contact, and timing information. This is useful in scenarios like automating scheduling workflows, syncing external booking systems, or managing appointments within a CRM or business platform.
For example, you could use this node to automatically book client meetings when a form is submitted on your website, or to schedule follow-up calls after a sales opportunity reaches a certain stage.
Properties
| Name | Meaning |
|---|---|
| Calendar ID | The identifier of the calendar where the appointment will be booked. |
| Location ID | The identifier of the location associated with the appointment. |
| Contact ID | The identifier of the contact for whom the appointment is being booked. |
| Start Time | The start date and time of the appointment in ISO 8601 format (e.g., 2021-06-23T03:30:00+05:30). |
| Additional Fields | A collection of optional fields to provide more details about the appointment: |
| - End Time | The end date and time of the appointment in ISO 8601 format. |
| - Title | The title or subject of the appointment. |
| - Appointment Status | The status of the appointment. Allowed values: new, confirmed, cancelled, showed, noshow, invalid. |
| - Assigned User ID | The identifier of the user assigned to the appointment. |
| - Address | The physical address related to the appointment. |
| - Ignore Date Range | Boolean flag indicating whether to ignore date range constraints. |
| - Notify | Boolean flag indicating whether to send notifications about the appointment (default is true). |
Output
The node outputs JSON data representing the result of the appointment booking operation. This typically includes confirmation details such as the appointment ID, status, timestamps, and any other metadata returned by the calendar service API.
If the node supports binary data output (not indicated here), it would represent attachments or related files linked to the appointment.
Dependencies
- Requires an API key or OAuth2 authentication token configured in n8n to access the calendar service.
- Depends on the external calendar service's API endpoint at
https://services.leadconnectorhq.com. - The node uses specific HTTP headers including
Accept: application/json,Content-Type: application/json, and a version header for API compatibility.
Troubleshooting
- Missing Required Fields: Ensure all required properties (
Calendar ID,Location ID,Contact ID,Start Time) are provided; otherwise, the API call will fail. - Invalid Date Format: Dates must be in ISO 8601 format. Incorrect formatting can cause errors or unexpected behavior.
- Authentication Errors: Verify that the API credentials are correctly set up and have sufficient permissions.
- Appointment Status Values: Use only allowed status values (
new,confirmed,cancelled,showed,noshow,invalid); invalid values may cause rejection by the API. - Network Issues: Check connectivity to the external API endpoint if requests time out or fail.
Links and References
- ISO 8601 Date Format
- HighLevel API Documentation (generic) (Note: Replace with actual documentation link if available)