Meetbot icon

Meetbot

Book meetings with the Meetbot scheduling API

Overview

This node integrates with the Meetbot scheduling API to facilitate booking meetings programmatically. It supports multiple operations including retrieving scheduling pages, fetching page details, listing available time slots, and making new bookings.

The Make Booking operation allows users to create a new meeting reservation on a specified scheduling page by providing the meeting start time, guest's name, email, and optional notes. This is useful for automating appointment scheduling workflows, such as confirming meetings from form submissions or CRM triggers.

Practical examples:

  • Automatically book a meeting slot when a customer fills out a contact form.
  • Schedule internal team meetings based on availability fetched from Meetbot.
  • Integrate Meetbot bookings into broader automation pipelines for event management.

Properties

Name Meaning
Page The URL of the scheduling page where the booking will be made (e.g., https://meet.bot/user/30min)
Start Time The starting time of the meeting in ISO 8601 format, matching an available slot from the API
Guest Name The full name of the person who is making the booking
Guest Email The email address of the person making the booking
Notes Optional notes for the booking that will appear in the calendar invite

Output

The node outputs a JSON object representing the response from the Meetbot API after attempting to make a booking. This typically includes details about the confirmed booking such as booking ID, time, guest information, and any metadata returned by the API.

If an error occurs during the booking process, the output JSON will contain an error field describing the issue.

The node does not output binary data.

Dependencies

  • Requires an API authentication token credential for the Meetbot API.
  • Makes HTTP requests to the Meetbot API endpoints:
    • https://meet.bot/v1/book for creating bookings.
  • Requires proper configuration of the API key credential within n8n.

Troubleshooting

  • Common issues:

    • Invalid or missing API token: Ensure the API key credential is correctly set up.
    • Incorrect page URL or unavailable slot time: Verify the scheduling page URL and that the start time matches an available slot.
    • Missing required fields: All required properties (page, start, guestName, guestEmail) must be provided.
  • Error messages:

    • Errors returned from the API are parsed and surfaced in the node output under the error field.
    • Typical errors include authorization failures, invalid parameters, or slot unavailability.
    • To resolve, check the error message details and adjust input parameters or credentials accordingly.

Links and References

Discussion