Send guides a daily Civitatis booking list for tomorrow

1. Civitatis sends the supplier an email for each confirmed reservation, so the first source is an inbox with one message per booking, spread over weeks.
2. The second source is the bookings area of the Civitatis provider panel, opened after logging in with your username and password.
3. For tomorrow, look up each activity and start time, add up the people per slot and note the lead traveler for each booking.
4. Copy everything into a message or sheet per guide, then check again in the morning, because late bookings and cancellations keep arriving overnight.
5. The easy miss is a cancellation after the list went out: the guide waits for a group that is not coming, or a late booking shows up with nobody expecting it.

Every evening at 19:00, send me tomorrow's Civitatis bookings per tour and start time, with head counts and the lead traveler's name and phone, so I can forward it to the guides.

1. 01

   Fix the window in local time

   The agent asks list_bookings for tomorrow only, from and to set to the same date, so a tour at 08:00 does not slip into the wrong day. It runs once per activity you sell, using the IDs from list_activities, and follows next_cursor until the day is complete.

2. 02

   Total each slot

   Bookings are grouped by activity and start time and the people are added up per slot. A slot with no bookings is listed as empty, so the guide knows the 16:00 tour may not run rather than assuming nobody checked.

3. 03

   Add who to call

   For each booking the agent opens get_booking for the reference and the lead traveler name and phone. Those details go only into the list you asked for and are not kept anywhere else.

4. 04

   Show what changed since yesterday

   A second list_bookings call with status cancelled for the same date catches cancellations. If you ran the list the day before, the agent marks new and cancelled bookings, so the guide sees changes instead of rereading the whole list.

Tomorrow, Wed 14 Oct
Bike tour of the old town 10:00: 9 people, 4 bookings
  CIV-702154 Sofia Lindqvist x3, +46 70 000 0000
  CIV-702160 James Carter x2, +44 7700 000000 (new since yesterday)
Bike tour of the old town 16:00: no bookings
Sunset cruise 18:00: 11 of 12 places
Cancelled since yesterday: CIV-701988 Ana Ruiz x2, cruise 18:00

• Civitatis travelers must be at the meeting point on the day and time shown on their voucher, and the Civitatis general conditions say the start time cannot be changed.
• The Civitatis general conditions say a supplier may ask to see the voucher, printed or on a phone, before the activity starts, and may turn away a traveler who has none.
• On Civitatis, travelers at the destination are told to call the supplier on the phone number printed on their voucher, so the number on your voucher is the one a late group will try first.
• Some Civitatis services let travelers pay part of the price when booking and the rest on arrival, depending on the supplier, so the guide may have money to collect on the day.
• Civitatis does not take responsibility when a traveler is late or cannot find the meeting point, and the start time stays as booked.

Every tool here only reads, so it can run daily from n8n, Make, Zapier or cron without waiting for your OK.

Sources: Civitatis: general conditions of use (vouchers, meeting points, partial payment) · Civitatis: provider FAQs (booking emails and panel)

curl https://cotlet.dev/api/v1/civitatis/list_bookings \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from":"2026-10-14","to":"2026-10-14","activity_id":"act_48213","status":"confirmed"}'

{
  "bookings": [
    {
      "booking_id": "bk_702154",
      "activity_id": "act_48213",
      "activity": "Bike tour of the old town",
      "date": "2026-10-12",
      "time": "10:00",
      "people": 3,
      "status": "confirmed"
    },
    {
      "booking_id": "bk_702160",
      "activity_id": "act_48213",
      "activity": "Bike tour of the old town",
      "date": "2026-10-12",
      "time": "10:00",
      "people": 2,
      "status": "confirmed"
    }
  ],
  "next_cursor": null
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is civitatis_list_bookings. Example data.

• Close Civitatis tour dates or cut places when a guide is off
• Answer Civitatis customer messages with AI drafts
• Request and reconcile your monthly Civitatis payment
• Civitatis API and MCP server: every tool
• All use cases