Resources · Make integration

anny Make integrationAutomate anny with Make.

What can the anny Make integration do for your bookings? Make offers 5 modules for anny: 4 scheduled triggers and 1 API call action. This page is for teams that run appointments in anny, and it walks you from the connection to a first working scenario.

Try the anny integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the anny Make integration let you automate?

The anny Make integration links your anny account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. On the anny side, Make can spot new bookings, customers, invoices and orders, then pass each one to the rest of your tools.

Hand invoices to your finance tools. Watch Invoices picks up the invoices anny has issued since the last check, so the next module in your scenario can file them where your accountant already works, in a sheet or a bookkeeping app.

Keep your customer list in one place. Watch Customers brings each new anny customer into Make as a bundle, one item passed from module to module, ready to be added to your CRM or newsletter tool.

Reach the parts of anny the triggers skip. Make an API Call reuses your anny connection to call any endpoint of the anny API, which is how you act on data the four triggers only read.

Know the limit before you start: Make's own documentation for anny is thin, because little public information exists about the app, so field names are discovered in the editor rather than read in a guide. When something breaks, the Make troubleshooting guide covers the usual causes. anny may also exist as an n8n node; the n8n vs Make comparison helps you weigh the two, and the Make training takes you further on scenario design.

Connect

How do you connect anny to Make?

  1. 01

    Add an anny module

    In a new scenario, click the + and search for anny. Pick any of its modules, for example Watch Bookings, then click Create a connection. A connection is your anny account linked to Make once, then reused by every anny module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as the studio or team it belongs to. Then either approve Make on the anny page that opens, or paste the key anny gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. Make now reads your anny data, and every other anny module you add later offers this same connection in its list, so you only do this once per account.

First scenario

Your first scenario with anny and Make

GoalWhen a new booking appears in anny, Make picks it up and sends a call to the anny API with the booking data.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the middle of the canvas to place your first module.

  2. 02

    Add Watch Bookings

    Search for anny, choose Watch Bookings and click Create a connection to link your account. Fill the fields Make shows once the connection works.

  3. 03

    Add Make an API Call

    Click the + on the right of Watch Bookings, pick anny again, then Make an API Call. Point it at the anny endpoint you need and map the booking data from the first module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check the booking arrived and the call went through.

  5. 05

    Schedule and switch it on

    Open the clock on Watch Bookings to set the schedule, every 15 minutes by default, then turn the scenario on so new bookings keep flowing without you.

Triggers

What starts an anny scenario?

4 modules start a scenario when something happens in anny. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by anny as soon as it happens.

anny1Watch Bookings

Watch Bookings

triggerIn the docs only

Every booking made in anny since the last check lands in your scenario, one bundle per booking, ready for the next module to confirm, log or share it.

How it fires
scheduled. Make checks anny on the scenario's schedule, which is every 15 minutes by default for a new scenario.
When to use it
your team needs a new appointment to show up in a shared calendar, a chat channel or a planning sheet without anyone copying it by hand.
Watch out
Make's documentation for anny does not list the fields of a booking, so click Run once and read a real bundle before you map anything.
anny2Watch Customers

Watch Customers

triggerIn the docs only

Each new anny customer reaches you at Make's next check, which is the cleanest starting point when your contact base lives somewhere else.

How it fires
scheduled. Make checks anny on the scenario's schedule and brings back the customers created since its previous pass.
When to use it
a person books with you for the first time and you want that profile added to your CRM or mailing tool, rather than typed in twice.
Watch out
Make lists no customer fields for anny, so run the scenario once and check which details a real customer bundle carries before you map it.
anny3Watch Invoices

Watch Invoices

triggerIn the docs only

This trigger feeds the invoices anny produces into Make, so your bookkeeping follows your sales without a manual export.

How it fires
scheduled. Make queries anny on the scenario's schedule; the free plan cannot go below 15 minutes between two checks, paid plans can go down to 1 minute.
When to use it
your accountant wants every invoice in the accounting tool or in a shared folder once anny issues it, without anyone exporting files by hand.
Watch out
each invoice processed counts as an operation, one run of one module that Make counts on your plan.
anny4Watch Orders

Watch Orders

triggerIn the docs only

Orders placed through anny become bundles in Make, which lets a purchase trigger the rest of your process instead of waiting in a dashboard.

How it fires
scheduled. Make looks at anny at the interval set on the scenario's clock, not at the exact second an order is placed.
When to use it
a customer places an order in anny and you want the sale recorded in your reporting sheet or announced to the team that delivers it.
Watch out
if you also use Watch Invoices on the same sales, decide which trigger feeds your reporting, so each sale is not counted twice.
Modules

What else can Make do in anny?

anny gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

anny1

Make an API Call

ActionIn the docs only

This module opens the whole anny API to your scenario, using the connection you already created, so you are not limited to the four triggers.

When to use it
you need to write something back into anny, or read data none of the Watch modules return, and the endpoint exists in the anny API.
Watch out
Make gives no guide for anny endpoints, so keep anny's own API reference open and test each call with Run once before switching the scenario on.
Need help

Need help automating anny with Make?

A person reads every message.

FAQ

anny and Make: common questions

01Is the anny Make integration free?
Yes, anny is a standard app in Make, so you can use it on the Free plan. That plan keeps you to 2 active scenarios, a gap of at least 15 minutes between two scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits: runs every minute, unlimited active scenarios and executions up to 40 minutes. Usage is counted in credits, meaning operations, each month. What you pay anny for its own service is a separate question.
02What do you need to connect anny to Make?
Make's documentation lists no specific prerequisite for anny: in practice, you start with an anny account and a Make account. You add any anny module, click Create a connection, optionally name it, then authorize Make on the anny page or paste the key anny provides, and save. If the connection is refused, the first thing to check is what your anny user is allowed to access. The same connection is then offered to every other anny module you place in a scenario.
03Does the anny trigger in Make run in real time?
No. All four anny triggers are scheduled: Make asks anny for new bookings, customers, invoices or orders on the scenario's schedule, which is every 15 minutes by default. On the Free plan you cannot go below 15 minutes; on a paid plan the shortest interval is 1 minute. There is no instant anny trigger in Make, meaning none where anny calls Make through a webhook the moment something happens. For most booking and billing flows, a short delay like that is acceptable.
04What if the anny module you need is missing in Make?
Use Make an API Call. It reuses your anny connection and can reach any endpoint of the anny API, so an action with no dedicated module is still possible. The catch is documentation: Make says it cannot document anny fully because too little public information exists, so you rely on anny's own API reference for the endpoint and its parameters. Run the module once in the editor, read what comes back, and only then map the result into the next steps of your scenario.
05Should you use Make or n8n for anny?
It depends on the tool your team already knows. On Make, anny gives you 4 scheduled triggers for bookings, customers, invoices and orders, plus Make an API Call for everything else. anny may also have an n8n node, so compare the modules each tool offers for your exact use case rather than the brand. If a colleague already builds scenarios in Make and the four triggers cover your need, staying there avoids learning a second editor. Otherwise, look at both lists side by side before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations