> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# Using BeatAPI in n8n

> Connect BeatAPI models and data to n8n, then import a task-specific workflow with clear validation boundaries.

# Using BeatAPI in n8n

Choose the entry point that matches your task. A model credential, an HTTP workflow, and a published n8n template are different things.

| Task                             | n8n entry point                               | BeatAPI surface                                                   |
| -------------------------------- | --------------------------------------------- | ----------------------------------------------------------------- |
| Text in an AI Agent or LLM Chain | Built-in OpenAI Chat Model                    | `https://api.beatapi.io/v1` and an exact ID from `GET /v1/models` |
| Social Data or Web research      | HTTP Request with Header Auth                 | The inspected capability or documented Data/Web endpoint          |
| Image, video, or music video     | HTTP Request, Wait, and a bounded status loop | Create once, preserve the task ID, then poll its status           |

## Configure credentials

For the OpenAI Chat Model, create an OpenAI credential with your BeatAPI key and base URL `https://api.beatapi.io/v1`. For HTTP Request nodes, create a Header Auth credential with header `Authorization` and value `Bearer <your BeatAPI key>`. Keep real keys in n8n credentials, never in exported JSON.

## Import a workflow

The [BeatAPI n8n examples](https://github.com/BeatAPI/beatapi-examples/tree/codex/n8n-capabilities/integrations/n8n) include a capability workflow, three public Social Data research workflows, and a music-video workflow. The current Social Data changes are in [PR #20](https://github.com/BeatAPI/beatapi-examples/pull/20); that pull request is a review artifact, not a merged release or n8n Marketplace listing.

1. Download the workflow JSON and import it into n8n.
2. Open **Configure Inputs** and replace the sample values.
3. Assign your Header Auth credential to every BeatAPI HTTP Request node.
4. Inspect the selected capability's input, output, price, and execution instructions before a paid run.
5. Test one execution and retain the BeatAPI request ID or task ID beside the n8n execution ID.

For asynchronous work, retry status reads without creating another billable task. End the loop on success, failure, or a fixed timeout. A timeout in n8n does not prove the BeatAPI task failed.

## Verification status

As of September 26, 2026, the three Social Data JSON files had imported into a local n8n instance. The X keyword workflow completed a local n8n execution; Instagram and YouTube had API checks and import checks, but no complete n8n execution. The X template had been submitted to the n8n Creator Portal for human review. Check [PR #20](https://github.com/BeatAPI/beatapi-examples/pull/20) and the n8n template directory for the latest distribution state.

The built-in nodes are enough to use these examples. BeatAPI has not published a dedicated n8n community node.