Webvizio

@Webvizio show me all active webhook subscriptions for our design feedback workflow

Found 3 active webhook subscriptions in your Webvizio account: (1) 'Design Review Notifications' targeting https://slack.example.com/hooks/review, subscribed to comment.created and issue.resolved events; (2) 'Client Approval Tracker' targeting https://zapier.example.com/webhooks/catch/abc123, subscribed to approval.requested events; (3) 'Bug Report Pipeline' targeting https://api.linear.app/webhooks/inbound, subscribed to issue.created with priority:high filter. All subscriptions show 'active' status with last delivery timestamps within the past 24 hours.

This read-only query helps teams audit their integration landscape before adding or removing webhooks. Requires an API key with webhook:read scope. The MCP returns subscription metadata but does not expose webhook secrets or payloads — useful for discovering what's wired up, less useful for debugging delivery failures without additional vendor dashboard access.

@Webvizio which webhooks are sending events to our Slack channel, and are any of them failing?

Two webhooks target Slack endpoints: 'Design Review Notifications' (https://slack.example.com/hooks/review) shows 47 successful deliveries in the past week with no failures, while 'Urgent Feedback Alerts' (https://slack.example.com/hooks/urgent) has 3 failed deliveries in the last 48 hours, last attempted 6 hours ago. The failed webhook is subscribed to comment.created events with an urgency:critical filter. Webvizio's dashboard shows HTTP 410 Gone responses, suggesting the Slack webhook URL may have been regenerated.

This example pairs the MCP's list capability with AI reasoning to filter and diagnose integration health. The MCP surfaces delivery status but cannot automatically fix broken endpoints — teams still need to update webhook URLs manually in Webvizio's settings. Delivery history depth depends on your Webvizio plan tier.

@Webvizio compare our current webhook setup to last month's audit and flag any new subscriptions we didn't document

Comparing current webhook list to the audit snapshot from March 15: Found 1 new subscription not in the previous audit — 'QA Sign-off Tracker' created April 2, targeting https://api.notion.so/v1/webhooks/inbound, subscribed to approval.completed events. This webhook was added by user sarah@example.com. The two previously documented webhooks ('Design Review Notifications' and 'Client Approval Tracker') remain active with unchanged configurations. No subscriptions were removed since the last audit.

This synthesis example assumes you've stored a previous webhook list in the Space's context or files. The MCP only provides current state — historical comparison requires the AI to diff against prior data you supply. Useful for security audits or onboarding reviews, but the MCP cannot enforce webhook governance policies or block unauthorized additions.

When you need to audit Webvizio webhooks before a sprint

A 3-person design team runs weekly sprints with Webvizio for visual feedback. Before each sprint kickoff, the lead designer needs to confirm which webhooks are firing into Slack, Linear, and their internal dashboard. The list-subscriptions tool solves this in 10 seconds: pull the active webhook config, verify endpoints, catch stale integrations before they spam the wrong channel. This works if your team has under 20 webhooks total. Beyond that threshold, you're managing webhook sprawl at a scale where a dedicated integration platform (Zapier, Make) is the better call. If your sprint ritual includes a 2-minute webhook check, this MCP keeps that check inside Switchy instead of logging into Webvizio's UI.

Use this MCP when offboarding a Webvizio client project

A 5-person agency wraps a 3-month website project and needs to hand off the Webvizio workspace to the client's internal team. The last step: document which webhooks are live so the client knows what's firing into their Slack and project tracker. The list-subscriptions tool exports the full webhook roster in one query, no UI clicking required. This is the right move if you're offboarding 2-4 clients per quarter and Webvizio is part of your standard stack. If you're offboarding weekly or managing dozens of concurrent projects, you need a CRM or project-handoff system that automates this across all tools, not just Webvizio. For occasional, high-touch handoffs, this MCP turns a 10-minute admin task into a 30-second Switchy query.

When a customer reports missing Webvizio notifications

A 2-person support team at a SaaS company gets a ticket: a customer's Webvizio comments aren't reaching their Slack channel. The support agent needs to verify the webhook config without escalating to engineering. The list-subscriptions tool lets the agent pull the customer's webhook setup, confirm the endpoint URL, and spot the misconfigured subscription in under a minute. This works if your support team handles 5-15 Webvizio-related tickets per month and the fix is usually a config check, not a code change. If you're debugging webhooks daily or across multiple feedback tools, you need centralized webhook monitoring (like Hookdeck or Svix). For low-volume, high-context support, this MCP keeps the diagnosis inside Switchy's shared workspace where the whole team can see the resolution.