Zapier demo

Walk a new user through the smallest possible first win — one app, one read action, one prompt that actually runs. The whole flow should feel quick: a few minutes from "I'm curious" to "oh, that worked."

This is the natural next step after zapier-onboard for users who want to see Zapier work before configuring a full toolkit.

When to use vs. other skills

• zapier-demo (this skill) — one app, one action, immediate demo. Fastest path to "oh, this works."
• zapier-onboard — pitch + connect + diagnose. Run this first if the server isn't connected yet.
• zapier-explore — role-tailored expansion. Run this after demo to set up a full toolkit for the user's role.
• zapier-status — health checks and audits on an existing setup.

If the user says "show me," lean here. If they haven't connected the server yet, route to zapier-onboard first.

Step 1: Confirm the server is connected

Inspect available Zapier MCP tools. If none exist, the server isn't authenticated yet — authenticate first via mcp_auth or the client's MCP settings (same pattern as zapier-onboard's connection step). Don't continue until at least the configuration tools are available.