You are here:
Retrieves available meeting times for a specified lead, contact, or person account based on the record owner’s schedule. Inbox is required to use this action. This action is available in flows running API version 66.0 and later.
| Available in: Lightning Experience |
| View supported editions. |
In Flow Builder, add an Action element to your flow. In the Action panel, search for Get Available Meeting Times, and then select Get Available Meeting Times.
Use values from earlier in the flow to set the inputs for the action.
| Field | Description |
|---|---|
| Date | Required. The attendee’s first desired meeting date. |
| Meeting Description | Optional. A description for the meeting. |
| Meeting Name | Optional. The name of the meeting. |
| Meetings Per Day | Required. The maximum number of Meeting times to retrieve per day. |
| Number Of Meeting Times | Required. The total number of meeting times to retrieve. |
| Start Time | Optional. The attendee’s first desired meeting start time, in UTC and 24-hour HH:MM:SS format. |
| Target Id | Required. The ID of the target. It can be a lead ID, contact ID, or the person contact ID for a person account. |
| Time Zone | Required. The time zone identifier for the meeting (for example, America/Los_Angeles). |
| Field | Description |
|---|---|
| Epoch Times | The start and end times of the meeting time slots, measured in milliseconds since the Unix epoch (January 1, 1970, 00:00:00 UTC). |
| Error Code | The error code when an error occurs. |
| Error Message | The error message returned when an error occurs. |
| Meeting Request Id | The ID of the meeting request. |
| Time Slots | The meeting slot start and end dates and times. |
The Get Available Meeting Times action is primarily used with Agentforce Sales. This action requires Inbox to be enabled. All flows are supported, including screen flows, schedule-triggered flows, and record-triggered flows.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.