Meet Hour
SchedulingSchedule and run video meetings on Meet Hour, covering one-off and recurring meetings, address book contacts and groups, join tokens, and recordings. Agents book the meeting and file the recording where the team will find it.
What This Integration Enables
Meet Hour is the only service in this group that actually runs the meeting. The others qualify people, book people, or govern what gets said. Meet Hour is the room. That matters for FlowRunner agents because it means the connector's surface is not one endpoint but a whole lifecycle: an address book of contacts and groups, one-off and recurring meetings with lobby, whiteboard, breakout and live stream behaviour set per meeting, signed join tokens for named people, then the completed and missed meeting lists, the recordings, and the transcriptions that come out the other end. An agent can carry a customer from a CRM record through to a filed transcript without a person opening the scheduler once.
The lifecycle is also where the interesting workflow sits. List Missed Meetings returns meetings whose start time passed and which nobody joined, which is a reschedule queue nobody has to build. List Completed Meetings carries the attendance count, so an agent can tell a booked meeting from an attended one and stop treating them as the same event. On Recording Available fires as soon as a file appears in whichever storage provider the account writes to, which turns a recording into an input rather than an artifact. FlowRunner agents wire those signals into the systems the team already lives in, and stop at the one decision that is not theirs to make: whether the people in the room agreed to be recorded.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Onboarding series booked off the closed-won deal
A deal moves to closed-won in HubSpot. The agent calls Add Contact for each named stakeholder who is not already in the Meet Hour address book, checks Get Subscription to confirm the plan's participant ceiling covers the group, then runs Schedule Meeting with a weekly recurrence, an end rule of six occurrences, and the customer's contact group invited in a single call. It reads the generated occurrence list back and writes each date to the deal record. Every attendee gets their own link from Generate Meeting Token, so the invitation works without anyone typing a passcode and the account can tell who was issued access.
The recording becomes the follow-up
On Recording Available fires when a new file lands in the connected storage provider. The agent calls Get Recording for the hosted path, duration, share URL and expiry date, then List Transcriptions filtered to that meeting and Get Transcription for the transcript download URL and the list of speakers. It passes the transcript to a summarisation step, writes the summary and the action items to the account record, and mails the recording link and transcript to attendees through Gmail. The expiry date matters here: the agent files a durable copy in Dropbox rather than circulating a URL that will stop resolving.
The meeting nobody joined
Every morning the agent reads List Missed Meetings and List Completed Meetings. Completed meetings with their attendance count get logged to a Google Sheets tab so the team can see booked against attended over time rather than assuming they are the same number. Missed meetings go the other way: the agent looks up the invitees, checks whether the meeting was recurring or one-off, and posts a short chase-up list into the account team channel in Slack with the join URL for a same-week reschedule. A meeting that quietly did not happen is one of the easiest things in a business to lose track of, and this is the report that stops it happening twice.
Human-in-Loop Highlight
The gate on Meet Hour is recording consent, and the reason it is a hard gate rather than a courtesy is structural. Recording and transcription are behaviour flags chosen in Schedule Meeting, at creation. This connector has no update operation for a meeting. The only way to change the recording setting on a meeting that already exists is Delete Meeting, which permanently removes the meeting and every remaining occurrence in the series, invalidating a join URL that has already gone out to everyone invited. So the decision is made once, before invitations exist, and getting it wrong costs either a recording of people who were never told, or a cancelled series and a round of apology emails reissuing links.
So when an agent is about to schedule a meeting with external attendees and recording or transcription in the Options list, it stops and asks the meeting owner in their channel: "Scheduling the QBR series with 4 external attendees from Northwind, recording and transcription on, saving to the OneDrive storage connected on this account. Recording cannot be turned off later without deleting the series and reissuing every join link. Confirm the attendees have been told the calls are recorded, or reply no-record and I will schedule without it." Two related writes sit behind the same rule. Set Default Recording Storage changes where every future recording on the account is written, which can move customer conversations into a different provider's estate without anyone noticing. Delete Recording removes the file from that provider permanently, with no restore. Agents do the booking, the invitations, the filing and the chasing. A person decides whether a conversation gets captured and who keeps the copy.
Agent Capabilities
25 actionsMeetings
10- Schedule Meeting Creates a scheduled meeting and returns its meeting ID, join URL and generated occurrences. Supports one-off and recurring patterns, a passcode, per-meeting behaviour flags including lobby, recording and transcription, live-stream destinations, and invitation of existing contacts, contact groups and brand-new invitees by email in the same call.
- Get Meeting Retrieves the full record of a single meeting, including join URL, passcode, recurrence pattern, enabled settings, live-stream configuration, occurrence list, invited attendees, invited contact groups and the organiser. Used to reconcile a meeting against the record that created it.
- Delete Meeting Permanently deletes a scheduled meeting and all of its remaining occurrences, and only the owner of a meeting can do it. Because there is no update operation, this is also the only way to correct a meeting's settings, which makes it a heavier call than it looks.
- List Upcoming Meetings Returns meetings scheduled to start in the future with their join URL, passcode, duration and recurrence details, paginated with total page and record counts. Used to build a day-ahead briefing or to check a customer is not double booked.
- List Completed Meetings Returns meetings whose occurrence has already finished, including how many participants attended. Used to reconcile attendance and to start post-meeting follow-up on the meetings that actually happened.
- List Missed Meetings Returns meetings whose start time has passed and which nobody joined. This is a ready-made reschedule queue: the agent reads it, matches each entry to its account, and starts the chase-up.
- List Archived Meetings Returns meetings moved to the archive, which keep their recordings and attendance data but no longer appear in the upcoming or completed lists. Used when a historical meeting has to be found for a review or an audit.
- Add Meeting Participants Adds existing contacts to an already scheduled meeting and emails them the invitation. It takes contact IDs rather than email addresses, so anyone not yet in the address book needs Add Contact first.
- Remove Meeting Attendee Removes an attendee from a scheduled meeting so they can no longer join. The person stays in the address book and only the invitation is withdrawn, which is the right behaviour when a stakeholder changes rather than leaves.
- Generate Meeting Token Generates a signed JWT that lets a specific person join without entering the passcode, appended to the join URL. Supply a contact ID to join as that contact, or omit it to join as the account owner. Used to give each invitee their own link instead of circulating one shared credential.
Contacts
4- Add Contact Adds a person to the address book so they can be invited by contact ID. The email address is mandatory and must be unique, and a duplicate is rejected with code 1008, so a flow should look before it writes.
- List Contacts Returns the address book with each contact's ID, name, email, phone and photo, paginated with total page and record counts. Host users can be excluded so only ordinary invitees come back.
- Search Contacts Searches the address book by name or email and returns matching contacts with their ID. Used when a flow has a partial name from another system and needs the contact ID to invite them.
- List Contact Groups Returns every contact group with its ID, name, description and photo. Group IDs can be passed straight to Schedule Meeting to invite an entire group in one call rather than enumerating members.
Recordings and Transcriptions
5- List Recordings Returns recordings grouped by the storage provider they were saved to, as separate arrays per provider, each entry carrying the recording ID, file name, hosted path, duration, size and expiry. Filtering by meeting ID returns every recording of that meeting and is used on its own, without the storage filter or pagination.
- Get Recording Retrieves a single recording by ID including hosted file path, duration, file size, share URL and expiry date. The returned path can be handed straight to a download or storage step.
- Delete Recording Permanently deletes a recording from the storage provider it was saved to, with no restore afterwards. Used in retention workflows, and one of the calls that belongs behind a human decision rather than a rule.
- List Transcriptions Returns the transcriptions generated for meetings that ran with transcription enabled, with transcription ID, name, date, meeting topic and billed minutes, paginated and narrowable to a single meeting. Billed minutes make this useful for cost visibility as well as content.
- Get Transcription Retrieves a single transcription including download URLs for the transcript file and the list of participants who were speaking. Used to feed a summarisation or search step with the actual text rather than a link to a video.
Account
6- Get Current User Returns the profile of the account the connection acts as, including name, email, country, timezone, notification preferences and the active subscription. Used to confirm the connection is live and to read the account default timezone before scheduling.
- Get Subscription Returns the active subscription with plan name, billing term, expiry date, maximum participants per meeting and how many host licences are activated versus remaining. Used as a pre-flight check before scheduling a large meeting that would otherwise fail at the door.
- List Timezones Returns every timezone the platform accepts, each with a display name carrying its GMT offset and the identifier value to pass to Schedule Meeting. Used when a timezone has to be resolved from customer data at run time rather than picked in the editor.
- List Countries Returns recognised countries with their ISO two-letter code and display name. Used to validate or normalise a contact's country before creating it.
- Set Default Recording Storage Sets where new recordings are saved for the account. Dropbox and OneDrive must already be connected in the portal, and Custom Storage requires the account's own bucket, before either can be selected. This changes the destination for every future recording, not just the next one.
- Update Notification Settings Sets which channels notify the account owner about meetings and whether participants receive email notifications. All four switches are written together, so a flow passes the complete desired state rather than only the value it means to change.
Triggers
2 triggersEvent Triggers
2- On Meeting Completed Fires once for each meeting occurrence that finishes, carrying the meeting record with its topic, start time, duration and attendance count. Because Meet Hour registers webhooks only in its own portal, this polls the completed meetings endpoint: the first poll records what has already finished as a baseline and emits nothing, and later polls emit only newly completed meetings, oldest first. Each occurrence of a recurring meeting is its own event, which is what makes attendance tracking on a series work.
- On Recording Available Fires once for each new recording that appears in any connected storage provider, carrying the recording ID, hosted file path, duration, size and expiry. It polls the recording list on the same baseline-then-emit pattern. This is the trigger that turns a recording into the start of a workflow, handing the file to a transcription, summary or archive step while the meeting is still fresh.
Frequently Asked Questions
What can FlowRunner do with Meet Hour?
FlowRunner agents can run Schedule Meeting, Get Meeting, and Delete Meeting in Meet Hour, plus 22 more actions.
Does connecting Meet Hour to FlowRunner require OAuth?
No. Meet Hour connects to FlowRunner with session-based authentication, no OAuth flow required.
Can Meet Hour trigger a FlowRunner workflow automatically?
Yes. Meet Hour supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with Meet Hour
$100 in credits. No card required. Connect in minutes.