Cisco Webex Trigger

Trigger workflow from Cisco Webex events

Overview

Starts a workflow when events occur in Cisco Webex (messages, meetings, memberships, rooms, recordings, attachment actions). Registers a webhook with the Webex API and verifies incoming payloads using HMAC-SHA1 signature. Supports resource-specific event filtering and optional data resolution for attachment actions.

Category: Communication
Tool Name: cisco_webex_trigger
Version: 1

Appearance: Icon: lucide-Video | Color: #00bceb

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Cisco Webex credentials. See the Credentials Guide for setup instructions.

Resources

Resource	Value
[All]	all
Attachment Action	attachmentAction
Meeting	meeting
Membership	membership
Message	message
Recording	recording
Room	room

Parameters

Parameter	Type	Required	Default	Description
Event	options	Yes	—	The event to listen for on the selected resource.
				Options: created, deleted, updated, started, ended, all (shown as * — every event on the resource)
Resolve Data	boolean	No	true	By default the response only contains a reference to the data the user inputted. If enabled, it will resolve the data automatically. (shown when Resource is attachmentAction)
Filters	collection	No	{}	Narrows which events Webex sends. Add only the fields available for your Resource and Event combination.
— Has Files	boolean	No	false	Whether to limit to messages which contain file content attachments. (shown when Resource is message and Event is created, deleted)
— Is Locked	boolean	No	false	Whether to limit to rooms that are locked. (shown when Resource is room and Event is created, updated)
— Is Moderator	boolean	No	false	Whether to limit to moderators of a room. (shown when Resource is membership and Event is created, updated, deleted)
— Mentioned People	string	No	—	Limit to messages which contain these mentioned people, by person ID. Accepts ‘me’ as shorthand for your own person ID. Separate multiple values with commas. (shown when Resource is message and Event is created, deleted)
— Message ID	string	No	—	Limit to a particular message, by ID. (shown when Resource is attachmentAction and Event is created)
— Owned By	string	No	—	Limit to meetings owned by a particular person. (shown when Resource is meeting)
— Person Email	string	No	—	Limit to a particular person, by email. (shown when Resource is membership and Event is created, updated, deleted)
— Person Email (Message)	string	No	—	Limit to a particular person, by email (for messages). (shown when Resource is message and Event is created, deleted)
— Person ID	string	No	—	Limit to a particular person, by ID (for attachment actions). (shown when Resource is attachmentAction and Event is created)
— Person ID (Membership)	string	No	—	Limit to a particular person, by ID (for memberships). (shown when Resource is membership and Event is created, updated, deleted)
— Person ID (Message)	string	No	—	Limit to a particular person, by ID (for messages). (shown when Resource is message and Event is created, deleted)
— Room ID	string	No	—	Limit to a particular room, by ID (for attachment actions). (shown when Resource is attachmentAction and Event is created)
— Room ID (Membership)	string	No	—	Limit to a particular room, by ID (for memberships). (shown when Resource is membership and Event is created, updated, deleted)
— Room ID (Message)	string	No	—	Limit to a particular room, by ID (for messages). (shown when Resource is message and Event is created, updated)
— Room Type	options	No	—	Limit to a particular room type (for messages). (shown when Resource is message and Event is created, deleted)
				Options: direct, group
— Type	options	No	—	Limit to a particular room type (for rooms). (shown when Resource is room and Event is created, updated)
				Options: direct, group

Output Data

Each delivered event produces one output item describing the Webex webhook and what changed:

• resource — the resource the event is about, in Webex’s plural form, e.g. messages
• event — the event, e.g. created
• data — the object that changed; for a message, fields such as id, roomId, roomType, personId, personEmail, created
• actorId — the person who caused the event
• id, name, targetUrl, status — the Webex webhook that delivered the event
• orgId, createdBy, appId, ownedBy — Webex ownership metadata
• _trigger — always cisco_webex_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — {resource}.{event}, e.g. messages.created

Reference the payload downstream by expression, e.g. {{ $json.data.roomId }} or {{ $json.actorId }}.

Usage Examples

• trigger workflow when a new Webex message is posted
• start workflow when a Webex meeting starts or ends
• listen for new Webex room membership changes
• receive Webex attachment action submissions
• monitor Webex recording events

Example Configuration

React when a meeting starts:

{
  "type": "cisco_webex_trigger",
  "parameters": {
    "resource": "meeting",
    "event": "started"
  }
}

Every message event:

{
  "type": "cisco_webex_trigger",
  "parameters": {
    "resource": "message",
    "event": "all"
  }
}

Attachment actions with data resolution:

{
  "type": "cisco_webex_trigger",
  "parameters": {
    "resource": "attachmentAction",
    "event": "created",
    "resolveData": true
  }
}

Filtered message events:

{
  "type": "cisco_webex_trigger",
  "parameters": {
    "resource": "message",
    "event": "created",
    "filters": {
      "hasFiles": true,
      "roomType": "group",
      "personEmailMessage": "user@company.com"
    }
  }
}

Membership events in one room:

{
  "type": "cisco_webex_trigger",
  "parameters": {
    "resource": "membership",
    "event": "created",
    "filters": {
      "roomIdMembership": "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0",
      "isModerator": false
    }
  }
}

Recording events:

{
  "type": "cisco_webex_trigger",
  "parameters": {
    "resource": "recording",
    "event": "created"
  }
}

Every event on every resource:

{
  "type": "cisco_webex_trigger",
  "parameters": {
    "resource": "all",
    "event": "all"
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

Entry point that fires when a Cisco Webex event occurs (messages, meetings, memberships, rooms, recordings, attachment actions). Verifies the webhook signature and outputs the event payload for downstream processing.

Important Notes

• Resolve Data is only available when the Resource is attachmentAction.
• Each filter field is available only for a specific Resource and Event combination — check the gate on each row before adding it.
• When Event is all, filters that require a specific event value (created, updated, deleted) are not available.
• Use roomIdMessage (not roomId) to filter messages by room; roomId applies to attachmentAction only.
• Use personEmailMessage (not personEmail) to filter messages by sender email; personEmail applies to membership only.
• Use roomIdMembership (not roomId) to filter memberships by room.
• Resource all fires on any event from any supported resource type.
• The node’s Resource values are singular (message, meeting), but Webex reports the plural form in the payload’s resource field (messages, meetings). Match on _webhookEvent or on the plural value when branching downstream.
• Every delivery is signature-checked against a secret generated when the webhook is registered, so unsigned or mismatched requests are rejected.