# Install and connect

Install the node in n8n and point it at your BeeL. account.

## Install the node

BeeL. is a **verified node**, so an instance owner enables it once and it becomes available to
everyone on the instance — see [n8n's guide to installing verified
nodes](https://docs.n8n.io/integrations/community-nodes/installation/verified-install/).

In n8n, go to **Settings → Community Nodes → Install** and enter:

```text
n8n-nodes-beel
```

Self-hosting, you can install it from the CLI instead:

```bash
cd ~/.n8n
npm install n8n-nodes-beel
```

Restart n8n afterwards. The node has no runtime dependencies of its own, so it pulls nothing else
into your installation.

---

## Create the credential

Add a **BeeL API** credential:

| Field | Notes |
|---|---|
| **API Key** | `beel_sk_test_…` targets the sandbox — no quota consumed, VeriFactu in test mode. `beel_sk_live_…` targets production. |
| **Default Company ID** | The company (NIF) nodes operate as by default. Each node can override it. |
| **Base URL** | `https://app.beel.es/api` unless told otherwise. |

The credential test calls `GET /v1/me/identity`, which needs no scope — a green tick means the key
is valid and nothing else.

<Callout type="info">
  Build the whole workflow with a **test key** first. You see exactly how each invoice comes out —
  QR, hash, numbering, the email the customer receives — without registering anything with the AEAT
  or consuming quota. Swap the credential for a live one when it does what you want.
</Callout>

---

## Choosing the company

BeeL. scopes its resources by company: invoices, customers, products and series all live under one.
Every node resolves the company in this order:

1. The **Company** field on the node — set it per item with an expression if one workflow serves several NIFs
2. The **Default Company ID** on the credential

There is no third option. The company travels in the URL, so a request without one cannot be sent
and the node says so instead of guessing.

### Provisioners

If your key provisioned accounts for other people, the **Account** field picks which one an
operation acts on — `account_id` may be your own account or an account you provisioned. Leave it
empty for the account the key belongs to. The Company dropdown follows whichever account is selected.

## Related

<Related>

- [n8n overview](/n8n) — what the node does and who maintains it
- [Recipes](/n8n/recipes) — workflows worth building
- [Scopes](/auth/scopes) — what the credential's key needs

</Related>

---

Full OpenAPI spec: https://docs.beel.es/api/openapi