connector-discoverylisted

# Connector Discovery ## 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 wants to know what the current assistant can do with connected apps, or before designing any scheduled task that uses app connectors. Two layers are usually in play: the current product's native connectors and Zapier. Survey both. Your job is to inspect the capabilities actually visible in the current chat, explain them in plain language, and flag anything missing, without ever stating a time-sensitive fact from memory. Inside the Inbox Assistant plugin the two layers have fixed jobs, and the inventory follows that split: **mail reads come from the native Gmail or Outlook connector first, with Zapier find actions as the fallback, and every write goes through Zapier only.** So a survey here answers three questions rather than one long list: can it read mail, can it save a draft, can it tidy a thread. The first is usually native. The other two are always Zapier. See `references/connector-matrix.md` for the routing table this maps onto. **A visible tool is not a permitted action, and saying so is part of the report.** Setup has two stages: stage 1 connects the reading, stage 2 turns on individual actions one at a time. All seven actions start off, and a discovery survey never c