---
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.

On the MCP server the action runs through the app's default connection; to use
another, look up its ID with `list_zapier_connections` and pass it as
`connection_id`. On the CLI, pass the app, `write` and the action key, with
`--connection` (an ID from `zapier-sdk list-connections`) and `--inputs` as
JSON, as in `zapier-sdk run-action google-sheets write add_row`. Each
successful MCP tool call uses two tasks from the Zapier plan. A write reaches
real people and records: confirm the inputs first.

## 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, then confirm it runs.

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

Run `zapier-sdk run-action`.

Before doing anything else, make one read-only call to confirm access.

## Rules

- Ask the user before anything that sends messages, costs money, or changes data.
- Never print API keys.