Resources · Make integration

Fingertip Make integrationAutomate Fingertip with Make.

Every booking, order and form reply on your Fingertip site can start a workflow. The Fingertip Make integration gives you 6 triggers and 1 action. This page shows how to link your account, build a first scenario and pick the right module.

Try the Fingertip integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Fingertip Make integration do for you?

The Fingertip Make integration links your Fingertip account to Make so that activity on your site, like a new booking, an order or a form reply, starts a scenario: the automation you build in Make, a chain of modules that runs on a schedule. No code is involved, only an API key and a few clicks.

A calendar that updates your team. Watch Created Bookings, Watch Rescheduled Bookings and Watch Cancelled Bookings each pick up one kind of change to your appointments. Pair each one with a message or a spreadsheet module from another app, and nobody has to check the Fingertip dashboard to know who is coming.

Form replies that turn into contacts. Watch Created Form Responses hands each reply to the next module, and Create Site Contact files the person in your Fingertip contacts. The first scenario below builds exactly this flow.

Orders that reach your other tools. Watch Created Orders passes every new sale to whatever comes next: an invoice tool, a shared sheet, a chat channel.

Know the limits before you start. The Fingertip app in Make has no universal API call module, and nothing in the documentation points to an instant trigger, so expect everything to run on the scenario's schedule and only the 7 listed modules are available. If you want a second opinion on the platform first, read our Make review. The same kind of app often has an n8n node too, and the n8n vs Make comparison helps you choose. When a flow grows beyond a few modules, the Make agency team can build it with you.

Connect

How do you connect Fingertip to Make?

  1. 01

    Copy your API key in Fingertip

    Open your Fingertip account dashboard, go to the API keys section and copy the key shown on screen. You need an active Fingertip account for this key to exist, so create one first if you have not yet.

  2. 02

    Add a Fingertip module in Make

    Log in to Make, open your scenario and add any Fingertip module. Click Create a connection. A connection is your Fingertip account linked to Make once, then reused by every Fingertip module you add later.

  3. 03

    Paste the key and save

    Give the connection a name in the Connection name field if you like; it is optional but helps when you run several sites. Paste the API key you copied, or follow the on-screen instructions, and save.

First scenario

Your first scenario: form replies saved as site contacts

GoalWhen someone answers a form on your Fingertip site, Make adds that person to your Fingertip site contacts.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. Search for Fingertip and choose Watch Created Form Responses.

  2. 02

    Link your account

    Click Create a connection and paste your API key. Once the connection exists, Make can read your Fingertip data and offers the options it finds in the module settings.

  3. 03

    Add the contact action

    Click the + on the right of the trigger and pick Fingertip's Create Site Contact. Map the details from the form reply into the contact, choosing them from the list of data the trigger returns.

  4. 04

    Test with Run once

    Send a test answer through your form, then click Run once. Each module shows the bundles it received, so you can check that the right person landed in your contacts.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario checks every 15 minutes by default, and paid plans go down to 1 minute. Then switch the scenario on and let it run.

Triggers

Fingertip triggers in Make

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

Fingertip1Watch Cancelled Bookings

Watch Cancelled Bookings

triggerIn the docs only

You find out about every cancelled appointment without opening Fingertip, because this trigger hands each cancellation to the rest of your scenario as a bundle, one item that moves from module to module.

How it fires
scheduled. Make checks Fingertip on the scenario's schedule, so a cancellation appears at the next check rather than the second it happens.
When to use it
a coach or a clinic that wants to warn staff that a slot just opened, or remove the visit from a shared planning sheet.
Watch out
it only sees cancellations; a moved appointment belongs to Watch Rescheduled Bookings.
Fingertip2Watch Created Bookings

Watch Created Bookings

triggerIn the docs only

Each new appointment made on your site starts the scenario, which is the most direct way to push bookings into a calendar, a CRM or a team chat.

How it fires
scheduled. Make looks for new bookings each time the scenario runs, following the clock set on this first module.
When to use it
a salon or a consultant who wants the team told about every new client visit, with the booking details copied into another tool.
Watch out
on the Free plan the shortest interval is 15 minutes, so a booking made just after a check waits until the next one.
Fingertip3Watch Created Form Responses

Watch Created Form Responses

triggerIn the docs only

Replies to the forms on your Fingertip site become usable data in Make: one bundle per reply, ready to be sorted, saved or answered by the modules that follow.

How it fires
scheduled. Make asks Fingertip for new replies at every run of the scenario.
When to use it
a quote request or a contact form where each answer should reach a sales sheet, a mailing tool or your own site contacts through Create Site Contact.
Watch out
every reply costs at least one operation per module it passes through, and operations are what Make counts on your plan.
Fingertip4Watch Created Orders

Watch Created Orders

triggerIn the docs only

New sales on your Fingertip site no longer stay locked in the dashboard: this trigger sends each order to the next step, whether that is bookkeeping, a delivery list or a thank-you message.

How it fires
scheduled. Make checks for fresh orders on the scenario's schedule.
When to use it
a small shop that wants each purchase logged in a spreadsheet or announced in the team channel so someone prepares it.
Watch out
Make shows only the order data this module returns after Run once; test with a real order before you map anything.
Fingertip5Watch Created Site Contacts

Watch Created Site Contacts

triggerIn the docs only

Your contact list on Fingertip can feed other tools: whenever a person is added to the site contacts, the scenario receives that contact and passes it on.

How it fires
scheduled. Make polls Fingertip for new contacts at the rhythm set on the first module.
When to use it
copying each new contact into a newsletter tool or a CRM, so your audience lives in one place.
Watch out
do not follow it with Create Site Contact in the same scenario, or every contact you create would be picked up again as a new one.
Fingertip6Watch Rescheduled Bookings

Watch Rescheduled Bookings

triggerIn the docs only

When a client moves an appointment, this trigger catches the change so your other tools show the new time instead of the old one.

How it fires
scheduled. Make checks Fingertip at every scheduled run of the scenario and passes on the bookings that moved.
When to use it
a therapist or a tutor who keeps a second calendar or sends reminders from another app and needs it in sync.
Watch out
run it in its own scenario or next to the created and cancelled triggers, since each one covers a single kind of change.
Modules

Fingertip actions in Make

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

Fingertip1

Create Site Contact

ActionIn the docs only

People who reach you through other channels land in your Fingertip contacts without any copy and paste: this action adds one contact to your site for each bundle it receives.

When to use it
after a form reply, a lead from an ad tool or a new row in a sheet, when you want Fingertip to hold the full list.
Watch out
the module creates one contact per run on each bundle, so a test with Run once can add real entries; clean them up afterwards.
Need help

Need help automating Fingertip with Make?

A person reads every message.

FAQ

Fingertip Make integration FAQ

01Is the Fingertip Make integration free?
Yes, on the Make side. Fingertip is a standard app, so it works from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of up to 5 minutes and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations each month. Your Fingertip subscription is separate: check the Fingertip pricing page for it.
02What do you need to connect Fingertip to Make?
An active Fingertip account and its API key. You find the key in your Fingertip account dashboard, under the API keys section, and paste it when Make asks you to create a connection. Naming the connection is optional. Nothing else is required on the Make side: the same connection then serves all 7 Fingertip modules, so you set it up once and reuse it in every scenario you build with this app.
03Do Fingertip triggers in Make work in real time?
Very likely not. The Make documentation lists the 6 Fingertip triggers by name only; their names and the absence of any instant tag suggest they are scheduled, so they run on the scenario's schedule. Make checks for new bookings, orders, form replies or contacts each time the scenario runs. A new scenario runs every 15 minutes by default; the Free plan cannot go below that, while paid plans can check as often as every minute. For most booking and order flows, that delay is acceptable as long as you know it is there.
04What if a Fingertip module you need is missing in Make?
It depends on what you need. The Fingertip app in Make has 7 modules and no Make an API Call module, so you cannot reach other parts of Fingertip from inside this app. Check first whether another app in your scenario can do the missing step, for example a spreadsheet or a messaging tool. If the gap blocks a real process, the Hack'celeration team can look at your case and suggest a workaround that fits your stack.
05Should you use Make or n8n for Fingertip?
It depends on your tools and habits more than on Fingertip. On Make, the app offers 6 scheduled triggers and 1 action, which cover bookings, orders, form replies and contacts. The same app often has an n8n node as well, so compare the modules each side offers for what you want to automate. If your other automations already live on one of the two platforms, keeping Fingertip there makes maintenance simpler.
Same platform

Other docs you might need on this stack.

Browse all integrations