Use the HTTP Request Node as a Universal Connector

n8n has 400+ built-in nodes, but the API you need will eventually not be among them. The HTTP Request node is the escape hatch: it can call any REST API, GraphQL endpoint, SOAP service, or plain URL. Master this node and you are never blocked by a missing integration. The HTTP Request node supports custom headers, authentication, request bodies, query parameters, pagination, and response parsing.

Real-world example: You need to integrate with a niche project management tool (Linear) that has no dedicated n8n node. Use the HTTP Request node with their GraphQL API.

{
  "method": "POST",
  "url": "https://api.linear.app/graphql",
  "authentication": "genericCredentialType",
  "genericAuthType": "httpHeaderAuth",
  "sendHeaders": true,
  "headerParameters": {
    "parameters": [
      {
        "name": "Content-Type",
        "value": "application/json"
      }
    ]
  },
  "sendBody": true,
  "bodyContentType": "json",
  "jsonBody": "={{ JSON.stringify({ query: `{ issues(filter: { state: { name: { eq: \"In Progress\" } } }) { nodes { id title assignee { name } priority } } }` }) }}"
}
```text
```json title="Response from Linear API"
{
  "data": {
    "issues": {
      "nodes": [
        {
          "id": "LIN-1234",
          "title": "Fix authentication flow",
          "assignee": { "name": "Jane Martinez" },
          "priority": 1
        },
        {
          "id": "LIN-1235",
          "title": "Add CSV export feature",
          "assignee": { "name": "Bob Chen" },
          "priority": 2
        }
      ]
    }
  }
}
```text
> **Tip: Create Reusable Credential Types**
>
> If you call the same API from multiple workflows, create an HTTP Header Auth credential with the API key stored once. All HTTP Request nodes can reference this credential, so rotating the key requires only one change.

The HTTP Request node turns n8n into a universal integration platform. Any service with an API becomes connectable, regardless of whether a dedicated node exists.

**Related:** [Use Path Parameters in Webhook URLs for Dynamic Routing](../webhook-mastery/01-use-path-parameters-in-webhook-urls-for-dynamic-routing.md) | [Use Edit Fields in "Map Each" Mode for Simple Renames](../data-transformation/01-use-edit-fields-in-map-each-mode-for-simple-renames.md)