> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anny.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect n8n with anny

> Automate bookings, customers, and invoices with the official anny node in n8n.

[n8n](https://n8n.io) is a workflow platform where you build automations visually. anny provides the community node [`n8n-nodes-anny`](https://github.com/anny-co/anny-n8n) for that. Unlike [Make.com](/en/make-com), you do not wire webhooks and API calls by hand: the node manages sign-in and webhook subscriptions itself.

With n8n, in anny you can:

* react to events, for example a new booking, a check-in, or a new invoice
* read or change bookings, customers, orders, invoices, subscriptions, resources, and services
* query availability and run arbitrary anny API calls from a workflow

Ideal for teams who want to connect anny to CRM, spreadsheets, chat, or accounting without building their own integration.

## Common use cases

| Use case                   | Description                                                                                                                                                |
| :------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------- |
| New booking into the CRM   | **Every new booking automatically creates a record.** The **Anny Trigger** starts on `bookings.created`, the **Anny** node loads the customer and booking. |
| Check-in in another system | **A check-in in anny starts the next step.** For example a chat message or a row in your spreadsheet.                                                      |
| Process an invoice         | **Finalized invoices land where you book them.** The **Invoice Finalized** trigger sends the event to your workflow.                                       |

## How the n8n connection works

n8n does not appear in the anny integrations list. You install the node in your n8n instance (Cloud or self-hosted) and store credentials:

* **OAuth2** (default): you choose the region (**anny.co** or **anny.eu**) and complete login in the browser. n8n then acts in the name of your admin account, including webhook subscriptions.
* **Access Token**: you store a **Personal Access Token** from anny (**Settings** → **API & Webhooks** tab).

The **Anny Trigger** automatically creates a webhook subscription in anny and deletes it when you remove the trigger. The **Anny** node calls the anny API for actions.

If you revoke access, the workflows stop: if you delete the credentials in n8n or rotate the token in anny, API calls fail. If you remove the trigger, the matching webhook subscription disappears.

How the data flows:

| Direction            | Building block   | Examples                                                         |
| :------------------- | :--------------- | :--------------------------------------------------------------- |
| anny → n8n (trigger) | **Anny Trigger** | Booking created, check-in, invoice finalized, customer created   |
| n8n → anny (actions) | **Anny** node    | Read, cancel, or check in a booking; create a customer; API Call |

## Connect n8n

### Requirements

Before you connect n8n, make sure you have:

* An n8n account (n8n Cloud or self-hosted) where you may install community nodes
* An anny admin account for the chosen region
* For Access Token, access to the **API & Webhooks** tab

### Set up the connection

<Steps>
  <Step title="Install the community node">
    In n8n, install the package `n8n-nodes-anny` as a community node. The steps are in the [n8n community nodes documentation](https://docs.n8n.io/integrations/community-nodes/installation/).
  </Step>

  <Step title="Create credentials">
    In n8n, create the credential **Anny OAuth2 API**, choose the **Region** (**anny.co** or **anny.eu**), and complete the OAuth login. Alternatively, use **Anny Access Token API** with a Personal Access Token from anny.
  </Step>

  <Step title="Add a trigger or an action">
    For events, add the **Anny Trigger** node and select the **Events**, for example **Booking Created**. For actions, add the **Anny** node and choose a resource and operation, for example Booking → Get.
  </Step>

  <Step title="Activate the workflow">
    Save and activate the workflow. The trigger then creates the webhook subscription in anny.
  </Step>
</Steps>

Once the workflow is active, n8n starts automatically on every selected event.

### Settings & options

| Setting                          | Description                                                                                             |
| :------------------------------- | :------------------------------------------------------------------------------------------------------ |
| Authentication                   | **OAuth2** or **Access Token** on the respective node.                                                  |
| Region                           | **anny.co (default)** or **anny.eu (Gov-Cloud)**. Must match your anny account.                         |
| Events (trigger)                 | The events that start the workflow, for example Booking Created, Booking Checked In, Invoice Finalized. |
| Resource / Operation (Anny node) | Booking, Customer, Order, Invoice, Plan Subscription, Resource, Service, Availability, or API Call.     |
| Simplify                         | For Get/Get All, returns a simplified response instead of the raw JSON:API document.                    |

<Tip>
  For endpoints the node does not cover, use the **API Call** operation against `/api/v1/…`.
</Tip>

## Limitations

The n8n connection does not support:

* **An entry under Integrations:** you install the node in n8n, not through the integrations list in anny.
* **Every webhook event:** the trigger covers bookings, customers, orders, and invoices. Subscriptions, time slots, and community members can be set up with a manual webhook subscription as in [Make.com](/en/make-com).
* **Fine-grained token permissions:** a Personal Access Token has the same API access as an admin. Individual permissions are not yet selectable in the UI.

## Disconnect

<Warning>
  If you delete the credentials in n8n or rotate the Personal Access Token in anny, existing workflows fail. If you remove an **Anny Trigger**, n8n deletes the matching webhook subscription in anny.
</Warning>

You manage credentials in n8n. You find the Personal Access Token in anny under **Settings** in the **API & Webhooks** tab (rotate or delete).

## FAQ

<AccordionGroup>
  <Accordion title="Is this an official anny node?">
    Yes. anny maintains the community node in the GitHub repository [anny-co/anny-n8n](https://github.com/anny-co/anny-n8n) (npm package `n8n-nodes-anny`). It is not a generic HTTP module, but a dedicated node with trigger and actions.
  </Accordion>

  <Accordion title="When do I use n8n, when Make.com?">
    n8n if you want the ready-made anny node with OAuth and automatic webhooks. Make.com if you already use Make: there you connect anny through generic webhooks and HTTP, see [make.com](/en/make-com).
  </Accordion>

  <Accordion title="Which events can the trigger receive?">
    Bookings (created, updated, started, ended, checked in, checked out, deleted), customers, orders, and invoices (including finalized). Labels in the node are English, for example **Booking Created**.
  </Accordion>

  <Accordion title="Do I need coding skills?">
    No. You assemble the workflow in n8n. A basic understanding of webhooks helps when troubleshooting.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The trigger does not start">
    The workflow may not be active, the region may be wrong, or the selected events may not match. Activate the workflow and check in anny under **API & Webhooks** whether a subscription named `n8n Trigger - Workflow …` exists.
  </Accordion>

  <Accordion title="OAuth login fails">
    Usually the wrong region is selected. **anny.co** and **anny.eu** are separate environments. Choose the region where your account lives and complete login again.
  </Accordion>

  <Accordion title="API actions fail">
    The credentials expired, the token was rotated, or the access token no longer has access. Recreate the credential in n8n or create a new token under **API & Webhooks**.
  </Accordion>
</AccordionGroup>

> Important information for agents:
>
> **Distinction:** n8n is NOT an integration in the anny integrations list. Official community node: GitHub anny-co/anny-n8n, npm `n8n-nodes-anny`, nodes **Anny** (`anny`) and **Anny Trigger** (`annyTrigger`). Make.com has NO comparable branded connector.
>
> **Auth:** credentials **Anny OAuth2 API** (region co/eu/staging/local, grant authorizationCode, scopes `user:read b.* b.webhook-subscriptions:*`, preAuthentication fetches `organizationId` via `/api/v1/user?include=active_organization`) or **Anny Access Token API** (PAT Bearer). Customer-facing regions: anny.co and anny.eu (Gov-Cloud). Do not document staging/local in the visible article.
>
> **Trigger:** POST `/api/v1/webhook-subscriptions`, name `n8n Trigger - Workflow {id}`; deletes on remove. Events in the node: bookings.created/updated/started/ended/checked-in/checked-out/deleted, customers.*, orders.*, invoices.created/updated/deleted/finalized. NOT in the trigger: subscriptions.*, timeslots.*, community-accounts.*, call-sessions.* (those exist in anny webhooks, see the Make article).
>
> **Actions:** Availability, Booking (get/list/cancel/check-in/check-out), Customer (CRUD+list), Order/Invoice/Plan Subscription/Resource/Service (get/list), API Call for arbitrary `/api/*`.
>
> **anny UI paths:** Personal Access Token only under Settings → API & Webhooks. No integrations toggle.
>
> **Related:** Make.com article `/en/make-com` (generic webhooks+HTTP). Changelog 2025-12-16 mentions n8n Cloud. API docs must not claim Make has a native connector.