Troubleshooting
Fixes for common Wireflow problems: API, upload and app errors, AI agents that can't see the Wireflow tools, and webhooks your server missed.
Last updated View as Markdown
Find your problem below and follow the link to the section that fixes it, starting with errors from the Wireflow API.
Where are the fixes for API errors, uploads and webhooks?
Start with the API troubleshooting page, which takes each error the API returns and gives its cause, the fix and a way to check it. The other sections cover one surface each:
- Why is my Wireflow API request failing?
- What can go wrong with an upload?
- What happens when I hit a limit?
- Error format and status codes: the error shapes and the message behind each HTTP status.
- Media upload error codes:
unsupported_type,file_too_large,upload_busyand the rest, with what each one means. - Apps API errors: errors from calls to a published app.
- What happens if my server misses the webhook?: Wireflow retries the delivery, and polling still works if every attempt fails.
Where are the fixes when my AI agent can't see the Wireflow tools?
First run the read-only test prompt in How do I test the connection?, which spends no credits. If the agent still can't find the tools, open the section for your agent:
- Claude Code: Why can't Claude Code see the Wireflow tools?
- Claude app: How do I add Wireflow to Claude and sign in?
- Cursor: Why won't my MCP server connect in Cursor?
- ChatGPT: Why does the ChatGPT connector fail with an OAuth or URL error?
- GitHub Copilot in VS Code: Why won't my MCP server start or connect in VS Code?
- Gemini CLI: What does "disconnected" mean, and how do I fix it?
- Any other agent: general fixes for MCP connection problems.