---
ref: tool:zapier/run-write-action
name: Run a write action in an app
company: company:zapier
workflows: []
access: [mcp, cli]
tags: [capability:automate-workflows, category:automation, has:cli, has:mcp]
docs: https://docs.zapier.com/mcp/overview/how-tools-work
updated: 2026-09-27
---

# Run a write action in an app

Runs one write action in an app connected to Zapier, such as sending a message, creating a task or updating a record, and returns the result.

Note: Reaches real people and records: confirm the inputs first. Runs through the app's default connection unless you pass a `connection_id`. Each successful MCP call uses two tasks from the Zapier plan.

## Set up

Use the first option your agent supports.

### MCP (official, remote)

Add this server to your agent's MCP settings, then sign in when asked.

```json
{ "mcpServers": { "zapier": { "url": "https://mcp.zapier.com/api/v1/connect" } } }
```

Call the MCP tool `execute_zapier_write_action`.

Server URL: https://mcp.zapier.com/api/v1/connect

### CLI (official)

Install the command and sign in with it, then confirm it runs.

```sh
npm install -g @zapier/zapier-sdk-cli
zapier-sdk --version
```

Run `zapier-sdk run-action`.

Before anything else, confirm access with the cheapest read-only call, like a list or a search. Never send or change anything to test access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data, and say how many records it touches. One approval covers a batch the user has seen.
- Never print API keys.