Keep a database updated without creating duplicate records

Automatically updates an existing record or creates a new one, so your database never ends up with duplicates.

How the work actually flows

It branches. Exactly one path is taken.

Pattern: Exclusive Choice (4) · Simple Merge (5)

flowchart TD trig>"new or updated info arrives"]:::trig s0["receive new information"]:::task s1["search for matching record"]:::svc s2[("update or create record")]:::store s3["confirm result"]:::task trig --> s0 s0 --> s1 s2 --> s3 gx{"× does record already exist"}:::gate s1 --> gx p00["update existing record"]:::task gx -->|"match found"| p00 p10["create new record"]:::task gx -->|"no match found"| p10 jn{"○ record saved"}:::gate p00 --> jn p10 --> jn jn --> s2 out[/"record updated or created"/]:::out pay{{"no duplicate records"}}:::pay s3 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itA stepAn outside serviceA record or sheetOne path onlyPaths rejoinResultPayoff
Build size
Advanced

A larger build with multiple systems, AI reasoning, and custom rules.

Business functions
API & Webhook Integration
Connects
Baserow
Featured in

The problem it solves

Every time new information comes in, someone has to check whether the record already exists before adding it, or you end up with duplicate entries cluttering your database. Sorting out duplicates later wastes time and makes your data unreliable.

Who it fits

A business that keeps a shared database of contacts, supporters, or records that get updated over time, like a volunteer list or customer record.

How it works

  1. New or updated information arrives through a form, website, or another system
  2. The automation searches the database for a matching record
  3. If a match is found, that record is updated
  4. If no match is found, a new record is created
  5. The result is confirmed back automatically
What you get

Records that stay clean without duplicates

Your database record gets updated or created automatically, so the same contact never appears twice.

What you get

An always-current database record with no duplicate entries.

What you need

A Baserow account with API access.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook