Resources · Zapier integration

Onalu Zapier integrationAutomate Onalu with Zapier.

The Onalu Zapier integration has 1 action and no trigger, and it runs on the free plan. Create Record adds a row to an Onalu table from whatever another app sends, so Onalu is always the receiving end of the Zap, never the starting point.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Onalu Zapier integration is for

Onalu presents itself as a new kind of spreadsheet, built to automate the human part of a business process. Linking it to Zapier means data born in other tools can land in an Onalu table without anyone copying it. The link only works in one direction: into Onalu.

With a single action, the results all look alike, but they serve different teams. A form that fills a table: each response from a sign-up or request form becomes a record through Create Record, ready for whoever handles it in Onalu. A sales log that keeps itself: a deal closed in your CRM writes a row that the operations team picks up. A support queue in a spreadsheet: a new ticket in your help desk becomes a record that someone can assign and follow.

What Zapier does not do for Onalu is just as clear. There is no trigger, so a change in an Onalu table can never start a Zap. There is no search, so a Zap cannot check whether a record already exists before adding one. And there is no update action: once a record is in, Zapier cannot touch it again. Corrections happen in Onalu, by hand.

To weigh Zapier against other tools for this kind of job, see Make vs Zapier or the list of Zapier alternatives.

Vocabulary

Zapier vocabulary in one minute

Eight words cover this page. Each keeps the meaning given here.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Onalu has none, so another app always plays this part.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you. Create Record is one.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan counts exactly those.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval and keeping only the unseen ones.
Instant trigger
A trigger the app reports itself, calling Zapier the moment the event happens, so nothing waits for the next check.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
Connection
Your account of an app linked to Zapier once, then reused by every step that uses that app.
Cost

What Onalu costs in Zapier tasks

Onalu is not a premium app on Zapier, so it works on the free plan. The bill is counted in tasks, and only completed actions count.

  • Free plan100 tasks per month, unlimited Zaps
  • One record addedOne task
  • Record that failsNot counted
  • Filter before the actionMulti-step Zap, paid plan

Each record that Create Record adds successfully is one task. A record that fails to go in is not counted. The trigger from the other app never costs anything, and neither do Zapier's checks on it, however often they run. On the free plan, a Zap holds two steps: the other app's trigger and Create Record, nothing more. Put a filter in front of the action, to keep only some responses, and the Zap becomes multi-step, which needs a paid plan. How fast a record appears depends on the other app's trigger, not on Onalu.

Connect

Connect your Onalu account in three steps

  1. 01

    Open the Apps page

    In Zapier, go to Apps and click + Add connection. You need an Onalu account, plus write access on any table you do not own and want the Zap to fill with records.

  2. 02

    Choose Onalu

    Search Onalu by name in the dialog, select it and click Add connection. A tab opens where you sign in to the Onalu account that holds the target table.

  3. 03

    Sign in and grant access

    Sign in to Onalu in that tab and allow Zapier to reach the account. The connection then appears on the Apps page, ready for any Zap that writes to Onalu.

First Zap

Your first Onalu Zap: every form response becomes a record

GoalEach new response to a form is added as a record in an Onalu table, with every answer in the matching field.

  1. 01

    Pick the trigger app

    Create a Zap and choose the form tool as the app that starts it, with its new-response event. Onalu cannot start a Zap, so this first card always belongs to another app.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent responses of the connected account, so you map the fields on a real answer.

  3. 03

    Add Create Record

    Add Onalu as the action with Create Record. Paste the table's address copied from its settings in Onalu, then fill the data mapping.

  4. 04

    Map each field

    On each row, type the exact name of an Onalu field on the left and pick the matching answer on the right. Names are case-sensitive.

  5. 05

    Test, then publish

    Test the action and check the new record in Onalu. Then click Publish. Responses sent before that moment are not added.

Actions

The Onalu action

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

1

Create Record

Action

In Zapier“Creates a Record in an Onalu Table.”

Adds one row to an Onalu table, filled with values another app delivered. You give it the table's address, then a mapping where each line pairs an Onalu field name with the value it should get.

When to use it
any flow where a person in Onalu has to pick up what arrived somewhere else, a request, a lead or a ticket.
Watch out
field names in the mapping are case-sensitive, so a name typed in lowercase will not match a capitalized column.
When it breaks

When an Onalu Zap breaks

Zapier links no help article to Onalu, so the cases below are the general traps, applied to this app.

Four mechanisms explain what goes wrong with a Zap that writes to Onalu. They are not bugs: Zapier works this way, and each one has a simple answer. If a Zap still misbehaves, the Zapier troubleshooting page goes further.

  • Old data never arrives

    A Zap only reacts to what happens after it is switched on. Responses or deals that existed before are not copied into Onalu; moving them is a separate job.

  • A table that loops

    If the trigger app watches a place your Zap also writes to, each new record can set the Zap off again and use up tasks very fast.

  • A big batch held back

    When the trigger app suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold the runs back.

  • Each item counted once

    On a polling trigger, Zapier remembers what it has already seen, so the same response does not create two records.
Need help

Need help automating Onalu with Zapier?

A person reads every message.

FAQ

Onalu and Zapier: frequent questions

01Is the Onalu Zapier integration free?
Yes. Onalu is not a premium app, so it works on Zapier's free plan, which includes 100 tasks per month and unlimited Zaps. On that plan, a Zap holds two steps: the trigger of another app and Create Record. That is enough for the simplest case, every item becoming a record. Once you add a filter to keep only some items, or a second action, the Zap becomes multi-step and needs a paid plan.
02How many tasks does an Onalu Zap use?
One task per record Create Record adds successfully. The trigger of the other app costs nothing, and neither do Zapier's checks on it. A record that fails to go in is not counted against the plan, whatever stopped it. So the bill follows the number of items the other app produces: a form that gets many responses fills the monthly quota faster than a CRM that closes a few deals.
03Can an Onalu Zap run in real time?
Onalu has no trigger at all, so the speed of the Zap depends entirely on the other app that starts it. If that app offers an instant trigger, the record is added right after the event. If it uses a polling trigger, Zapier checks at the interval of your plan: 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. Nothing on the Onalu side changes that timing.
04What does connecting Onalu to Zapier require?
An Onalu account, plus write access on any table you do not own and want the Zap to fill. You add the connection from the Apps page of Zapier, choose Onalu, sign in in the tab that opens and grant access. Then, for each Zap, open the target table's settings in Onalu, make sure the option that lets outside tools reach it is on, and copy the table's address into Create Record.
05Why does Create Record put nothing in some fields?
Most often because a field name in the data mapping does not exactly match the column in Onalu. Names are case-sensitive: a field called Email in Onalu will not receive a value mapped to email. Check each line of the mapping against the table, letter by letter. Another cause is the table's address: if the option that lets outside tools reach the table was switched off, the action cannot write to it at all.
06What if the Onalu operation needed is not in Zapier?
Then it is not available, whatever the plan. Zapier lists a single operation for Onalu, Create Record, with no trigger, no search and no update. Anything that needs to react to a change in Onalu, find an existing record or edit one cannot be built with Zapier alone. For those needs, the work stays inside Onalu itself, by hand, while Zapier covers the single step of adding new records to a table you choose.
07Zapier, Make or n8n for Onalu?
Compare on criteria rather than looking for a winner. Coverage: on Zapier, Onalu offers one action and nothing else, so the tool only fits flows that end with a new record. Speed: the timing comes from the trigger app and your plan's interval when that trigger is polled. Cost: each record is a task, and a filter makes the Zap a paid one. Hold those three points against what the other tools offer for Onalu.
Same platform

Other docs you might need on this stack.

Browse all integrations