Connect n8n to Software Without an API (July 2026)
n8n's HTTP Request node can call anything with an API. For portals that have none, a generated backend endpoint makes them a node like any other. Updated July 2026.
n8n has become the workflow engine of choice for technical teams and automation agencies: self-hostable, source-available, priced kindly at volume, and unusually good at AI-agent workflows. If you build client automations for a living, you probably already run it. The recurring blocker is the client system that nothing connects to.
TL;DR
n8n can call anything that speaks HTTP. Supergood turns a no-API portal into documented REST endpoints (and MCP tools), so the portal becomes an ordinary HTTP Request node in your workflow: structured JSON in, structured JSON out, milliseconds per call, maintenance handled upstream.
Why this fits n8n specifically
Three reasons. First, n8n users are comfortable with the HTTP Request node, so a generated endpoint needs no custom connector to be useful on day one. Second, self-hosted n8n often runs inside client environments where a bot fleet or hosted browser is a non-starter; a REST call isn't. Third, n8n's AI agent nodes can consume MCP tools, and every Supergood integration ships as one, so the same portal actions your workflows use are available to your agents.
| Approach in n8n | Works when | Failure mode |
|---|---|---|
| Official or community node | The vendor has an API someone wrapped | No node exists for most vertical portals |
| Browser automation called from n8n | One-off, low-stakes tasks | UI changes and MFA break unattended runs |
| HTTP Request node + Supergood endpoint | Any web portal a user can log into | Backend schema changes (detected and fixed upstream) |
The MSP and agency angle
If you sell automation as a service, every workflow that drives a client portal's UI is a maintenance contract you gave away for free: the portal redesigns on its own schedule, and the 2 a.m. breakage is your unbilled morning. Moving the portal segment to a managed endpoint moves that liability upstream. Your n8n workflow keeps the logic and your margin keeps the hours, and the integration is deliverable under your brand.
FAQ
Is there a Supergood community node? The HTTP Request node covers everything today (the endpoints are plain documented REST with bearer auth). If your team would use a dedicated node, tell us; enough requests reorder the roadmap.
How does auth work for a client's portal? The client adds a service account (a real managed email and phone) to their portal like any employee. MFA challenges have somewhere legitimate to go, access is scoped to that user's permissions, and every call is logged.
Self-hosted n8n too? Yes. The endpoint is an HTTPS API, so cloud and self-hosted n8n call it identically.
Related reading
- What iPaaS Can't Reach — how the orchestration and connectivity layers compose.
- MCP for Software Without a Public API — the agent-tools side of the same integrations.
Updated July 2026.