Connector implementation and rollout
Shared by Pavel · Updated 2026-11-03
By late October 2026, Substrate had first-class Notion, Gmail, and WhatsApp connectors plus a path to any MCP, but several connections and processing flows still needed setup or verification.
Updated 30 Oct 2026 with new facts.
Integrations being built or checked
- Notion and HubSpot: September 11 action items were to continue Notion integration work and complete the HubSpot integration.
- Composio: On October 28, Pavel asked for a check whether Composio connectors were already implemented in the Substrate folder; the check was marked done, but no result was recorded. (more: Gmail and WhatsApp connectors)
- Google Drive: The plugin connection was still open; Pavel planned to connect it to review sales materials and summarize deal changes, risks, and next actions.
- Gmail and Google Drive: A planned workflow would use Drive with Gmail to review unread messages and prepare reply drafts; this was described as a planned, not confirmed, connection.
- Gmail access: Google OAuth verification and a CASA assessment were still required, with the task assigned to Pavel.
- MCP connection demo: A GIF for a newsletter was still rendering and awaited approval on October 19.
What the work showed
- The product had a stated connector set—Notion, Gmail, and WhatsApp—and could connect to any MCP; MCP connections typically used OAuth.
- That breadth did not mean every source was ready in practice: Gmail still faced verification requirements, Drive was awaiting connection, and the Composio implementation check had no recorded outcome.
- Processing was guarded rather than fully verified: a six-source extraction task excluded Slack, and streams were to remain paused until a manual tick had been inspected.
- Runtime MCP support was also uneven: one MCP request succeeded, but resources and templates were empty and Priors MCP tools were not exposed in the runtime.