AnyDB Zapier integrationAutomate AnyDB with Zapier.
The AnyDB Zapier integration offers 2 triggers, 5 actions and 1 search. Both triggers are instant, so new and updated records reach Zapier at once, and the actions create, update, move records, write pages and upload files in AnyDB, on the free plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the AnyDB Zapier integration does
The AnyDB Zapier integration links AnyDB, a flexible data platform where growing teams keep their records, folders and pages in one place, to Zapier, the tool that connects your apps. AnyDB tells Zapier about new and changed records the moment they happen, and Zapier can create, change, move and file things back.
Three things teams build with it. Tidy filing: New Record watches one folder, and Move Record sends the new items your filter picks to their destination folder. A data hub fed from other tools: Create Record, Create Page Document and Upload File drop form answers, notes and attachments into the right folder. Records that react to each other: Updated Record watches chosen cells, and Update Record writes new values elsewhere.
What Zapier does not do here: every step works on one scope you set by hand, a team, a database and a record ID copied from AnyDB. There is no trigger that watches a whole database at once, no delete action, and the only search, Search Records, asks for a team and a database before anything else.
On speed, no worry: both triggers are instant, so a new or changed record reaches Zapier on any plan, the free one included. To check that Zapier suits the rest of your setup, read our Zapier review and our n8n vs Zapier comparison.
Zapier terms, in plain English
Eight words carry this page. Here is each one in a line.
- Zap
- The automation you set up on Zapier: one trigger, then one or more actions that run whenever the trigger's event happens.
- Trigger
- The event in an app that starts your Zap. As long as the Zap is on, Zapier waits for that event.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you.
- Task
- The unit Zapier charges for: one action your Zap completes successfully. Your plan's limit is a number of tasks.
- Instant vs polling
- An instant trigger is sent by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap keep going only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps that follow can use what it found.
- Multi-step Zap
- Any Zap past one trigger and one action. A filter, a search or a second action makes it one, and it needs a paid plan.
What an AnyDB Zap costs
AnyDB is not a premium app, so it runs on Zapier's free plan. Its two triggers are instant, so the plan's checking interval never holds them back.
- Free plan100 tasks a month, unlimited Zaps
- Steps on the free plan2: one trigger, one action
- AnyDB triggers2 instant, no waiting on any plan
- AnyDB on the free planYes, it is not a premium app
The trigger never costs a task. Every action that succeeds counts once, and an action that fails is not billed. A Zap with three actions uses three times what a one-action Zap does. The free plan comes with 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. A filter, Search Records or a second action makes it multi-step, and that needs a paid plan. The interval grid below only matters for polling triggers.
Connect AnyDB to Zapier in 3 steps
- 01
Open Apps
Go to the Apps page of your Zapier account and click + Add connection. The connection is your AnyDB account linked once, then reused by every Zap that uses AnyDB.
- 02
Pick AnyDB
Type AnyDB in the search box of the dialog, select it and click Add connection. You need an AnyDB account first, since Zapier does not create one for you.
- 03
Sign in and allow
Sign in to AnyDB in the tab that opens and grant Zapier access to the account. For databases or records that a colleague owns, you also need read or write access on them.
Your first AnyDB Zap: file new records automatically
GoalWhen a new record lands in an intake folder in AnyDB, move it under the Invoices folder, but only when its Category cell says Invoice.
- 01
Build: set the trigger
In the editor, under Build, pick AnyDB as the trigger app and New Record as the event. Choose your connection, then the Team and the Database.
- 02
Point it at the folder
Paste the Parent Record ID of your intake folder, copied from its details menu in AnyDB. Only records created under it will start the Zap.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent items of your account, so you map the next steps on a real record, not a guess.
- 04
Add the filter
Click the plus icon, add Filter, pick the Category cell from the trigger, the exact-text rule and the value Invoice. Other records stay where they are. The Zap is now multi-step and needs a paid plan.
- 05
Add Move Record
Add AnyDB as the action app with Move Record. Map the ID of Record to Move from the trigger and paste the New Parent ID of the Invoices folder, which sits outside the intake folder.
- 06
Test, then Publish
Test the action once and check the record moved in AnyDB. Then click Publish. Records already in the folder before that are never picked up.
The 2 AnyDB triggers
2 events start a Zap when something happens in AnyDB, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Record
Instant triggerIn Zapier“Triggers when a new record is created under specified scope.”
This trigger fires when a new record is created under the record you point it at, typically a folder. It does not watch a whole database, only that one branch.
Updated Record
Instant triggerIn Zapier“Triggers when an existing record is updated under specified scope.”
Here the Zap starts when an existing record changes, but only in the cells you list, such as A1 or A2. An option also lets it watch the records nested under that one.
The 5 AnyDB actions
AnyDB gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Record
ActionIn Zapier“Creates a record in AnyDB.”
Adds a new record under a parent record you choose, with its cells filled from Cell Values.
Create Page Document
ActionIn Zapier“Creates a Page in AnyDB.”
Writes a new page in AnyDB, with a name and content that can include HTML, under the record you choose.
Move Record
ActionIn Zapier“Moves a record in AnyDB.”
Moves a record from where it sits to a new parent record.
Update Record
ActionIn Zapier“Updates a record in AnyDB.”
Changes the cells of an existing record, which you identify by its ID.
Upload File
ActionIn Zapier“Uploads a File to AnyDB.”
Stores a file in AnyDB under the record you name, for example a folder record.
The 1 AnyDB search
1 search step looks for data that already exists in AnyDB, so a later step can use it.
A search step looks up something already stored and hands it to the steps after it. Searches sit at the bottom of the Action event list, under SEARCH, and some action fields offer + Add search step to slot one in just before. Whether a search wants an exact value or something close is up to AnyDB. Three settings decide what happens next.
Search Records
SearchIn Zapier“Search records in AnyDB.”
Looks through the records of an AnyDB database and returns what matches, so later steps can use an existing record's ID or values.
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 the steps that depended on it are skipped. Switched on, the Zap carries on with nothing found.
- Create X if it doesn't exist yet?Ticking this turns a search into a find-or-create. AnyDB lists no find-or-create variant for Search Records, so a missing record needs its own Create Record step.
- If multiple search results are found?Three ways out when several records match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When an AnyDB Zap breaks
Zapier attaches no help article to AnyDB. The cases below are the general limits every Zap meets, applied to a records database.
Few of them come with a clear error. The Zap misses records, or runs much more than you meant. When a run fails and the reason is not obvious, our Zapier troubleshooting page is the next step.
Existing records are not replayed
A Zap only reacts to what happens after it is on. Records already in the folder never reach it; moving that backlog is a separate job.Writing into the watched folder
A Zap that creates records under the same parent its New Record trigger watches sets itself off again and again, and burns through tasks fast.A bulk import gets held back
If a trigger suddenly sends a huge batch, after importing a spreadsheet into AnyDB for instance, Zapier's flood protection can hold it back.A search that comes back empty
On the default setting, a Search Records that finds nothing stops the Zap, and the update or move after it never runs.
Need help automating AnyDB with Zapier?
A person reads every message.



