List Webhooks

webex.list_webhooks
ActionChat & messagingconnection required

Calls the Cisco Webex API with the connection's credentials.

List the Webex webhooks this connection created.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Cisco Webex
Secret shape
the Webex access token, or {"access_token": "…"}
Resolved by
config.connection_id, else node.connection_id

Configuration

1 field, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
max_results
How many webhooks to ask for.
numberNo100≥ 1—

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "max_results": 100
}

Output

One shape.

result

FieldTypeExample
items[].id
The webhook id — pass it to webex.delete_webhook.
string—
items[].name
The webhook's name.
string—
items[].target_url
The URL Webex POSTs each event to.
string—
items[].resource
The resource it watches, e.g. messages.
string—
items[].event
The event it watches, e.g. created.
string—
items[].filter
The filter narrowing it, e.g. roomId=….
string—
items[].status
'active', or 'inactive' after Webex gave up on the URL.
string—
items[].created
When the webhook was created (ISO-8601).
string—
count
How many rows this page carries.
number—
{
  "count": 0,
  "items": [
    {
      "created": "",
      "event": "",
      "filter": "",
      "id": "",
      "name": "",
      "resource": "",
      "status": "",
      "target_url": ""
    }
  ]
}

Notes

  • Only the webhooks created by this token are listed.
  • One page only: Webex paginates with an RFC 5988 Link header, which this node does not follow — narrow the filters or raise max_results instead.

See List Webhooks run in a workflow.

In a technical demo we add the Cisco Webex connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.