zapier-limits-and-costlisted

# Zapier Limits and Cost ## Platform compatibility When running in ChatGPT or Codex, read `../../references/codex-compatibility.md` before inspecting connectors or proposing scheduled work. Describe only the apps and MCP tools actually available in the current conversation. Use this skill when the user's request may not fit the current platform's scheduled-task feature, may not be possible through Zapier, or may cost more than expected. This skill is Zapier-specific; do not apply Zapier task costs to direct/native platform connectors. Keep the explanation short and plain, but never quote a limit, price, task count, or capability from memory. Inside the Inbox Assistant plugin the routing is fixed, and it changes the cost story: **mail reads come from the native Gmail or Outlook connector first, and every write goes through Zapier.** Native reads spend nothing. Zapier-routed reads, which are the fallback whenever a native connector does not cover a mailbox, spend tasks like any other Zapier call, and so does every Zapier write. **So the count that matters is Zapier-routed calls, reads-as-fallback included, never runs.** A daily brief reading natively spends Zapier tasks on the drafts it saves and on nothing else; the same brief reading a mailbox through Zapier spends tasks on those reads as well; a read-only setup on native connectors, where drafts print in the brief instead of saving into the mailbox, spends none at all. See `references/connector-matrix.md` for which capa