Overview
The "Get Slots" operation of the Meetbot node retrieves available booking slots from a specified scheduling page URL. It allows filtering these slots by date range, timezone, and limits the number of results returned. Optionally, it can include shareable booking links for each slot.
This node is useful when you want to programmatically access open meeting times from a Meetbot scheduling page to display availability, integrate with other calendar or booking systems, or automate appointment management workflows.
Practical examples:
- Fetching available time slots for a consultant's scheduling page to show on a custom website.
- Automatically retrieving open booking slots within a date range to sync with an external calendar.
- Generating shareable booking links for available slots to send in automated emails.
Properties
| Name | Meaning |
|---|---|
| Page | The scheduling page URL to query available booking slots for (e.g., https://meet.bot/user/30min) |
| Count | The maximum number of booking slots to return |
| Start Date | Optional start date filter for slots, formatted as YYYY-MM-DD |
| End Date | Optional end date filter for slots, formatted as YYYY-MM-DD |
| Timezone | Optional timezone for the query in IANA format (e.g., America/New_York) |
| Include Booking Link | If true, includes a shareable booking link for each slot in the response |
Output
The output JSON contains an array of available booking slots matching the query parameters. Each slot typically includes details such as the start time, duration, and optionally a shareable booking link if requested.
If the "Include Booking Link" property is enabled, each slot object will have a URL that can be shared directly for booking that specific time.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token credential for the Meetbot scheduling API.
- The node makes HTTP GET requests to the Meetbot API endpoints.
- Proper network connectivity to
https://meet.botis necessary.
Troubleshooting
Common issues:
- Invalid or missing API token credential will cause authentication failures.
- Incorrect or malformed scheduling page URLs may result in empty or error responses.
- Date filters must be valid dates; invalid formats might cause errors or unexpected results.
- Timezone strings must conform to IANA timezone names; incorrect values may lead to wrong slot times.
Error messages:
- Errors returned from the API are parsed and surfaced with descriptive messages.
- If the API returns validation errors, the first relevant message is shown.
- Network or HTTP errors will also be reported with their message.
Resolution tips:
- Verify the API token credential is correctly configured and has required permissions.
- Double-check the scheduling page URL format.
- Use valid ISO date strings for start and end dates.
- Confirm the timezone string matches a valid IANA timezone name.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.
Links and References
- Meetbot Scheduling API Documentation
- IANA Time Zone Database
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)