OneTapCheckIn for AI agents
Agents read OneTapCheckIn at once. Changes and sends are held for a person's approval by default.
About OneTapCheckIn
OneTapCheckIn helps organizations manage events, attendee profiles, check-ins, passports, integrations, and attendance alerts.
What an agent can do in OneTapCheckIn
Every OneTapCheckIn action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in OneTapCheckIn without asking first. 7 actions.
- Find ListsGet one list by exact ID or search the connected organization's lists. Search returns one page and a continuation cursor.
- Find ParticipantsGet one participant by exact ID or search attendance records by list, profile, status, text, or date range. Search returns one page and a continuation cursor.
- Find ProfilesGet one profile by ID or search profiles by identity, list, passport, or check-in code. Returns one page and a continuation cursor.
- Get OrganizationReturn the organization associated with the connected API key. The response does not expose the organization's subscription tier.
- Get Profile Custom FieldsReturn the organization's configured profile custom-field definitions so an agent can use valid field names and value types when creating or updating profiles.
- List AlertsReturn one page of organization alert and automation rules together with outbound check-in confirmation settings.
- List PassportsList one page of standard passports for exactly one profile or participant. Use next_page to continue when a full page is returned; the provider does not support an unfiltered list-all call.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 12 actions.
- Add ParticipantsAdd one or more existing profiles to one or more lists without checking them in. This deliberately excludes add-all-profiles and initial attendance fields to prevent unexpectedly broad or historical m
- Create ListCreate an event/check-in list. The provider currently creates open registration even when disabled during creation, so this tool does not expose that unreliable flag; update the list afterward when re
- Create ProfileCreate one person profile without adding it to a list. OneTapCheckIn automatically creates a global passport. This tool does not send a confirmation email.
- Create ProfilesCreate 1 to 25 person profiles in input order using one provider request per profile. Confirmation emails are always disabled. Provider validation or conflict failures are reported per item and later
- Delete ListPermanently delete one list by ID. This is intentionally limited to one known list and never invokes the provider's bulk or delete-all operation.
- Delete ProfilePermanently delete one profile. This also removes the profile's automatically created global passport and never invokes the provider's bulk or delete-all operation.
- Remove ParticipantRemove one participant record from its list. This deletes the list membership and attendance record, not the underlying profile.
- Update ListPartially update a list. Omitted fields are preserved even though the provider uses PUT.
- Update ParticipantUpdate metadata on one participant record without performing check-in or checkout. Omitted fields are preserved.
- Update Participant AttendanceCheck in, check out, undo check-in, or undo checkout for one known participant. These operations change attendance history; undo actions retain attachments. This tool never sends visitor alerts.
- Update Participant Attendance BatchApply one shared check-in, checkout, undo check-in, or undo checkout operation to 1 to 25 participants in input order, using one provider request per item. Items execute independently: validation, not
- Update ProfilePartially update one profile. Omitted fields are preserved even though the provider uses PUT.
Changes wait in Needs you
Changes and sends in OneTapCheckIn are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
OneTapCheckIn questions
Can an agent change data in OneTapCheckIn on its own?
Not by default. Changes and sends in OneTapCheckIn are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in OneTapCheckIn?
This connector lists 7 read actions. Reads run at once, without waiting for approval.
How does OneTapCheckIn connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.