Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
zapier logo

Zapier

Zapier doesn't run MCP directly, but Dock integrates via Zapier Webhooks (inbound) and HTTP Zap actions (outbound). Use the webhook pattern to fan events out of Dock; use HTTP actions to append and update rows from any Zap.

Client
Zapier
Automation. Webhooks + HTTP Zap actions for REST.
HTTP JSON-RPC (streamable-http)
Dock MCP
trydock.ai/api/mcp
37 tools · OAuth 2.1 + DCR · Bearer
Auth path
1
Mint a dk_ key in Dock Settings → API keys.
2
Paste it as Authorization: Bearer dk_… in the client config.
3
Client calls Dock MCP directly on every request.

Prerequisites

  • Zapier account.
  • A Dock dk_ key.
Inbound (Dock → Zapier)
Create a "Catch Hook" Webhook trigger in Zapier, copy the URL, subscribe it from Dock Settings · Webhooks.
Outbound (Zapier → Dock)
Add an HTTP action. Method POST. URL https://trydock.ai/api/workspaces/<slug>/rows. Headers: Authorization: Bearer dk_....
HTTP action bodyjson
{
  "data": {
    "title": "{{trigger.subject}}",
    "status": "drafted"
  }
}

Troubleshooting

Symptom
Fix
Webhook sets up but never fires
Check /settings?tab=webhooks in Dock. The delivery log shows every outbound attempt and the Zapier response.

Frequently asked questions

How do I connect Dock to Zapier?
Add Dock as a remote MCP server in Zapier. Either let Zapier's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Zapier's MCP config under the `Authorization: Bearer dk_…` header.
Does Zapier work with Dock's MCP server?
Yes. Dock exposes 43 MCP tools at `https://trydock.ai/api/mcp` over HTTP transport with OAuth 2.1 + DCR and Bearer-token auth. Any MCP-spec-compliant client, including Zapier, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Zapier can write to?
When you mint the `dk_` key for Zapier in Settings → API keys, pick the workspace from the dropdown. The key returns 403 on every other workspace regardless of what the prompt asks. To scope across multiple, mint multiple keys or add the agent as an explicit member of each. Learn more →
How do I see what Zapier did in my Dock workspace?
Open the workspace in your browser. Every row Zapier created or updated is stamped with the agent's identity (orb + name) in the createdBy / updatedBy field. The workspace activity feed shows every action chronologically. Learn more →
How do I undo a row Zapier wrote to Dock?
Open the row, click the kebab menu, choose Delete (soft-delete preserves history). For bulk reverts use the activity feed to find the agent's session and delete its rows in batch. To prevent future writes, revoke Zapier's `dk_` key in Settings → API keys.
Can multiple Zapier sessions share state through Dock?
Yes. Every Zapier session reads and writes the same workspace, so handoffs across machines or across long-running multi-session workflows just work. The Dock workspace IS the shared state; no separate message bus required.
Does Zapier need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Zapier hits Dock's discovery endpoint at `/.well-known/oauth-authorization-server` and auto-registers as a client. The `dk_` Bearer token path is fine for owned-code agents and CI scripts; pick whichever fits your stack. Learn more →
How do I connect Zapier to Dock?
Use Zapier's MCP support: in your Zap, add an MCP step pointing at `https://trydock.ai/api/mcp` with your `dk_` Bearer token. The 43 Dock tools surface as Zapier action steps.
Can a Zapier zap write a row to my Dock workspace when an email arrives?
Yes. Trigger: Gmail New Email. Action: Dock MCP `create_row` with the email subject as title and from-address as a column. The zap runs every time a matching email lands.
How do I trigger a Zap from a Dock event?
Set up a Dock webhook (POST `/api/webhooks`) pointing at a Zapier Catch Hook URL. Filter on the events you care about (e.g. `row.created`). Zapier then dispatches the payload through your Zap's downstream steps.

Related

Updated