Resources · Make integration

TAAPI.IO Make integrationAutomate TAAPI.IO with Make.

Can Make fetch TAAPI.IO data for you on its own? Yes: the TAAPI.IO Make integration gives you 5 action modules and no trigger. This page is for builders who know TAAPI.IO, and it walks you from the connection to a first scenario that runs on a schedule.

Try the TAAPI.IO integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the TAAPI.IO Make integration do for you?

The TAAPI.IO Make integration lets a Make scenario (the automation you build, a chain of modules) ask TAAPI.IO for data and hand the answer to your other tools. Each module is one brick of that chain. TAAPI.IO brings 5 of them, all actions, so the scenario starts from a schedule or from another app.

Keep an indicator flowing into your tools. Put Get Indicator (Single) after a schedule, then add a module from your spreadsheet or chat app. Each run fetches one indicator and passes it along as a bundle, the item that travels from one module to the next.

Check several readings in one pass. When one value is not enough, Get Indicator (Multiple) and Get Indicators (Bulk) gather more in a single step, so the rest of the scenario works from one answer instead of a pile of separate calls. Before any of that, Get Exchange Symbols helps you see which symbols you can ask about.

Reach what the modules skip. Make an API Call reuses your connection to query any TAAPI.IO endpoint, which covers requests the four named modules do not offer.

One honest caveat: Make's own documentation for TAAPI.IO is limited and says there is not enough public information for a complete guide. Expect to learn each module by opening it and reading its fields. If you are weighing tools, the n8n vs Make comparison lays out the criteria, the Make pricing page explains plans and operations, and Make troubleshooting helps when a run fails.

Connect

How do you connect TAAPI.IO to Make?

  1. 01

    Add a TAAPI.IO module

    In your scenario, click the + and type TAAPI.IO in the search box. Pick any of its modules, for instance Get Indicator (Single), then click Create a connection. A connection is your TAAPI.IO account linked to Make once and reused by every module.

  2. 02

    Name it and authorize

    Give the connection a name if you plan to link more than one account. Then follow what the window asks: authorize Make on the TAAPI.IO page, or paste the key TAAPI.IO gives you. Make's documentation lists no other prerequisite.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the dropdown of every TAAPI.IO module, so the next module you add only asks you to pick it from the list instead of logging in again.

First scenario

Your first scenario with TAAPI.IO

GoalWhen the schedule fires, Make lists what TAAPI.IO can read and fetches one indicator for the symbol you chose.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle. Search TAAPI.IO and pick Get Exchange Symbols as your first module.

  2. 02

    Connect and fill the first module

    Click Create a connection, finish the three steps above, then fill the fields Make shows. Once the connection exists, Make can suggest values it reads from your account.

  3. 03

    Add the indicator module

    Click the + on the right of the first module, add Get Indicator (Single) and map what it needs from the previous bundle. Mapping means dragging a value from one module into a field of the next.

  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 confirm the indicator came back before anything goes live.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the Scheduling. A new scenario runs every 15 minutes by default. Pick the interval that fits, then switch the scenario on.

Modules

What each TAAPI.IO module does

TAAPI.IO gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

TAAPI.IO1

Get Exchange Symbols

ActionIn the docs only

This one tells you which symbols TAAPI.IO can work with, as its name suggests, which saves you from guessing before you ask for an indicator. Make's docs give no description, so open it and read the fields listed.

When to use it
at the start of a scenario, to feed a symbol into the indicator module that follows.
Watch out
a list can produce many bundles, and each bundle passed to the next module costs one operation.
TAAPI.IO2

Get Indicator (Multiple)

ActionIn the docs only

You get several readings from a single module here, instead of stacking copies of the single version. The name points to more than one indicator per call; the exact fields only show once your connection is set.

When to use it
when the next step, a sheet row or a message, needs a few values side by side.
Watch out
run it once first and read the bundle, so you know how the values are arranged before mapping them.
TAAPI.IO3

Get Indicator (Single)

ActionIn the docs only

The simplest way to pull one TAAPI.IO indicator into a scenario and pass it to your other tools. It is the module to learn first, because its output is easy to read after a test run.

When to use it
when a scenario only needs one value, for example to post it in a channel or append it to a sheet.
Watch out
if you catch yourself adding it three or four times in a row, the Multiple or Bulk module is probably the better pick.
TAAPI.IO4

Get Indicators (Bulk)

ActionIn the docs only

Bulk is the heavy option: it gathers a larger set of indicators in one step, judging by its name, so the scenario handles one answer instead of many small ones. Make documents none of its fields, so explore it with a test.

When to use it
when Multiple feels too narrow for the number of readings you track.
Watch out
a big answer can split into many bundles downstream, and every module that processes them counts operations.
TAAPI.IO5

Make an API Call

ActionIn the docs only

Your way out when none of the four named modules covers a request. It calls any endpoint of the TAAPI.IO API with the connection you already created, so there is nothing new to authorize.

When to use it
when TAAPI.IO offers a request that Make has no dedicated module for.
Watch out
you build the request yourself, so keep the TAAPI.IO API reference open, since Make's documentation for this app is limited.
Need help

Need help automating TAAPI.IO with Make?

A person reads every message.

FAQ

TAAPI.IO and Make: common questions

01Is the TAAPI.IO Make integration free?
Yes, TAAPI.IO is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one execution of one module on one bundle. Your TAAPI.IO subscription is a separate matter that this page does not cover.
02What do you need to connect TAAPI.IO to Make?
A TAAPI.IO account and a Make account. Make's documentation lists no prerequisite and no official steps for this app, so the generic flow applies: add a TAAPI.IO module, click Create a connection, name it if you like, authorize Make on the TAAPI.IO page or paste the key TAAPI.IO gives you, then click Save. The connection is reused by every TAAPI.IO module in your scenarios, so this setup happens once per account.
03Does the TAAPI.IO Make integration react in real time?
No, because TAAPI.IO has no trigger module in Make, only actions. A scenario that uses it starts in one of two ways. Either you set a schedule on the first module, every 15 minutes by default, with 15 minutes as the floor on the Free plan and 1 minute on paid plans. Or you place a trigger from another app first, and the TAAPI.IO modules run whenever that app starts the scenario.
04What if a TAAPI.IO module is missing in Make?
Use Make an API Call. It reaches any endpoint of the TAAPI.IO API through the connection you already have, so a request without a dedicated module is still possible. Keep in mind that Make's documentation for TAAPI.IO is limited and says there is not enough public information for a complete guide. You will rely on the TAAPI.IO API reference to write the request, then on Run once to check what comes back before the scenario goes live.
05Make or n8n for TAAPI.IO?
It depends on what you need to build. On Make, TAAPI.IO gives you 5 action modules, including Make an API Call, and no trigger, so every scenario starts from a schedule or another app. Many apps also have an n8n node, so check whether one exists for TAAPI.IO and what it covers. Then compare the two on the modules available for your use case and on the editor your team prefers, rather than on the tool's reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations