Description:

This step creates a Cisco Webex meeting using a configured OAuth provider.

The Create Webex Meeting workflow step connects to a Cisco Webex account using a configured OAuth provider, creates a meeting with the specified meeting details, invites attendees, and stores the generated meeting information—including the meeting ID, meeting URL, and complete response JSON—in FlowWright Variables or Global Variables.

The step supports configuring the meeting name, password, scheduled start date and time, duration, agenda, time zone, and attendee email addresses. After the meeting is successfully created, the generated meeting details can be used by downstream workflow steps to send notifications, update business records, integrate with external systems, or automate meeting lifecycle management.

This step provides an efficient way to automate meeting scheduling as part of business workflows such as approval processes, onboarding, customer appointments, project reviews, and support sessions.

The step supports:

• Cisco Webex OAuth authentication
• Automatic meeting creation
• Meeting scheduling
• Optional meeting passwords
• Time zone selection
• Agenda configuration
• Multiple attendee invitations
• Storage of meeting metadata
• Integration with FlowWright workflow automation

This step can be used for:

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

Usage:

The Create Webex Meeting step is typically placed after approval, scheduling, customer registration, onboarding, or case management activities where an online meeting must be automatically created.

The workflow authenticates with Cisco Webex, creates the meeting using the configured meeting details, invites the specified attendees, stores the meeting information, and makes the generated values available to downstream workflow steps.

A typical workflow might look like this:

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

• Send meeting invitations
• Update CRM systems
• Create calendar events
• Store meeting metadata
• Notify participants
• Generate reports
• Continue workflow execution

The selected OAuth provider must already be configured and authorized before this step is executed.

Prerequisite:

Navigate to the Integration - Connections page. Create a new OAuth connection string as shown below. 

The OAuth connection string for Webex is provided for reference. 

Example:

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

• Create a new process definition named “clsWebexMeetingDef” and open it in designer mode.
• Drag a “clsWebexMeeting" step onto the canvas. 
• Connect the dots from the “Start” step to the “clsWebexMeeting" steps, as shown above. 
• Define a variable or a global to store the result.
• Click the "clsWebexMeeting" step to configure its "Required" properties. Provide a name for the step. Select the Webex OAuth connection string from the drop-down list. Enter the meeting description. Set the meeting date and time. Enter the meeting duration. Enter the participants' email IDs. Provide a variable or global reference to store the meeting URL. Provide a variable or global reference to store the meeting JSON event as a JSON object. 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 "clsWebexMeeting" step to configure its "Optional" properties. Enter the meeting password. Enter the meeting agenda description. Select the meeting time zone. Provide the variable or global reference to store the Webex meeting ID. Then 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 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 Webex Meeting step, FlowWright authenticates with Cisco Webex using the selected OAuth provider, creates the meeting, invites the specified participants, and stores the generated meeting information. If the operation completes successfully, the workflow follows the True return path. If authentication fails, the OAuth provider is invalid, attendee information is incorrect, required meeting properties are missing, or the Webex service returns an error, the workflow follows the False return path. Click the process step to view its properties. The step should successfully create the meeting, populate the configured Variables or Global Variables with the meeting information, and return True upon completion.

Tips:

• Configure and validate the OAuth provider before using this step in production workflows.
• Use descriptive meeting names so attendees can easily identify the meeting's purpose.
• Select the correct time zone to ensure invitations are scheduled accurately across different regions.
• Use workflow variables to dynamically generate meeting names, agendas, and attendee lists.
• Store the complete JSON response to simplify troubleshooting and enable access to additional meeting metadata.
• Store the meeting URL in a Global Variable if it will be referenced by multiple downstream workflow steps.
• Use the True and False return paths to implement appropriate success and exception handling.
• Combine this step with Send Email, Generate PDF, Create Calendar Event, Update Variables, REST Call, Teams Notification, or Approval workflow steps to automate end-to-end meeting scheduling processes.

Notes:

• A valid Cisco Webex OAuth provider must be configured before this step can create meetings.
• The selected OAuth account must have permission to schedule Webex meetings.
• Participant email addresses should be valid and properly formatted.
• The Meeting ID, Meeting URL, and complete JSON response can be stored independently for downstream processing.
• The Meeting Password and Agenda properties are optional.
• Authentication failures, scheduling conflicts, invalid attendee information, network connectivity issues, or Webex API errors may cause the step to return False.
• This step creates a new Webex meeting but does not modify 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:

• OAuth provider selection
• Meeting name
• Start date and time
• Duration
• Time zone
• Attendee email addresses
• Variable or Global Variable mappings
• Cisco Webex account permissions
• Environment-specific settings

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

Click here to download the sample file.