Zapier SDK

Set up the Zapier SDK for me. Before installing anything:

- Run `pwd` and tell me the current folder.
- Ask whether to install here or somewhere else.

End with: "Should I set up here, or do you want to point me at a different directory?" Then STOP and wait. If I name a different directory, `cd` there first, creating it with `mkdir -p` if needed. If my reply is ambiguous, use the current directory.

After I confirm the directory, work through these steps one at a time. Run each command in the terminal, report what happened, then continue.

1. Detect the package manager.
   Check for pnpm-lock.yaml, yarn.lock, bun.lockb, or package-lock.json. If one exists, use that manager for every install command. If none exist, use npm.

2. Ensure a project exists.
   - If package.json exists, use the project as-is and remember this for step 9.
   - If package.json is missing, create one: npm init -y

3. Check Node.js is installed at version 20 or higher: node -v
   - If Node is missing, tell me to install it from https://nodejs.org or run brew install node, then stop.
   - If Node is older than 20, tell me to upgrade it, then stop.

4. Install the SDK: npm install @zapier/zapier-sdk
   - An EPERM error on ~/.npm/_cacache usually means the command sandbox is blocking npm cache writes, not that file permissions are broken.

5. Install dev dependencies: npm install -D @zapier/zapier-sdk-cli @types/node typescript tsx

6. Ask whether to install the optional Zapier SDK skill for agent context.
   Say: "Do you want me to install the optional Zapier SDK skill for extra agent context? It is not required for SDK setup." Then STOP and wait.
   - If I clearly say yes, run: npx skills add zapier/sdk -y
   - Otherwise, skip this step and continue.

7. Authenticate with Zapier.
   First ask: "Are you signing up or logging in? Am I running on your local machine with a browser, or in a remote/headless environment like Telegram or Discord?" Then STOP and wait. Do not infer the environment.
   - If I do not have a Zapier account and we are in a remote environment like Telegram or Discord, run: npx zapier-sdk signup --non-interactive --headless
   - If I do not have a Zapier account and you are running on my machine, run: npx zapier-sdk signup --non-interactive
   - If I already have a Zapier account and we are in a remote environment like Telegram or Discord, run: npx zapier-sdk login --non-interactive --headless
   - If I already have a Zapier account and you are running on my machine, run: npx zapier-sdk login --non-interactive
   - If unsure, ask whether to sign up or log in, and whether you are local or remote, before running any auth command.
   - Use --headless when auth must happen through a browser outside this terminal. Show me the printed URL and pass the final OAuth callback URL back to the waiting command when I provide it.
   - Browser signup/login opens a browser. A permissions or sandbox error usually means credentials could not be written to disk.
   - If authentication fails for another reason, try once more.
   - After authentication succeeds, confirm the email from the CLI output.

8. List my connected apps: npx zapier-sdk list-connections --owner me --json 2>/dev/null | head -n 1000
   - Show only the first 10 results as a markdown table with columns: ID, App Key, Expired. Do not show Title.
   - Tell me how many total connections there are. If there are more than 10, say you are only showing the first 10.
   - The page size is 100. If exactly 100 connections return, note that more may exist, but do not fetch more pages.
   - If the list is empty, tell me to connect at least one app at https://zapier.com/app/assets/connections and come back.

9. If this was an existing project from step 2, scan the codebase and suggest 2-3 concrete ways to integrate the Zapier SDK. Reference real files and patterns you find, for example an API route, tool registry, backend service, or sync script. If this is a fresh project, skip this step.

When setup is done, tell me I am ready and explain:

Zapier has pre-built connectors for 9,000+ apps, including Slack, Google Sheets, Salesforce, GitHub, and thousands more. The SDK and CLI expose that integration layer to code, so you do not have to build OAuth, token refresh, retries, or each app API yourself. My existing Zapier connections are authenticated and ready to use.

- **TypeScript SDK:** for production integrations, backend services, scheduled workflows, and agent tools. It is type-safe, handles token refresh and retries, and uses the same app keys, action keys, and input shapes discovered through the CLI. SDK reference: https://docs.zapier.com/sdk/reference
- **CLI:** for exploration and ad-hoc actions. Use it to inspect apps, fields, and actions, then run one-offs from a terminal or agent. CLI reference: https://docs.zapier.com/sdk/cli-reference

**Want to run a quick test?**

If I have a Slack connection, offer to send me a DM on Slack using the SDK. Describe what will happen and end with: "Want to run this quick test?" Then STOP and wait. Do not output anything else. If I do not have a Slack connection, skip the test.

Only proceed with the test if my reply is clearly affirmative, such as "yes" or "go ahead". If ambiguous, skip the test and continue.

When I say yes, create src/zapier-slack-test.ts with code that:

1. Looks up my Slack user by email using sdk.runAction("slack", "search", "user_by_email", { connectionId: ID, inputs: { email: "ZAPIER_EMAIL" } }).
2. Sends a DM to myself using sdk.runAction("slack", "write", "direct_message", { connectionId: ID, inputs: { channel: "USERNAME", text: "Hello via Zapier SDK" } }).

Replace ID, ZAPIER_EMAIL, and USERNAME with real values from earlier steps. Run it with npx tsx src/zapier-slack-test.ts. If user_by_email fails, ask for my Slack email and try again.

After the test completes, is skipped, or there is no Slack connection:

- Pick 1-3 apps from the connections table and show commands I can use to explore their actions, such as: npx zapier-sdk list-actions APP_KEY
- Do not run those commands.
- Suggest 3 specific ideas based on my connected apps. Each idea should read from one app, optionally process data, and write to another. Do not suggest event-driven workflows. Keep each idea to one sentence. Example: "pull in-progress Jira issues and DM yourself a summary on Slack".