> ## 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 Make.com with anny

> Connect anny to Make.com via webhooks and the API to automate your booking workflows without coding.

[Make.com](https://www.make.com) is an automation platform where you connect tools in visual scenarios without coding. A scenario reacts to an event in one system and then triggers actions in others. You connect anny to Make.com through two general building blocks: **webhooks** send events from anny to Make, and through the anny **API**, Make triggers actions in anny.

With Make.com, in anny you can:

* react to events, such as a new booking, a cancellation or new customers, and process the data further in other tools
* automatically transfer bookings, orders, invoices and customers to other systems like spreadsheets, chat or your CRM
* trigger actions in anny from a Make scenario, for example creating bookings or customers

Ideal for teams who want to connect anny to tools like Google Sheets, Slack or their CRM without any coding of their own.

## Common use cases

| Use case                              | Description                                                                                                                                                |
| :------------------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Record a new booking in a spreadsheet | **Every new booking automatically lands in your spreadsheet.** anny sends the event to your Make scenario, which turns it into a new row in Google Sheets. |
| Notify your team of cancellations     | **Your team hears about changes right away.** When a booking is deleted, Make automatically posts a message in Slack or Microsoft Teams.                   |
| Add customers to your CRM             | **New customers move into your CRM automatically.** As soon as anny creates a new customer, Make creates the matching contact in your CRM.                 |

## How the Make.com connection works

Make.com is not a built-in module in anny and doesn't appear in the integrations list. You connect the two systems through the **API & Webhooks** tab in your organization's **Settings**. There you set up two things:

* A **Personal Access Token** for access to the anny API. Make uses it to authenticate as a trusted way into your organization. With the token, Make can read and create the data that an admin can also reach through the API (for example bookings, orders, invoices and customers).
* One or more **webhook subscriptions** that send events from anny to an endpoint URL you specify. This URL comes from your Make scenario.

If you revoke access, the connection ends immediately: if you delete or rotate the token, Make can no longer access the anny API. If you deactivate or delete the webhook subscription, anny stops sending events to Make.

Here's how the data flows between anny and Make:

| Direction             | Building block                      | Examples                                                             |
| :-------------------- | :---------------------------------- | :------------------------------------------------------------------- |
| anny → Make (trigger) | Webhook subscription                | Booking created, booking checked in, order created, customer created |
| Make → anny (actions) | anny API with Personal Access Token | Read or create a booking, create a customer                          |

<Tip>
  anny signs every webhook call with a **signature key**. In Make, you can use it to verify that an incoming call really comes from anny.
</Tip>

## Connect Make.com

### Requirements

Before you connect Make.com, make sure you have the following:

* Access to the **API & Webhooks** tab in the organization settings (admin rights)
* A Make.com account
* A scenario in Make with a **Webhook** module for triggers and, if you want to trigger actions in anny, an **HTTP** module for the anny API

### Set up the connection

<Steps>
  <Step title="Create a Personal Access Token">
    Open **Settings** and go to the **API & Webhooks** tab. In the **Personal Access Tokens** area, click **Create token**, enter a **token name** (e.g. "Make.com") and copy the token right away. anny only shows it once.
  </Step>

  <Step title="Prepare the webhook URL in Make">
    Create a scenario in Make and add a **Webhook** module as a trigger. Make generates a unique URL for it. Copy this URL.
  </Step>

  <Step title="Create a webhook subscription in anny">
    In the **Webhooks** area, click **Create webhook**. Enter a **name** and the copied URL as the **endpoint URL**, select the events you want under **Event selection** and enable the **Active** toggle. Optionally, you can limit booking events to specific resources, groups or categories. Save the subscription.
  </Step>

  <Step title="Set up actions via the anny API">
    If you want to create or read data in anny from Make, add an **HTTP** module to your scenario and store the Personal Access Token as a bearer token. You'll find the available endpoints in the anny API documentation.
  </Step>
</Steps>

Once the webhook subscription is active, anny sends the data to your Make scenario on each selected event.

### Settings & options

| Setting         | Description                                                                                                                                                                                                                                          |
| :-------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name            | Freely chosen label for the webhook subscription.                                                                                                                                                                                                    |
| Endpoint URL    | The address anny sends the events to (the webhook URL from your Make scenario).                                                                                                                                                                      |
| Event selection | The events that trigger the webhook, grouped into **Bookings**, **Orders**, **Invoices**, **Customers**, **Subscriptions**, **Appointments** and **Community members**. The individual events appear as technical labels such as `bookings.created`. |
| Active          | Switches the subscription on or off. Only active subscriptions send events.                                                                                                                                                                          |
| Restrictions    | Optional: limits booking events to specific resources, groups or categories.                                                                                                                                                                         |
| Signature key   | Automatically generated and read-only. anny uses it to sign every call so you can verify authenticity in Make.                                                                                                                                       |

<Tip>
  Under **Show call history**, you see the webhook attempts of the last 30 days per subscription, with status, HTTP status code and response. You can manually re-trigger failed calls there.
</Tip>

## Limitations

Connecting to Make.com via webhooks and the anny API doesn't support:

* **A ready-made anny module:** anny has no prebuilt connector in the Make marketplace. You build the connection with Make's generic modules (Webhook, HTTP).
* **Fine-grained permissions:** Selecting individual permissions for a token isn't available yet. A token gets access to all data in your organization reachable through the API.
* **Custom headers:** A webhook subscription doesn't send custom HTTP headers. The signature key serves as the safeguard.
* **German event names:** anny shows the individual events as technical labels (e.g. `bookings.created`), not as translated names.

## Disconnect

<Warning>
  If you delete or rotate the Personal Access Token, Make can no longer access the anny API, and existing scenarios will fail. If you deactivate or delete the webhook subscription, anny stops sending events to Make.
</Warning>

You'll find both under **Settings** in the **API & Webhooks** tab: the token via **Rotate** or Delete, the webhook subscription via the **Active** toggle or Delete.

## FAQ

<AccordionGroup>
  <Accordion title="Is there a ready-made anny module in Make.com?">
    No. You connect anny and Make through the generic building blocks: a Webhook module in Make receives the events from anny, and an HTTP module talks to the anny API. There's no branded anny connector in the Make marketplace.
  </Accordion>

  <Accordion title="Which events can I send to Make?">
    Events from the categories Bookings, Orders, Invoices, Customers, Subscriptions, Appointments and Community members, for example a new booking, a check-in or a new invoice. You select them when creating the webhook subscription.
  </Accordion>

  <Accordion title="How do I secure my webhooks?">
    Each subscription has an automatically generated signature key. anny uses it to sign every call. In your Make scenario, you can verify the signature and make sure the call really comes from anny.
  </Accordion>

  <Accordion title="Where do I see whether an event was delivered?">
    Under **Show call history** on the respective webhook subscription. There you see the attempts of the last 30 days with status, HTTP status code, request and response.
  </Accordion>

  <Accordion title="Do I need coding skills?">
    No, you assemble the scenarios in Make by clicking. A basic understanding of webhooks and HTTP requests does help when setting up the connection, though.
  </Accordion>
</AccordionGroup>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Make isn't receiving events from anny">
    The webhook subscription may not be active, the endpoint URL may be wrong, or the right events may not be selected. Check the **Active** toggle, the **endpoint URL** and the selected events. Under **Show call history**, you see whether and with what status anny has sent.
  </Accordion>

  <Accordion title="My webhook was deactivated automatically">
    anny deactivates a subscription whose calls repeatedly fail. The usual cause is an unreachable or incorrect endpoint URL. Correct the URL in Make and in anny and re-enable the subscription via the **Active** toggle.
  </Accordion>

  <Accordion title="API requests from Make fail">
    The Personal Access Token has probably expired, been rotated or deleted. Create a new token in the **API & Webhooks** tab and store it in the HTTP module of your Make scenario.
  </Accordion>
</AccordionGroup>

> Important information for agents:
>
> **Distinction:** Make.com is NOT a built-in anny integration. There's no backend module, no entry in the integrations list and no integration toggle. The connection runs purely through two generic anny building blocks: Personal Access Tokens (API access) and webhook subscriptions (triggers). anny itself never mentions "Make"/"Make.com"/"Zapier" anywhere; whether there's an official anny connector in the Make marketplace can't be confirmed from the code.
>
> **UI paths:** Setup isn't under "Integrations", but under **Settings → "API & Webhooks" tab**. Two areas there: **"Personal Access Tokens"** ("Create token" button, "Token name" field; actions "Rotate"/Delete; token shown only once) and **"Webhooks"** ("Webhook subscriptions" table, "Create webhook" button; fields "Name", "Endpoint URL", "Active", "Event selection", optional restrictions; read-only signature key). Deliveries via "Show call history".
>
> **Auth & API:** Make authenticates with the Personal Access Token as a bearer token against the anny JSON:API at `/api/v1`. Fine-grained token permissions (scopes) can't be selected in the UI yet ("permissions coming soon"); a token without set scopes currently has full access to the organization. Security-relevant.
>
> **Events (triggers):** Categories localized (Bookings, Orders, Invoices, Customers, Subscriptions, Appointments, Community members); individual events NOT localized, as technical IDs. Full list: `bookings.created/updated/started/ended/checked-in/checked-out/deleted`, `orders.created/updated/deleted`, `invoices.created/finalised/updated/deleted`, `customers.created/updated/deleted`, `subscriptions.created/started/updated/canceled/renewed/suspended/ended/charged/reactivated`, `timeslots.created/updated/started/ended/deleted`, `community-accounts.joined/left`, `call-sessions.completed`.
>
> **Payload:** Envelope per call with `event`, `event_id`, `webhook_id`, `triggered_at`, `data`. Signature via HMAC over the subscription's signature key (Signature header). No custom headers configurable.
>
> **Quirks:** (1) Webhook subscriptions are automatically deactivated after repeated delivery failures; optional "Webhook deactivation notification" email; then reactivate manually. (2) Call history shows attempts of the last 30 days; failed ones can be retried manually, successful and already-retried ones cannot. (3) Restrictions apply only to booking events. (4) The "API & Webhooks" tab only appears with the permission for webhook subscriptions; a possible plan binding can't be verified from the code.
>
> **Relationships:** For the action path (Make → anny), the anny API is used; cross-reference to the API documentation tab once it's filled. Related automation context: "(Automatic) exports".