Overview
This node integrates with the Meetbot scheduling API to facilitate booking meetings and retrieving scheduling information. It supports operations such as fetching all scheduling pages for the authenticated user, getting detailed information about a specific scheduling page, retrieving available booking slots with optional filters, and making new bookings.
A common use case is automating meeting scheduling workflows by programmatically accessing scheduling pages and their availability or creating bookings based on external triggers or data sources. For example, you could automatically check available slots on a scheduling page and book a meeting when certain conditions are met, or retrieve page info to display scheduling details in another system.
The Get Page Info operation specifically retrieves detailed information about a single scheduling page given its URL.
Properties
| Name | Meaning |
|---|---|
| Page | The URL of the scheduling page to get information about (e.g., https://meet.bot/user/30min). This must be provided for the "Get Page Info" operation. |
Output
The output is a JSON object containing the response from the Meetbot API for the requested scheduling page information. The structure depends on the API's response but generally includes details about the scheduling page such as its configuration, availability, and metadata.
The node does not output binary data.
Example output JSON structure (simplified):
{
"id": "string",
"name": "string",
"description": "string",
"duration": number,
"timezone": "string",
"availability": [ /* array of available times or rules */ ],
...
}
Dependencies
- Requires an API key credential for authenticating with the Meetbot API.
- The node makes HTTP requests to the Meetbot API endpoints (
https://meet.bot/v1/info). - Proper network access to the Meetbot API service is necessary.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authentication errors.
- Providing an incorrect or malformed scheduling page URL may result in errors or empty responses.
- Network connectivity problems can cause request failures.
Error messages:
- Errors returned by the API are parsed and surfaced as node errors with descriptive messages.
- If the API returns validation errors, the first error message is extracted and shown.
- To resolve errors, verify the API token, ensure the page URL is correct, and check network connectivity.
The node supports continuing on failure, allowing workflows to handle errors gracefully.
Links and References
- Meetbot Scheduling API Documentation (hypothetical link)
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)