EventTemple Integration

Venue and event management, connected with an API key. Covers enquiries, bookings, and the spaces behind them. EventTemple official site ↗

What it covers

EventTemple manages venues, events and the enquiries that fill them. Connecting it lets the concierge describe what spaces exist, check what is booked, and capture an enquiry with the detail a salesperson actually needs.

Setup steps

Create an API key in EventTemple
In EventTemple, generate an API key for the account you want Maison to read.
Send it to Maison
Provide the key through the business console or to your Maison contact. It is encrypted at rest and never shown again once saved.
Choose which tools to enable
Two are on by default. Anything that writes to your EventTemple account is opt-in — see the table below.

Available tools

5 tools are available for EventTemple. The concierge calls them on a guest's behalf during a conversation; which are enabled is set per property, so you only turn on what you want it to be able to do.

Enabled by default (2)

On as soon as the integration is connected, with nothing else to configure.

Tool What it does

eventtemple_get_space_availabilities Check which event/function spaces are free for a specific time window AND large enough for the group. Returns the ids of available spaces — cross-reference eventtemple_get_spaces to get their names and details. local_start_time and local_end_time are the property's local time in 'YYYY-MM-DD HH:MM' format (e.g. '2026-09-01 09:00'); attendees is the expected attendee count. An empty result means no space fits — offer alternative dates or a smaller group. Always check availability before promising a date. Never quote rates or pricing — direct pricing questions to the events team.

eventtemple_get_spaces List the property's event/function spaces (meeting rooms, ballrooms) with their names, capacities, and descriptions. Use this when a guest asks what event spaces exist, how many people a space holds, or which space suits their event. Provide space names, capacities, and descriptions to help guests choose. Never quote room rates or pricing — direct all rate and pricing inquiries to the events team. To check whether spaces are open at a specific time, use eventtemple_get_space_availabilities instead.

Tool	What it does
`eventtemple_get_space_availabilities`	Check which event/function spaces are free for a specific time window AND large enough for the group. Returns the ids of available spaces — cross-reference eventtemple_get_spaces to get their names and details. local_start_time and local_end_time are the property's local time in 'YYYY-MM-DD HH:MM' format (e.g. '2026-09-01 09:00'); attendees is the expected attendee count. An empty result means no space fits — offer alternative dates or a smaller group. Always check availability before promising a date. Never quote rates or pricing — direct pricing questions to the events team.
`eventtemple_get_spaces`	List the property's event/function spaces (meeting rooms, ballrooms) with their names, capacities, and descriptions. Use this when a guest asks what event spaces exist, how many people a space holds, or which space suits their event. Provide space names, capacities, and descriptions to help guests choose. Never quote room rates or pricing — direct all rate and pricing inquiries to the events team. To check whether spaces are open at a specific time, use eventtemple_get_space_availabilities instead.

Available on request (3)

Off by default. Ask Maison to enable any of these for your property — several change data in your EventTemple account, so they are opt-in rather than assumed.

Tool	What it does
`eventtemple_create_booking`	Step 2 of 2 for capturing an event inquiry as a sales lead: create a LEAD booking linked to the contact. Call this only after eventtemple_create_contact succeeds, passing the returned contact id as data.attributes.contact_id. The booking name should summarize the inquiry — include event type and guest count (e.g. 'Wedding inquiry — Jane Smith, ~120 guests'). Dates are ISO YYYY-MM-DD. This records a sales lead for the events team — it does NOT confirm or reserve anything; the events team follows up. Never retry after a timeout — the lead may already have been recorded. Route pricing questions and booking confirmations to the events team.
`eventtemple_create_contact`	Step 1 of 2 for capturing an event inquiry as a sales lead: create the contact record. Before calling, collect the guest's event type, approximate dates, guest count, and contact details (first and last name plus email; phone optional). Pass them inside data.attributes. On success this returns the new contact id (data.id) — immediately call eventtemple_create_booking with that contact id to complete the lead. Never call this twice for the same inquiry, and never retry after a timeout — the contact may already have been created.
`eventtemple_create_full_booking`	OPERATOR-GRADE: create a REAL event booking with its agenda events — never use in guest conversations unless explicitly instructed. This reserves function spaces in EventTemple (not a lead). For guest event inquiries always use the two-step lead flow (eventtemple_create_contact then eventtemple_create_booking) instead. Each agenda event needs a name, ISO YYYY-MM-DD dates, a status, expected and guaranteed headcounts, and optionally the space_id from eventtemple_get_spaces. Never retry after a timeout — the booking may already have been created.

Not yet certified (15)

Built and working against the EventTemple API, but Maison is not yet certified with EventTemple to use them in production, so they cannot be enabled today. Listed so you can see what is coming rather than discover the gap when you ask for it.

Tool	What it does
`eventtemple_change_booking_dates`	Reschedule an event booking to a new start/end. start_at and end_at are UTC date-times in ISO 8601 format (e.g. '2026-09-01T09:00:00.000Z'). Set shift_event_dates true (recommended) to move the booking's agenda events by the same offset — otherwise the events keep their original dates. Always confirm the new dates with the verified contact, and check space availability (eventtemple_get_space_availabilities) before promising them. Never retry after a timeout — the dates may already have changed.
`eventtemple_change_booking_status`	Change an event booking's status: lead, tentative, definite, or lost. To CANCEL a booking, set status 'lost'. Confirm the exact intent with the verified contact before any transition — 'definite' confirms the event and 'lost' cancels it, and both have business consequences the events team acts on. Never retry after a timeout — the status may already have changed.
`eventtemple_get_booking`	Get one event booking by id: name, status (lead/tentative/definite/lost), dates, day-times (seconds since midnight), number of events on its agenda, amount paid, and total. Use for any 'what's the status / balance of my event booking' question. List the agenda items with eventtemple_list_events. Never quote or negotiate pricing beyond the recorded totals — route pricing questions to the events team.
`eventtemple_get_contact`	Get one event contact by id: name, email, phone number, and job title. Use after eventtemple_search_contacts to confirm contact details, or to read the contact attached to a booking. Only share these details with the verified contact themself.
`eventtemple_get_event`	Get one agenda event by id: name, dates, day-times (seconds since midnight), status, notes, expected/guaranteed/actual headcounts, and the booking, space, event-type, and setup-style ids. Use for detail questions about a specific agenda item found via eventtemple_list_events.
`eventtemple_get_event_types`	List the property's event types (e.g. Wedding, Corporate Meeting) as id/value pairs. Use to resolve the event_type_id on agenda events, or to tell a guest what kinds of events the property hosts.
`eventtemple_get_menu_items`	List the property's catering menu items with names, descriptions, and published per-item prices (price and tax-included price). Use when a guest asks about catering or menu options for their event. Quote only these published catalog prices — for package deals, discounts, or negotiated pricing, direct the guest to the events team.
`eventtemple_get_packages`	List the property's event packages (bundled offerings, e.g. 'Full-Day Meeting Package') with names and descriptions. Use when a guest asks what event packages exist. Package pricing is not included — direct pricing questions to the events team.
`eventtemple_get_setup_styles`	List the property's room setup styles (e.g. Theatre, Banquet, U-Shape) as id/value pairs. Use to resolve the setup_style_id on agenda events, or to describe seating arrangements to a guest.
`eventtemple_get_space`	Get one event/function space by its id (from eventtemple_get_spaces): name, minimum and maximum capacity, floor area, and description. Use when a guest asks for detail about a specific space. Never quote rates or pricing — direct pricing inquiries to the events team.
`eventtemple_list_bookings`	List the event bookings belonging to a contact (by numeric contact id from eventtemple_search_contacts): booking id, name, status, and dates. Status is one of lead, tentative, definite, or lost — only 'definite' is a confirmed event; treat 'lost' as cancelled. Use eventtemple_get_booking for full detail on one booking. If the result notes more bookings exist, narrow down by asking which event the guest means.
`eventtemple_list_events`	List the agenda events inside an event booking (by numeric booking id): name, dates, day-times (seconds since midnight), status, expected/guaranteed headcounts, and the space, event-type, and setup-style ids. Resolve those ids via eventtemple_get_space, eventtemple_get_event_types, and eventtemple_get_setup_styles. Use eventtemple_get_event for one event's full detail including notes.
`eventtemple_search_contacts`	Search the property's event contacts by name or email and return matching contact ids and names. Use this to locate an existing contact's id before reading their details (eventtemple_get_contact) or listing their event bookings (eventtemple_list_bookings). Results contain names only — use eventtemple_get_contact for contact details. If the result notes more matches exist, ask for a more specific name or the email address and search again.
`eventtemple_update_booking`	Rename an existing event booking (data.attributes.name). Use when a verified contact asks to change how their event is titled. For status changes (confirm/cancel) use eventtemple_change_booking_status; for rescheduling use eventtemple_change_booking_dates. Never retry after a timeout — the change may already have been applied.
`eventtemple_update_contact`	Update an existing event contact's details (name, email, phone number, job title). Include only the fields being changed inside data.attributes — omitted fields keep their current values. Use when a verified contact asks to correct their contact information. Never retry after a timeout — the update may already have been applied.