Status: no native Zapier connector#
LumenFlow has no dedicated Zapier entry under workspace connections and no one-click authorization flow. This article describes the path that works right now.
What works today: the MCP host#
LumenFlow exposes a workspace-scoped MCP (Model Context Protocol) endpoint that any MCP-compatible client can call, authenticated with a workspace API key:
POST https://<your-app-domain>/api/v1/mcp
Authorization: Bearer <your-workspace-api-key>
Generate an API key from your workspace settings — see API reference. One tool is wired up today: a read-only list of your workspace's delivery programs, each with its ID, title, status, created and completed dates, and a progress figure. It never makes changes to your workspace. See Connect to LumenFlow via MCP for the full endpoint and authentication details.
If your automation platform can act as an MCP client, point it at this endpoint to read delivery-program data into a workflow.