Noloco Zapier integrationAutomate Noloco with Zapier.
The Noloco Zapier integration gives you 2 triggers, 3 actions and 1 search. Zapier watches the tables of your Noloco app for new and edited records, and can create, update, delete or look up records in them from any other tool you use.
Verified Trustpilot reviews · AI, automation & growth agency
What the Noloco Zapier integration does for you
Noloco lets you build internal tools and client portals without code, on top of its own data tables. Zapier plugs those tables into the rest of your stack: a new or edited record can start an automation, and other apps can write records back into Noloco. Every operation works on one table at a time.
Three things you can build. A portal that talks back: Record Created picks up each request a client submits in your Noloco portal and sends it to the person who handles it. A database that fills itself: Create a New Record drops every form answer or paid order into the right Noloco table, so nobody copies data by hand. Status that stays in sync: Search for a Record finds the matching row and Update a Record changes its status when something happens elsewhere, like an invoice getting paid.
Now the limits. Both triggers are polling triggers, so a change in Noloco reaches your Zap at the next check, not the second it happens. The triggers only cover the records of your tables: a new record or an edited one, nothing else. And a Zap never looks back, so records that existed before you published it stay untouched.
Not sure Zapier is the right tool here? Our Zapier review lays out the trade-offs, and n8n vs Zapier compares cost and control.
Zapier vocabulary in one minute
Eight terms you will meet in the editor. Each one is explained here once, then used as is.
- Zap
- The automation you build on Zapier: 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, like a new record in a Noloco table. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, like Update a Record.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance is a count of these.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer; an instant one is pushed by the app. Both Noloco triggers are polling.
- Filter
- A step that lets the Zap go on only when the incoming record meets your condition, and stops it otherwise.
- Search step
- A step that looks up a record that already exists, so the steps after it can update or use it.
- Connection
- Your Noloco account linked to Zapier once, then reused by every step that reads from or writes to Noloco.
What Noloco costs you in Zapier tasks
Noloco is not a premium app, so it works on the free plan.
- Free plan100 tasks per month, unlimited Zaps, two steps max
- Noloco triggers2, both polling
- BilledEach successful action, never the trigger
- Premium appNo
The trigger never costs a task, and neither do Zapier's checks for new records, however often they run. You pay one task for each action that succeeds; one that fails costs nothing. The free plan builds two-step Zaps only: one trigger, one action. A search followed by an update, a filter on a status, or a second action all make the Zap multi-step, and that needs a paid plan. Your plan also sets how often Zapier checks Noloco for changes.
Connect your Noloco account in three steps
- 01
Open the connection dialog
Go to the Apps page of your Zapier account and click + Add connection. You need a Noloco account with access to the app and the tables your Zaps will work on.
- 02
Pick Noloco
Type Noloco in the search box of the dialog, select it from the results, then click Add connection. A new tab opens on the Noloco side so you can sign in.
- 03
Sign in and grant access
Log in to Noloco in that tab and allow Zapier to use the account. The connection then appears on the Apps page, and every Zap that touches Noloco reuses it.
Your first Zap: answer every portal request and mark it handled
GoalEach new request in your Noloco portal is emailed to the right person, then the record is marked as notified.
- 01
Pick the Noloco trigger
Build: create a Zap, choose Noloco and Record Created, then select your connection and the Requests table. The Table field is required, so pick it before anything else.
- 02
Test on a real request
Test: Zapier brings back the three most recent records of that table. Pick one with real content so the next steps are mapped on actual data.
- 03
Send the email
Add Gmail and Send Email. Map the requester, the subject and the details from the record so whoever handles it gets everything in one place.
- 04
Mark the record
Add Noloco and Update a Record on the same table, and set a status field to notified. Two actions make this a multi-step Zap, so it needs a paid plan.
- 05
Test and publish
Run each step once, then check the email and the record. Click Publish when both look right. Requests from before that moment are not sent.
Noloco triggers in Zapier
2 events start a Zap when something happens in Noloco. Zapier checks for them at the interval your plan allows.
Record Created
Polling triggerIn Zapier“Triggers when a new record is created in your app.”
Starts your Zap when a new record appears in the Noloco table you choose. It is the natural starting point for a client portal or an internal request form built in Noloco.
Record Updated
Polling triggerIn Zapier“Triggers when an existing record is updated in your app.”
Fires when an existing record in your chosen Noloco table is edited. Status changes are the classic case: an order moving to shipped, a task moving to done, a request getting approved.
Noloco actions in Zapier
Noloco gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a New Record
ActionIn Zapier“Creates a new record in a collection.”
Adds a row to a Noloco table from whatever another app sends: a form answer, an order, a new contact.
Delete a Record
ActionIn Zapier“Deletes an existing record from a collection.”
Removes a record from a Noloco table, on a signal from another app.
Update a Record
ActionIn Zapier“Updates a existing record in a collection.”
Changes the values of a record that already exists in a Noloco table, usually right after a search found it.
Noloco search: find a record by a unique field
1 search step looks for data that already exists in Noloco, so a later step can use it.
Noloco's search sits at the bottom of the Action event list, under the SEARCH heading. It is how a Zap gets hold of an existing record before updating or deleting it. Three settings decide what happens when the search does not find exactly one match.
Search for a Record
SearchIn Zapier“Search for an existing record by unique fields.”
Looks up a record in the Noloco table you pick, using a field whose value is unique to one row, such as an email or an order number.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap and skips the steps that depended on it. 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. Noloco does not offer that variant, so this box does not apply to its search.
- If multiple search results are found?Three ways out: keep the first match, the default, stop the Zap, or pass every match on at once.
When a Noloco Zap breaks
Zapier links no help article to Noloco, so the known weak points are Zapier's general rules, applied to how Noloco works.
Four cases to check first, all tied to how Zapier itself works. For anything else, the Zapier troubleshooting page covers the usual causes.
Existing records are not picked up
A Zap only reacts to records created or edited after you publish it. Rows already in your Noloco tables are never sent; moving them is a separate job.Record Updated plus Update a Record
A Zap that updates the table its own Record Updated trigger watches sets itself off again with every write, and burns through your tasks fast.Bulk imports held back
Importing a large batch of rows into a Noloco table can return a huge batch at the next check. Zapier's flood protection may hold it back.Same record, one run
Zapier remembers what a polling trigger has already seen, so a record that was already picked up does not start Record Created a second time.
Need help automating Noloco with Zapier?
A person reads every message.
