Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Cisco Webex Meetings

Cisco Webex Meetings integration for Flows360 workflows.

CategoryCommunication
AuthenticationOAuth 2.0
Version0.1.0
Published scopes2 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Cisco Webex Meetings with Flows360

Cisco Webex Meetings integration for Flows360 workflows.

Use the Cisco Webex Meetings connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 2 triggers.

Available actions

  • Create Message
  • Create Room
  • Create Team
  • Find Message
  • Find room
  • Custom API Call

Available triggers

  • New room
  • New meeting

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Cisco Webex Meetings
  • Package: @activepieces/piece-webex@0.1.0
  • Exact artifact digest: sha256:2970021b8f5ad1564900d66998a9d1b991ee62fca9d1a0c7c8dbda5f5c2218bd
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Message (createMessage), Post a plain text or rich text message to a Webex room or send a direct message Classification: read.
  • Create Room (createRoom), Create a new Webex room (space). The authenticated user is automatically added as a member. Classification: read.
  • Create Team (createTeam), Create a new Webex team. The authenticated user is automatically added as a member. Classification: read.
  • Find Message (findMessage), Retrieve details for a specific message by message ID Classification: read.
  • Find room (findRoom), Retrieve details for a specific room by room id Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New room, webhook.
  • New meeting, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects8
Supported actions6
Triggers2

Authentication

Authentication method: OAuth 2.0

Required scopes

spark:allmeeting:schedules_read

Authentication profiles

connection · oauth2

OAuth scopes: spark:all, meeting:schedules_read

Supported objects

ObjectReadWriteNotes
Create Message Yes No Post a plain text or rich text message to a Webex room or send a direct message
Create Room Yes No Create a new Webex room (space). The authenticated user is automatically added as a member.
Create Team Yes No Create a new Webex team. The authenticated user is automatically added as a member.
Find Message Yes No Retrieve details for a specific message by message ID
Find room Yes No Retrieve details for a specific room by room id
Custom API Call Yes No Make a custom API call to a specific endpoint
New room Yes No webhook trigger declared by the pinned package.
New meeting Yes No webhook trigger declared by the pinned package.

Supported actions

Create Message · Read

Post a plain text or rich text message to a Webex room or send a direct message

create_message · Risk: low · Retry: safe

Inputs

  • messageType · string · Required, Choose between sending to a room or a direct message to a person
  • destination · object · Required
  • text · string · Required, The message to send
  • markdown · string · Optional, The message in Markdown format for rich text. If provided, text will be used as alternate text
  • parentId · string · Optional, The parent message ID to reply to (optional)
  • files · array · Optional, Public URLs to files to attach (only one file per message)
Create Room · Read

Create a new Webex room (space). The authenticated user is automatically added as a member.

create_room · Risk: low · Retry: safe

Inputs

  • title · string · Required, A user-friendly name for the room
  • description · string · Optional, The description of the room. Required if isPublic is true.
  • teamId · string · Optional, The ID for the team with which this room is associated (optional)
  • classificationId · string · Optional, The classificationId for the room (optional)
  • isPublic · boolean · Optional, Make the room public and discoverable within the org. Note: description is required if this is true.
  • isLocked · boolean · Optional, Set the space as locked/moderated. The creator becomes a moderator.
  • isAnnouncementOnly · boolean · Optional, Sets the space into announcement mode. Only moderators can post messages. Note: space must be locked (moderated) to enable this.
Create Team · Read

Create a new Webex team. The authenticated user is automatically added as a member.

create_team · Risk: low · Retry: safe

Inputs

  • name · string · Required, A user-friendly name for the team
  • description · string · Optional, The description of the team (optional)
Find Message · Read

Retrieve details for a specific message by message ID

find_message · Risk: low · Retry: safe

Inputs

  • messageId · string · Required, The unique identifier for the message
Find room · Read

Retrieve details for a specific room by room id

find_room · Risk: low · Retry: safe

Inputs

  • roomId · string · Required
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New room · Webhook

Triggers when a new room is created

New meeting · Webhook

Triggers when a new meeting is created.

Setup

Setup

  1. Add the Cisco Webex Meetings connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • spark:all
  • meeting:schedules_read
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-webex@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Cisco Webex Meetings connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-webex@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com