n8n Integrations: Connect Any App, API or Database
How n8n integrations work, the most popular nodes by category, how to connect any API with the HTTP Request node, and when to use community or custom nodes.
How n8n Integrations Work
Every integration in n8n is a node. App nodes wrap an external service's API into ready-made operations like "create contact" or "send message", so you pick an action instead of writing requests. Trigger nodes start workflows when something happens in an app.
Credentials are stored once and reused across workflows, and every node outputs JSON that the next node can use — which is what lets you chain integrations together.
Most Popular n8n Integrations by Category
| Category | Popular nodes | Typical use |
|---|---|---|
| Spreadsheets & docs | Google Sheets, Airtable, Notion | Store and update records |
| CRM & sales | HubSpot, Salesforce, Pipedrive | Lead routing and enrichment |
| Communication | Slack, Microsoft Teams, Telegram, Gmail | Alerts and notifications |
| E-commerce & payments | Shopify, WooCommerce, Stripe | Order and payment sync |
| Databases | Postgres, MySQL, MongoDB, Redis | Read, write and sync data |
| AI | OpenAI, Anthropic, Gemini, vector stores | Classify, summarise, build agents |
| Developer | GitHub, GitLab, Jira | Issue and release automation |
Connecting Any API With the HTTP Request Node
When there is no dedicated node, the HTTP Request node connects n8n to any REST API. Most integrations you need are one well-configured request away.
- Find the endpoint and authentication method in the app's API documentation.
- Create a credential in n8n (header auth, OAuth2 or basic auth) instead of pasting keys into the node.
- Set the method, URL, query parameters and JSON body.
- Enable pagination settings if the API returns results in pages.
- Test the request and map the response fields into the next node.
Community and Custom Nodes
Community nodes are published by other developers and installed from the n8n settings on self-hosted instances. They cover many niche services. Check the package's maintenance activity and permissions before relying on one.
For internal systems, a custom node packages your own API into reusable operations for your team. It takes developer time, so it makes sense mainly when many workflows call the same system.
Integration Best Practices
- Use one credential per service and environment, and name it clearly.
- Respect rate limits with batching, Wait nodes and retries.
- Prefer webhook triggers over polling when the app supports them.
- Validate incoming webhook data before acting on it.
- Keep secrets out of Code nodes and workflow fields.
Keep reading
Frequently Asked Questions
How many integrations does n8n have?
n8n ships with several hundred built-in nodes for apps and services, plus core nodes for logic and data. Community nodes and the HTTP Request node extend that to almost any service with an API.
What if n8n has no node for my app?
Use the HTTP Request node to call the app's REST API directly, check for a community node, or build a custom node. Most modern apps can be connected this way.
What are n8n community nodes?
Community nodes are integrations built and published by other developers as npm packages. You can install them from the n8n settings on self-hosted instances; review the code and maintenance activity before using one in production.
How do I connect an app to n8n?
Add the app's node to a workflow, create a credential (usually OAuth or an API key), and choose the resource and operation you need. Test the node with sample data before building further.
Can n8n connect to databases?
Yes. There are native nodes for Postgres, MySQL, Microsoft SQL Server, MongoDB, Redis and others, so workflows can read and write data directly.
Does n8n integrate with AI models?
Yes. n8n has nodes for OpenAI, Anthropic, Google Gemini, Mistral, Ollama and more, along with vector stores and the AI Agent node for building agents.
Ready to build?
Start from a ready-made workflow, or have an expert build one around your own systems.