Resources · Zapier integration

Xata Zapier integrationAutomate Xata with Zapier.

The Xata Zapier integration gives you 4 actions and no trigger. Zapier can write records into your Xata tables, with or without an ID you choose, but something else has to start the Zap. Here is what that means, what it costs and where it breaks.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What Zapier can do with your Xata tables

Connecting Xata to Zapier lets other apps push data into your Xata database without a line of code. Zapier only writes: it adds a record, or updates or replaces one when you hand it the record ID. It cannot notice changes inside Xata, so the Zap always starts in another tool.

Three jobs come up again and again once the connection is live.

A clean log of incoming data. Every sign-up, order or form answer from another app lands as a fresh row through Create Record, and Xata hands out the ID itself. Good for a growth team that wants raw events in one table.

A table that mirrors another system. If your CRM or shop already gives each customer a stable ID, Create or Update Record With a Given ID keeps one row per customer and only touches the columns you map. Run it twice on the same person and you still have one row.

A guarded first insert. Create Record With a Given ID refuses to write when that ID is already taken. It is the action to pick when a duplicate would be worse than a missed row, for example on invoice numbers.

What Zapier does not do here: it cannot read from Xata. There is no trigger, so nothing happening in your database can start a Zap, and there is no search step, so a Zap cannot look up an existing record before writing. Deleting a record is not offered either. If you need any of that, the Xata n8n integration and the Xata Make integration cover the same app on the two other platforms, so you can compare before you commit.

Vocabulary

Zapier words you will meet on this page

Seven terms, in plain English. Once they are clear, the rest of the page reads fast.

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. Xata has none on Zapier, so your trigger always lives in another tool.
Action
What the Zap does once it has started. Here, every action writes a record into one of your Xata tables.
Task
The unit Zapier bills: one action that completes successfully. The number on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer by Zapier. An instant one is reported by its app the moment it happens.
Filter
A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
Connection
Your Xata account linked to Zapier once, then reused by every step of every Zap that writes to Xata.
Cost

What a Xata Zap really costs

Zapier bills tasks, and each Xata action that succeeds is one task. The trigger in the other app costs nothing.

  • Xata triggerNone, the Zap starts in another app
  • Each successful action1 task
  • Failed actionNot counted
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, works on the free plan

Xata is not a premium app, so it works on the free plan: 100 tasks a month and Zaps of two steps, one trigger and one action. Add a filter or a second action and the Zap becomes a multi-step Zap, which needs a paid plan. An action that fails, such as a duplicate ID, is not counted. How fast the Zap starts depends on the trigger app, using the grid below when that trigger is a polling one. Plan the filter early, it changes the bill.

Connect

Connect Xata to Zapier in three steps

  1. 01

    Open the connection dialog

    In your Zapier account, go to the Apps page and click + Add connection. A dialog asks which app you want to link: type Xata and pick it from the results.

  2. 02

    Sign in to Xata

    Click Add connection. Xata opens in a new tab and asks you to sign in. Use the account that owns the database, or one with write access to the tables your Zaps will fill.

  3. 03

    Grant access

    Allow Zapier to act on your Xata account. The connection is saved once and every Xata step, in every Zap, can reuse it. You only redo this if you revoke the access.

First Zap

Your first Xata Zap: store each new sign-up once

GoalEvery new sign-up collected in your form tool becomes one row in a Xata table, keyed on the email so the same person never appears twice.

  1. 01

    Build: pick the trigger

    Create a Zap, choose your form tool and its new-response event. Test it: Zapier pulls in the three most recent answers so you map fields on a real one.

  2. 02

    Add a filter

    Add a Filter step from the plus icon. Pick a field the trigger brought back, a rule that matches its type, and the value to compare with, so only the answers you want go through. This makes the Zap multi-step, so a paid plan.

  3. 03

    Add the Xata action

    Pick Xata and Create or Update Record With a Given ID. Choose the Table, then map the email into the record ID and the other answers into their columns.

  4. 04

    Test the action

    Run the test and open the table in Xata. You should see one row. Run it again with the same answer: the row is updated, not doubled.

  5. 05

    Publish

    Click Publish to switch the Zap on. From now on, each new answer that passes the filter costs one task. Earlier answers are not picked up.

Actions

The 4 Xata actions, and which one to pick

Xata gives you 4 actions. 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“Create a record with an automatically generated id.”

Adds a new row to the table you choose and lets Xata generate its ID. You map columns, Zapier writes, and that is the whole job.

When to use it
logging events that will never be updated later, such as each paid order or each support ticket opened.
Watch out
since Xata invents the ID, running the same data twice gives you two rows.
2

Create or Update Record With a Given ID

Action

In Zapier“Create or partially update a record with the provided record id. In case the record id already exists in the table, existing values are updated and values of columns that are not referenced in the update are preserved.”

Creates the row if the ID is new. If it exists, only the columns you mapped change, and the others keep their current values.

When to use it
keeping a customer table in sync with a CRM, where each update carries just a few fields.
Watch out
the ID decides which row is touched, so give it a stable value, such as the customer ID from your CRM.
3

Create or Replace Record With a Given ID

Action

In Zapier“Create or replace a record with the provided record id. In case the record id already exists in the table, the record is fully replaced overwritting all existing column values.”

Works like an overwrite with a safety net: a new ID gets a new row, and an existing one sees Zapier rewrite the full record: every column takes the value from this run.

When to use it
when the source app always sends the complete picture, such as a full product sheet.
Watch out
any column you forgot to map is wiped on an existing row. Prefer the update action when in doubt.
4

Create Record With a Given ID

Action

In Zapier“Create a record with the provided record id. In case the record id already exists in the table, the operation is cancelled and an error is returned.”

Writes a new row under an ID you supply, and refuses to touch anything if that ID already exists: the step is cancelled and Zapier reports an error.

When to use it
invoice or contract numbers, where overwriting an existing row would be a real problem.
Watch out
a refused write is a step in error, so the row you expected is not written.
When it breaks

When a Xata Zap breaks

Zapier does not attach any help article to Xata, so the known traps are the general ones, plus the ID rules of the actions themselves.

None of these are bugs. They are how Zapier and these four actions behave, and each one is cheaper to plan for than to discover in the Zap history. If a Zap still misbehaves, see Zapier troubleshooting.

  • Rows from before the Zap stay behind

    A Zap only reacts to what happens after you publish it. Data that already sat in the source app is not copied into Xata; moving that backlog is a separate job.

  • A taken ID cancels the write

    With Create Record With a Given ID, an existing ID stops the step with an error. The task is not counted, but the row is not written either.

  • Replace wipes forgotten columns

    Create or Replace Record With a Given ID rewrites the whole record. A column left unmapped loses its value on rows that already existed.

  • A bulk import can be held back

    If the trigger app suddenly releases a huge batch, after an import or a migration, Zapier's flood protection can pause it before Xata sees a single row.
Need help

Need help automating Xata with Zapier?

A person reads every message.

FAQ

Xata Zapier integration: frequent questions

01Is the Xata Zapier integration free?
Yes, on the free plan, because Xata is not a premium app. That plan gives 100 tasks a month and Zaps of two steps, so one trigger in another app and one Xata action. As soon as you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. Most Xata Zaps on a free account therefore look like this: one event in a form tool, a shop or a CRM, then one Create Record step.
02How many tasks does a Xata Zap use?
One task per Xata action that succeeds. The trigger in the other app never costs anything, and neither does Zapier checking for new data. A Zap with one Xata action uses one task per run; with two Xata actions, two. If an action fails, for instance because Create Record With a Given ID finds the ID already taken, that run is not counted against your plan. Checking for new data in the trigger app is free too, however often it happens.
03Does Xata on Zapier work in real time?
It depends entirely on the trigger in the other app, since Xata offers no trigger on Zapier. If that trigger is instant, its app tells Zapier the moment something happens and the Xata row follows straight away. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on the free plan, 2 on Professional, 1 on Team and Enterprise. The Xata write itself happens as soon as the Zap reaches it.
04What does it take to connect Xata to Zapier?
A Xata account with write access to the tables you want to fill, and a Zapier account. You add the connection from the Apps page, sign in to Xata in the tab that opens and grant access. Then create the target table and its columns in Xata before building the Zap, because every action asks for a Table and lists its columns for mapping. That connection is then reused by every Xata step you add later.
05Why does Xata say the record ID already exists?
Because you used Create Record With a Given ID, which is built to refuse duplicates: if the ID is already in the table, the write is cancelled and an error comes back. That is the expected behaviour, not a bug. If you want the existing row to change instead, switch to Create or Update Record With a Given ID, which only touches mapped columns, or to the replace action, which rewrites the whole record.
06What if the Xata operation you need is not on Zapier?
Then it is not available through this integration. Zapier only offers the four write actions listed here: no trigger, no search and no delete. One way around it is to start the Zap in the app where the change begins, then write to Xata. For anything that must read Xata or react to it, compare the same app on Make or n8n, whose own pages list what they cover. Starting from that list saves a lot of time.
07Zapier, Make or n8n for Xata?
Judge it on three criteria rather than on a ranking. First, coverage: on Zapier, Xata is write-only, so check whether the other platforms offer the reads you need. Second, cost model: Zapier counts one task per successful action, which is easy to forecast. Third, the shape of your Zap: on the free plan Zapier stops at one trigger and one action, so a flow with a filter means a paid plan.
Same platform

Other docs you might need on this stack.

Browse all integrations