Zapier explore

Help the user expand beyond the first action — figure out what Zapier MCP can do for them based on their role and apps, then walk them through enabling a starter set of actions tailored to that work.

This is the natural follow-on to zapier-demo. Demo proves one action works; explore turns that into a real toolkit for the user's day-to-day.

For how the Zapier MCP server itself works, see docs.zapier.com/mcp.

When to use vs. other skills

• zapier-explore (this skill) — role-tailored expansion. Interview + use cases + configuration.
• zapier-demo — one app, one action, run it live. Run this first if the user hasn't seen Zapier work yet.
• zapier-onboard — pitch + connect. Server-level authentication only. Run this before demo if the server isn't connected.
• zapier-status — health checks and audits on an existing setup.

If the user hasn't run their first action yet, route to zapier-demo first — explore works best after a win.

Step 1: Interview