Resources · Make integration

Peaka Make integrationAutomate Peaka with Make.

Need the rows of a Peaka query inside another tool? The Peaka Make integration gives you 2 modules: one search that returns query results as rows, and one action that sends an authorized call to Peaka. This page links your API key, builds a first scenario and explains both modules.

Try the Peaka integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Peaka Make integration do for you?

The Peaka Make integration lets a Make scenario (the automation you build, a chain of modules) read the result of a Peaka query and reuse it in any other app. Each module is one brick of that chain. Peaka has two of them in Make: a search and an action, and no trigger.

Feed a report with fresh rows. A form, a CRM or a spreadsheet starts the scenario, Search Peaka Query runs your query, and every row comes back as a bundle, one item that flows to the next module. Map those rows into the tool that needs them.

Answer a request with data. When a colleague asks for figures through another app, the same search looks them up in Peaka and hands them over without anyone opening a dashboard.

Reach what the search does not cover. The Make and API Call module sends an authorized request to Peaka with the connection you already made, for the cases the search leaves out.

What Make will not do here: Peaka has no trigger, so nothing starts a scenario from inside Peaka. The scenario opens on another app or on Make's own schedule, every 15 minutes by default. The Peaka documentation is also flagged as AI-generated by Make, so check any detail that matters with Peaka. If you are new to the tool, the Make training covers the editor step by step, and n8n vs Make helps if you are still choosing a platform.

Connect

How do you connect Peaka to Make?

  1. 01

    Generate an API key in Peaka

    In Peaka, click the Settings icon on the dashboard and open the API Keys tab in the sidebar. Click Add First API Key (or API Key), give it a name, press Generate, then copy the key shown in the window.

  2. 02

    Add a Peaka module in Make

    Open your scenario, add either Peaka module and click Create a connection. A connection is your Peaka account linked to Make once, then reused by both modules. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied from Peaka into the credentials field and confirm. Make can now read your queries. The key is the only credential Peaka asks for, and you need an active Peaka account for it to work.

First scenario

Build your first scenario with Peaka

GoalWhen another app sends a new request, Make runs your Peaka query and returns its rows, one bundle each, ready for the next module.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app that starts the flow, for example the form or CRM where requests arrive, since Peaka itself has no trigger.

  2. 02

    Add Search Peaka Query

    Click the + on the right of the first module, search for Peaka and choose Search Peaka Query. Click Create a connection and paste your API key.

  3. 03

    Fill the module

    Once connected, Make lists what it can read from Peaka. Pick the Peaka query whose rows you want. The query itself is built on the Peaka side, so prepare it there first.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received. Each row of the query shows up as its own bundle.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default, 15 minutes at least on the Free plan) and switch the scenario on. Add the destination module later with the same +.

Modules

What the Peaka modules do

Peaka gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Peaka1

Make and API Call

Action

In Make“Performs and arbitrary authorized API call”

Sends an authorized request to Peaka through the connection you already created, so you can reach something the search module does not offer.

When to use it
a colleague needs a Peaka feature that has no dedicated module in Make, and you know which request the Peaka API expects.
Watch out
you write the request yourself, so check the details against the Peaka documentation before switching the scenario on.
Peaka2

Search Peaka Query

Search

In Make“Searches and returns the result of Peaka Query as rows”

Runs a Peaka query and hands its result back as rows, one bundle per row, so the next module can use each line on its own.

When to use it
a request comes in and you want the matching figures from Peaka pushed into a sheet, a message or a CRM record.
Watch out
a search can return zero, one or many rows, and every module after it runs once per row, which counts as extra operations.
Need help

Need help automating Peaka with Make?

A person reads every message.

FAQ

Peaka and Make: common questions

01Is the Peaka Make integration free?
Yes, Peaka is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one execution of one module on one bundle. You still need an active Peaka account, with its own subscription.
02What do you need to connect Peaka to Make?
An active Peaka account and an API key. You create the key in Peaka under Settings, API Keys tab, with the Add First API Key or API Key button, then Generate. In Make, add a Peaka module, click Create a connection, give it a name if you want and paste the key. The same connection then serves both Peaka modules, so you only set it up once, whichever of the two modules you add first.
03Can Peaka start a Make scenario in real time?
No, Peaka has no trigger module in Make, neither scheduled nor instant. A scenario that uses Peaka must start another way. Either a trigger from another app opens the flow, for example a new form entry, or you let Make run the scenario on its own schedule, which is every 15 minutes by default and at least 15 minutes on the Free plan. Paid plans can go down to 1 minute between runs.
04What if the Peaka module you need is missing in Make?
It depends on what is missing. Peaka has only 2 modules in Make, so start by checking whether Search Peaka Query already returns what you need once the query is built on the Peaka side. If the gap is in another tool, look for that tool's own app in Make. The Peaka documentation in Make is also flagged as AI-generated, so confirm important details with Peaka. For a flow that still does not fit, the team behind this site can review it with you.
05Should you use Make or n8n for Peaka?
It depends on the tool you already run. In Make, Peaka offers a query search and an authorized call, linked with a single API key and started by another app or by a schedule. Peaka may also exist as a node in n8n, so check what each platform offers for your exact use case before you decide. The comparison page on this site lays out the differences between the two platforms, without ranking one above the other.
Same platform

Other docs you might need on this stack.

Browse all integrations