Integration Overview (Choosing a Tool)
Besides calling the REST API directly, you can generate Re:port Flow PDFs from no-code automation tools and AI agents. Every integration calls the same Re:port Flow API, so the same template and parameters produce the same PDF.
Which one should I use?
| What you want to do | Integration |
|---|
| Create a PDF when a spreadsheet, form or CRM record changes | Zapier / Make / n8n |
| Run it on a self-hosted workflow platform | n8n |
| Ask an AI such as Claude, Cursor or VS Code to "make a PDF" | MCP Server |
| Create PDFs from a Coze bot or workflow | Coze |
| Call it from your own code | API Quick Start |
Comparison
No-code automation
| Tool | Distribution | Authentication | Acting on a finished PDF |
|---|
| Zapier | Public beta in the Zapier App Directory | OAuth 2.0 (Authorization Code + PKCE) | New PDF Generated trigger (the connected account must be a workspace administrator) |
| Make | Reviewed official app | OAuth 2.0 (Authorization Code + PKCE) | Watch file completed trigger (the connected account must be a workspace administrator) |
| n8n | Official community node n8n-nodes-reportflow | Application key (AppKey) | No dedicated trigger; combine async generation with webhooks |
AI agents
| Tool | Distribution | Authentication | Notes |
|---|
| MCP Server | Listed in Claude's connector directory, remote endpoint, npm package reportflow-mcp | OAuth 2.0 (Authorization Code + PKCE) + Dynamic Client Registration | No API key is handed to the AI client |
| Coze | Registered as an OpenAPI plugin in your own Coze account (Plugin Store listing in preparation) | appkey header | Confirm completion with async generation and download |
See each page for the details behind every column (scopes, available operations, constraints).