Resources · Make integration

A&A/FITPASS Calltracking Make integrationAutomate A&A/FITPASS Calltracking with Make.

Can Make log events into A&A/FITPASS Calltracking without a line of code? Yes. The A&A/FITPASS Calltracking Make integration offers 2 action modules, Register an Event and Make an API Call. Below, you link your account and build a first working scenario.

Try the A&A/FITPASS Calltracking integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the A&A/FITPASS Calltracking Make integration do?

The A&A/FITPASS Calltracking Make integration links your account to Make so that a scenario, the automation you build in Make, can write into the app for you. A scenario is a chain of modules, one brick each. Both bricks of this app are actions, so something else has to start the scenario.

Turn a form entry into an event. Put the trigger of your form tool first, then Register an Event. Each new entry becomes an event in A&A/FITPASS Calltracking, and nobody retypes it. The 123FormBuilder Make integration page shows how a form app behaves inside Make.

Log activity from another channel. A chat or phone tool you already connect to Make can hand its data to the same module, so the record stays in one place.

Reach what the modules leave out. Make an API Call sends a request to any endpoint of the app's API with the connection you already have.

What Make does not offer here: a trigger. No module watches the app, so nothing that happens in A&A/FITPASS Calltracking can start a scenario by itself. Make also states that its documentation for this app is limited, since little public information exists about it. The app may also exist as an n8n node; the n8n vs Make page compares the two tools.

Connect

How do you connect A&A/FITPASS Calltracking to Make?

  1. 01

    Open the connection window

    Add any A&A/FITPASS Calltracking module to your scenario, then click Create a connection. A connection is your account linked to Make once, and every module of the app reuses it.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, it helps when you run several accounts. Then either approve Make on the app's own authorization page, or paste the key the app gives you, depending on what the window asks for.

  3. 03

    Save and check the module

    Click Save. Back in the module, the connection now appears in the dropdown, and Make can list the objects it is able to read from your account.

First scenario

Build your first scenario with A&A/FITPASS Calltracking

GoalWhen a new entry arrives in another app, Make registers a matching event in A&A/FITPASS Calltracking.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to place the first module.

  2. 02

    Pick what starts it

    Search the app that holds your source data, a form tool for instance, choose its trigger and click Create a connection to link that account too.

  3. 03

    Add Register an Event

    Click the + on the right of the first module, search A&A/FITPASS Calltracking and pick Register an Event. Fill its fields by mapping the data the first module sends.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received; a bundle is one item passed along, here one entry.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A brand new scenario checks every 15 minutes by default, and you can keep that value to start. Adjust it if needed, then switch the scenario on.

Modules

What A&A/FITPASS Calltracking can do in Make

A&A/FITPASS Calltracking gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

A&A/FITPASS Calltracking1

Make an API Call

ActionIn the docs only

Make an API Call gives you access to anything the A&A/FITPASS Calltracking API exposes beyond the ready-made module. Your scenario sends its own request to the endpoint you choose, reusing the connection you created once.

When to use it
your process needs an operation that Register an Event does not cover.
Watch out
Make's documentation for this app is limited, so keep the app's own API reference at hand to pick the right endpoint.
A&A/FITPASS Calltracking2

Register an Event

ActionIn the docs only

Register an Event records an event in your A&A/FITPASS Calltracking account straight from a scenario, filled with data that earlier modules pass along. Given the app's name, an event is likely a tracked call; check the fields to confirm.

When to use it
a form entry or a message in another app should become an event without anyone copying it by hand.
Watch out
Make gives no description of this module, so read its fields in the editor and test with Run once before switching the scenario on.
Need help

Need help automating A&A/FITPASS Calltracking with Make?

A person reads every message.

FAQ

Frequently asked questions

01Is the A&A/FITPASS Calltracking Make integration free?
Yes, you can start on the Free plan, because A&A/FITPASS Calltracking is a standard app and standard apps are open on every plan. The Free plan allows 2 active scenarios, runs a scheduled scenario at most every 15 minutes, stops a run after 5 minutes, and caps files at 5 MB with 512 MB of data transfer. Every time a module processes one bundle, Make counts one operation on your plan. Paid plans lower the minimum interval to 1 minute and remove the cap on active scenarios.
02What do you need to connect A&A/FITPASS Calltracking to Make?
An A&A/FITPASS Calltracking account and a Make account are enough, since Make lists no other prerequisite for this app. You click Create a connection in any module of the app, optionally name it, then either authorize Make on the app's page or paste the key the app provides, and click Save. That single connection then serves both modules, including Make an API Call, so you never link the same account twice inside one scenario.
03Does the A&A/FITPASS Calltracking module react in real time?
No, because the app has no trigger in Make: none of its modules can start a scenario. Your scenario starts elsewhere instead. Either you place the trigger of another app first, and the timing then depends on that app's trigger, or you rely on the schedule of the first module, which checks every 15 minutes by default on a new scenario. Paid plans let that schedule go down to 1 minute. Register an Event then runs as soon as the scenario reaches it.
04What if an A&A/FITPASS Calltracking module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the A&A/FITPASS Calltracking API through the connection you already set up, so you are not limited to Register an Event. Be aware that Make describes its own documentation for this app as limited, because little public information is available. Plan to consult the reference published by A&A/FITPASS Calltracking itself, then test your request with Run once before activating the scenario.
05Should you use Make or n8n for A&A/FITPASS Calltracking?
It depends on what each tool offers for this app. In Make you get 2 modules, Register an Event and Make an API Call, with no trigger. Many apps also have an n8n node, but that is not confirmed here, so check the n8n node list for A&A/FITPASS Calltracking before deciding. If your other scenarios already live in Make, adding this app there saves you from splitting your work across two editors. The comparison page linked above describes the differences between the two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations