GuestTrack

Records that a visitor has arrived at a project, now unless checkedInAt is given. This adds a visit record; no confirmation SMS or email is sent. Each call adds a new record, so don't repeat a call that succeeded. Get the QR code id from list_qr_codes and the field keys from get_check_in_form. For a visitor who was pre-registered, this adds a second record rather than marking the booking as arrived.

check_in_visitor

Records when a visitor left, now unless checkedOutAt is given. A visit that has already ended is returned unchanged, so repeating the call is safe. A pre-registered visitor who hasn't arrived can't be checked out.

check_out_visitor

One visit record by its id, as returned by list_visits.

get_visit

The fields visitors fill in when they check in to a project, in order. Use the field keys to read a visit's fields. Each field's setBy says where its answer goes when a visit is added: `fields`, or visitor.name / visitor.mobile / visitor.email for the name, mobile and email arguments. A field with any other setBy, or none, can't be filled in here yet.

get_check_in_form

The QR codes (check-in points such as doors or areas) of a project. A visit's qrCode.id is one of these ids.

list_qr_codes

The GuestTrack projects (sites or businesses) this connection can read, with their ids. Call this first: every other tool needs a project id.

list_projects

Visit records of a project (who checked in, when, and what they filled in), newest first unless order is asc. Returns up to `limit` visits and, when hasMore is true, a nextCursor: call again with the same filters and that cursor for the next page. Always give `from` and `to` when asked about a day or a period.

list_visits

Books a visitor who is expected at a project at a later time. The visit is recorded with status booked; no invitation or confirmation is sent. Each call adds a new record, so don't repeat a call that succeeded.

pre_register_visitor