Vyte
SchedulingConnect AI agents to Vyte, a meeting scheduling platform for individuals and teams. Agents create and confirm events, find free slots across users and teams, and manage invitees so group scheduling converges without long email threads.
What This Integration Enables
Most scheduling tools are built around a slot. Vyte is built around a proposal. Create Event puts several candidate dates and places in front of a group, the invitees vote on them, and only later does Confirm Event turn one of those candidates into the meeting. That distinction runs through the whole connector and it is the reason to reach for Vyte rather than a booking link. A booking link works when one person's calendar is the constraint. It stops working the moment the meeting needs four people who do not report to each other, which is most meetings that matter.
The availability surface is unusually strong for this. List Free Slots takes invitees by email, by user ID, or by team ID, and returns the open time for all of them against a duration and a date range. List Free Slots By Day groups the same answer by calendar day when a flow needs to render a picker. Get Next Availability answers the narrower question of what is bookable soonest. Get User Availability reads the recurring weekly settings behind those answers, including timezone, booking buffers, and restrictions such as treating today or the past as busy. Alongside the group scheduling side, the connector reads booking pages, which Vyte calls vytemes and addresses by the nickname at the end of the public URL, along with the appointment types configured on them. There are no triggers, so flows start from a schedule or from an event in another system rather than from a push out of Vyte. Worth knowing before you design around a delete: Vyte has no hard delete for events, and Cancel Event is the way to take one out of active scheduling, which means it notifies everybody. Agents propose, gather, and report. Ending the group's say is a human call, which is the human-in-the-loop default FlowRunner builds around. Every operation here is built and verified against Vyte's official API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A Panel Interview That Converges in a Day
A candidate reaches the panel stage in Workable. The agent reads the assigned interviewers, resolves them through List Users, and calls List Free Slots for the panel with a 60 minute duration across the next two weeks. It takes the four strongest overlaps and runs Create Event with those proposed dates, the video room as the place, and the candidate added as an invitee. The candidate votes on what suits them. Get Event returns the votes, the agent posts the tally to Slack, and the recruiting lead confirms. The candidate never receives a link to somebody's personal calendar and the panel never trades messages about Thursday.
Offering the Soonest Time, Not a Calendar Grid
A prospect submits a demo request through Typeform. Rather than replying with a booking URL, the agent runs Get Next Availability for the assigned rep against a 30 minute appointment duration and takes the three soonest genuinely open slots. It sends those three specific times through Gmail in the body of the reply. If the prospect picks one, Create Event proposes exactly that slot and Confirm Event closes it because the choice came from the person themselves. If they ask for something else, the agent falls back to List Free Slots By Day and offers a week laid out by day. The prospect makes one decision instead of navigating an interface.
Keeping the Guest List Honest as a Project Changes
A project's stakeholder list shifts partway through a planning cycle. The agent reads the current list from Notion, compares it against the invitees returned by Get Event for the upcoming session, and prepares the difference. New stakeholders are added through Add Invitees, which sends them an invitation immediately, and departures are prepared as Remove Invitee calls with the invitee IDs read from the event object. The proposed change posts to Slack for the project owner to confirm, because adding somebody to a meeting is cheap and removing them is a signal. Once approved, the agent applies both sides in one pass and logs the change against the project record.
Human-in-Loop Highlight
Confirm Event locks in one date and one place and sets the event to confirmed. That sentence sounds administrative and it is not. Everything before it in a Vyte event is a group deciding: the invitees were asked to vote, Get Event returns each of them alongside the slots they chose, and until the confirm runs, a person who has not voted yet still has a say. Confirm Event is the moment their input stops mattering. That is fine when the vote is complete and it is a small betrayal when it is not, because four votes out of seven is a partial count and not a decision, and the three people who had not answered yet find out by receiving a calendar entry. The exit is expensive in a specific way: Vyte has no hard delete for events, so an early confirm can only be walked back with Cancel Event, which tells every invitee the meeting is off. There is no quiet correction available. So the agent does the work that is genuinely mechanical and stops at the count. It messages the organizer: "Q3 planning has 4 of 7 votes in. Tuesday 14:00 leads with 3, Thursday 10:00 has 2, and the CFO and two regional leads have not voted. Confirm Tuesday now, wait until Friday, or send a reminder?" Proposing slots, computing overlap across a team, adding invitees, and reporting on what got confirmed all run unsupervised. Deciding that a group has finished deciding does not.
Agent Capabilities
18 actionsEvents
6- Create Event Creates a scheduling event with one or more proposed dates, one or more places, and a set of invitees. The invitees receive an invitation to vote on the slots you proposed. Set the creator either by an existing Vyte user ID or by an email address. This is the operation that opens a group decision rather than closing one.
- List Events Retrieves the events in your organization, with optional filtering by title, status, creator, or invitee, and a Limit parameter for paging. Filter on status to pull just the confirmed or upcoming set, which is what reporting flows usually want.
- Get Event Retrieves one event in full by ID, including the proposed dates, the proposed places, every invitee, the slots each of them voted for, and the confirmation status. This is where a flow learns whether the group has actually converged.
- Update Event Changes an existing event's title, proposed dates, or places, altering only the fields you supply. Use it to add a candidate slot or fix a room. Locking in the final date and place is a different operation, and it is Confirm Event.
- Confirm Event Confirms an event by selecting one date and one place and moving its status to confirmed. When the event carries only a single proposed date or place, the corresponding ID is optional. This ends the voting, which is why it belongs behind a person.
- Cancel Event Cancels an event and notifies the invitees that the meeting will not take place. Vyte has no hard delete for events, so cancellation is the way to take one out of active scheduling. Treat it as an announcement rather than a cleanup step.
Invitees
2- Add Invitees Adds one or more people to an existing event, each with an email address and optionally a full name and phone number. Newly added invitees receive an invitation immediately, so this action reaches somebody's inbox the moment it runs.
- Remove Invitee Removes a single person from an event using their invitee ID. That ID is distinct from a Vyte user ID and is found on the invitee object returned by Get Event, so read the event first rather than reusing a user ID.
Availability
4- List Free Slots Returns the free time of one or more Vyte users, or a whole team, for a given duration inside a date range. Invitees are supplied by email, by user ID, or by team ID. This is the intersection a person would otherwise assemble by opening calendars one at a time.
- List Free Slots By Day Returns the same free time grouped by calendar day across a date range. Reach for it when the output is going to be rendered as a day by day picker or written into a message that a human will read down a column.
- Get Next Availability Returns the next available slots for one or more users or a team for a given appointment duration, starting from now. The right operation when the useful answer is soonest rather than best, such as replying to an inbound request within the hour.
- Get User Availability Reads a user's recurring weekly availability settings, including timezone, booking buffers, restrictions such as treating today or the past as busy, and the enabled slots for each weekday. Use it to explain why a slot search returned what it did.
Booking Pages
4- Get Booking Page Retrieves a booking page, which Vyte calls a vyteme, by its nickname. The nickname is the last part of the public booking URL, so john-doe in a page at vyte.in/john-doe. Returns the page message, its owner, and its customization settings.
- List User Booking Pages Lists the booking pages owned by a specific Vyte user. Each user can hold a primary page plus secondary pages for different appointment contexts, so this is how a flow finds the right one before reading its appointment types.
- List Appointment Types Lists the appointment types configured on a booking page. Each type is a bookable meeting option with its own duration, availability, and description, which makes this the catalog behind any self-serve booking flow.
- Get Appointment Type Retrieves one appointment type on a booking page by its handle, returning the full configuration including duration, message, description, and public visibility. Useful for confirming that the option you are about to offer is actually visible to the person you are offering it to.
Users
2- List Users Lists the Vyte users in your organization with their names, emails, and timezones. This is how a flow turns a name or an email held in another system into the user ID that the availability operations expect.
- Get User Retrieves one Vyte user in your organization by user ID, returning profile details such as name, emails, timezone, and language. Reach for it when a message needs to be written in somebody's language or a slot needs to be expressed in their timezone.
Frequently Asked Questions
What can FlowRunner do with Vyte?
FlowRunner agents can run Create Event, List Events, and Get Event in Vyte, plus 15 more actions.
Does connecting Vyte to FlowRunner require OAuth?
No. Vyte connects to FlowRunner with an API key, no OAuth flow required.
Can Vyte trigger a FlowRunner workflow automatically?
Vyte doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Vyte
$100 in credits. No card required. Connect in minutes.