Description:

This step creates a Google Meet event using a configured Google OAuth provider.

The Create Google Meet Event workflow step authenticates using a configured Google OAuth provider, creates a Google Calendar event with an associated Google Meet conference link, invites one or more attendees, and stores the meeting information in FlowWright Variables or Global Variables.

During execution, the step creates the calendar event with the specified meeting name, start date and time, duration, time zone, description, and attendee list. The generated Google Meet link, Google Calendar event ID, and complete JSON response can be stored for use by later workflow activities.

This step provides an efficient way to automate meeting scheduling as part of approval workflows, onboarding processes, project kickoffs, customer meetings, service requests, training sessions, and business process automation.

The step supports:

• Google OAuth authentication
• Google Meet meeting creation
• Google Calendar event creation
• Multiple attendee invitations
• Configurable meeting duration
• Configurable time zone
• Meeting descriptions
• Storage of Meeting URL
• Storage of Event ID
• Storage of complete JSON response
• Integration with FlowWright workflow automation

This step can be used for:

• Customer meetings
• Project kickoff meetings
• Employee onboarding
• Approval meetings
• Training sessions
• Support appointments
• Business process automation

Usage:

The Create Google Meet Event step is typically placed before notification, approval, interview, onboarding, or scheduling activities that require an online meeting.

The workflow authenticates with Google, creates the calendar event, generates the Google Meet conference link, invites attendees, stores the returned meeting information, and continues processing.

A typical workflow might look like this:

Once the meeting has been created, later workflow steps can:

• Send email invitations
• Update CRM systems
• Create calendar reminders
• Store meeting information
• Notify participants
• Generate reports
• Continue workflow execution

A valid Google OAuth provider must be configured before this step is executed.

A sample Google OAuth configuration is provided here for reference.

Example:

Let’s build and execute the “clsGoogleMeetDef” example.          

• Create a new process definition named “clsGoogleMeetDef” and open it in designer mode. 
• Drag a “clsGoogleMeet” step to the canvas. 
• Connect the dots between the “Start” and “clsGoogleMeet” steps, as shown above.  
• Click the “clsGoogleMeet” step to configure its “Required” properties. Provide a name for the step. Select the OAuth provider from the dropdown list. Provide the event name. Configure the event start date and time, as well as the duration (in minutes). Select the event time zone from the dropdown list. Provide the recipient email IDs, separated by semicolons. Provide a variable or a global reference to store the meeting link and the JSON result. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

• Click the “clsGoogleMeet” step to configure its “Optional” properties. Enter the event description. Enter a variable or global reference to store the event ID. Click the Save button. 

• The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. This is achieved by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the Process Definition. Create a new Process Instance and execute it. When the workflow reaches the Create Google Meet Event step, FlowWright authenticates using the selected OAuth provider, creates the Google Calendar event, generates the Google Meet conference link, invites the specified attendees, and stores the returned information in the configured Variables or Global Variables. If the operation completes successfully, the workflow follows the True return path. If authentication fails, the OAuth provider is invalid, attendee information is invalid, or the Google Meet event cannot be created, the workflow follows the False return path. Click the process step to view its properties. The step should successfully create the Google Meet event, populate the configured Variables or Global Variables with the meeting information, and return True upon completion.

Tips:

• Configure and test the Google OAuth provider before using this step.
• Verify that attendee email addresses are valid.
• Select the appropriate time zone to avoid scheduling errors for attendees in different regions.
• Store the generated Meet link so it can be included in workflow notifications or documents.
• Store the complete JSON response when downstream workflow steps require additional meeting information.
• Use workflow variables to dynamically populate meeting names, dates, durations, and attendee lists.
• Use the True and False return paths to implement appropriate success and exception handling.
• Combine this step with the Send Email, Create Task, REST Call, Update Variables, Teams Notification, or Calendar Integration workflow steps to automate complete meeting-scheduling workflows.

Notes:

• A valid Google OAuth provider must be configured before this step can create Google Meet events.
• The executing workflow must have permission to access the configured Google account.
• The meeting is created as a Google Calendar event with an associated Google Meet conference link.
• Multiple attendees can be invited using the configured email list.
• The generated Google Meet link, Event ID, and JSON response can be reused throughout the workflow.
• Authentication failures, invalid attendee information, or unavailable Google services may cause the step to return False.
• This step creates a new Google Calendar event but does not update or delete existing meetings.
• The workflow should include appropriate handling for both True and False return paths.

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition page.

Note: Verify and complete any missing configuration after importing the sample, including:

• Google OAuth Provider
• Event Name
• Meeting Date and Time
• Duration
• Time Zone
• Attendee Email Addresses
• Meet Link Variable mapping
• Event ID Variable mapping
• JSON Result Variable mapping
• Environment-specific settings

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.