Skip to main content
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

​
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:
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.

​
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

1

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.
2

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.
3

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.
4

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.
Once the webhook subscription is active, anny sends the data to your Make scenario on each selected event.

​
Settings & options

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.

​
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

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.
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

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.
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.
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.
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.
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.

​
Troubleshooting

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.
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.
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.