Bug: `webhooks list` and `integrations list` return empty despite existing webhooks/integrations

[jmsundar]

Summary

cx webhooks list and cx integrations list return an empty result even when outgoing webhooks / integrations exist in the tenant. Other commands that hit the same data work correctly, so this looks like a bug in the list handlers (or the list endpoint/response parsing) rather than missing data or a permissions issue.

Version

cx 0.1.7

Steps to reproduce

$ cx webhooks list -o json
Fetching webhooks...
[]

$ cx webhooks list
Fetching webhooks...
No webhooks found.

$ cx integrations list -o json
[]

Expected

A list of the configured webhooks/integrations.

Evidence the data exists

cx webhooks types reports non-zero counts for the same tenant/profile:

$ cx webhooks types
...
      - type: GENERIC
        label: Generic webhook
        count: 3
      - type: SEND_LOG
        label: Send log
        count: 2
      - type: AWS_EVENT_BRIDGE
        label: AWS EventBridge
        count: 1

And cx webhooks get <id> resolves individual webhooks fine (by external/integration id):

$ cx webhooks get 13639 -o json
{ "webhook": { "id": "…", "type": "GENERIC", "name": "…", "externalId": 13639, … } }

For cross-reference, the Coralogix MCP manage_webhooks list action returns all 6 webhooks for the same tenant, confirming the data is present and listable via the API.

Impact

list is the natural way to discover webhook/integration IDs. With it returning empty, there is no CLI-only way to enumerate webhooks — you have to already know each ID to use get. This blocks scripting/automation that needs to find a webhook by name.

[OmriGabai]

Thanks for raising.
The integrations list is already fixed and live
re 'webhooks list' - working on it