Peaka Zapier integrationAutomate Peaka with Zapier.
Peaka Zapier integration: 0 triggers, 0 actions, 1 search. Peaka cannot start a Zap and cannot be written to from one. What it offers is a single step that runs one of your saved Peaka queries mid-Zap and hands the rows to the next app.
Verified Trustpilot reviews · AI, automation & growth agency
What the Peaka Zapier integration can and cannot do
Peaka is a data platform that plugs into your sources so you can query them together, without building copy jobs first. The Peaka Zapier integration brings one of those queries into a Zap (an automation with one trigger, then one or more actions): another app starts the Zap, Peaka answers, the next step uses the answer.
A row enriched with fresh figures. A new line in a sheet starts the Zap, Run Peaka Query (With Line Item Support) runs one of your saved queries, and the following step writes its result next to the original line.
A team message with real numbers. A form entry or a closed deal triggers the Zap, a saved query pulls the current figures, and Slack or email posts them for the people who need them.
A handoff between two tools. The rows the query returns come back as line items, so an app that accepts lists can take them all in one go instead of one by one.
What Zapier does not do here: Peaka has no trigger, so nothing happening in Peaka can start a Zap, and it has no action, so a Zap cannot write into Peaka. You run queries already saved there, nothing more. Any Zap using it is therefore multi-step and needs a paid plan. If you are comparing platforms for this kind of data job, see n8n vs Zapier or Make vs Zapier, and the Peaka Make integration page for the same app on Make.
Zapier terms behind a Peaka Zap
Eight words carry the whole page. Each gets one plain line here.
- Zap
- The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Peaka has none, so with Peaka the trigger always comes from another app.
- Action
- What the Zap does once started: the step that writes, sends or moves something, such as posting a message or adding a row.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Search step
- A step that looks up something that already exists in an app so the following steps can use it. Peaka's only step is one.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A search, a filter or a second action makes one, and it needs a paid plan.
- Connection
- Your Peaka account linked to Zapier once, then reused by every Zap step that runs a Peaka query.
What a Peaka Zap costs
Peaka is not reserved for paid plans as an app, but in practice the free plan cannot use it.
- Trigger (other app)Never costs a task
- Successful actionCounted, one by one
- Failed actionNot counted
- Free planTwo-step Zaps only, so no Peaka step
The free plan builds Zaps of two steps only: one trigger and one action. A search turns a Zap into a multi-step Zap, and Peaka's only step is a search, so every Peaka Zap needs a paid plan. On the bill, the trigger never costs a task and each action that succeeds is counted on its own; a failed action is not. How fast the Zap starts depends on the other app's trigger: if it is a polling one, the plan grid below applies.
Connect Peaka to Zapier in three steps
- 01
Open Apps, add a connection
In your Zapier account, open the Apps page and click + Add connection. A dialog with a search box opens. You need a Peaka account, plus access to any project you do not own but want the Zap to query.
- 02
Pick Peaka and sign in
Type Peaka, select it, then click Add connection. Peaka opens in a new tab: sign in there with the account that holds the queries your Zaps will run, not a personal sandbox.
- 03
Grant access
Peaka asks you to let Zapier use the account. Accept. The connection is then reused by every Peaka step in every Zap, so it is a once-per-account job.
Your first Zap with Peaka: look up data for every new row
GoalEach new row in a sheet runs a saved Peaka query, and the result goes to a Slack channel.
- 01
Build: pick the trigger
Start a new Zap and choose the app and event that should start it, here a new row in a sheet. Peaka cannot fill this slot: the first step always belongs to another app.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so you set up the next steps on a real row rather than a guess.
- 03
Add the Peaka step
Add Peaka and choose Run Peaka Query (With Line Item Support). Select the query in the Peaka Queries field. This search makes the Zap multi-step, so a paid plan is required.
- 04
Add the action
Add the app that should receive the result, here Slack, and map the values the Peaka step returned into the message. Test it once and read what came back.
- 05
Publish
When every step returns what you expect, click Publish to switch the Zap on. Only rows added after that point will run the query.
The Peaka search
1 search step looks for data that already exists in Peaka, so a later step can use it.
A search step looks up something that already exists and hands it to the following steps. In the editor, Peaka's search sits at the bottom of the Action event list, under the SEARCH heading.
Run Peaka Query (With Line Item Support)
SearchIn Zapier“Runs Peaka query and returns the result as line items.”
Runs one of the queries saved in your Peaka account and passes the rows it returns to the next steps as line items, a list that later apps can take in one piece.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a query that returns nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Peaka exposes no find-or-create variant, so here the step only reads; it never creates anything.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Peaka Zap breaks
Zapier ties no help article to Peaka, so the cases below are the general limits that apply to any Zap carrying a Peaka step.
None of them shows up as an error in Peaka itself. They show up as a message without figures, a Zap that stopped halfway, or a task count rising faster than planned. When you are stuck, start from the Zapier troubleshooting page.
An empty query stops the Zap
If the query returns nothing and the setting stays on its default, the Zap stops at the Peaka step and the actions after it are skipped.No catch-up on the past
A Zap only reacts to what happens after you switch it on. Rows or records created before you publish never run the query; handling them is a separate job.A loop through the trigger app
If the final action writes into the very place the trigger watches, the Zap sets itself off again and again and burns through the task count.Flood protection after an import
When the trigger app suddenly returns a huge batch, after a bulk import or a migration, Zapier can hold it back instead of running every item.
Need help automating Peaka with Zapier?
A person reads every message.
