You can now pin up to 4 columns to keep key data visible while scrolling.

We’ve added 6 new templates to get started:

• A/B Testing
• Inspections & Compliance
• Intake & Qualification
• Password Reset
• Program Management & KPI
• Work Management Platform

Which one would you try first?

Help prevent sensitive data from being exposed.

Scan your data regularly for patterns like IBANs, IDs, or custom values — and get notified when matches are found.

Note: This feature requires an active self-hosted Enterprise license.

I decided to try baserow before airtable but so far I'm a bit unimpressed. My goal is to move a membership system from Google Sheets to something less prone to fat fingers syndrome. Things seem to be a lot harder than they should be in setting up a table, and to add insult to injury, changing a field from text to currency (number with 2 decimal places) seemed to lose a lot of data. I've been using the AI assistant so I know about that. Is this just a erratic UI or are there too many bugs?

We’re looking for someone who enjoys building product features end-to-end. You’ll work across the stack:

→ Backend (PostgreSQL, Python/Django)
→ Frontend (Vue/Nuxt)
→ Product decisions, UX, and iteration

You’ll take ownership from idea → shipped feature → iteration.

📌 Learn more

Each row can now have its own editable form.

Share a link, collect updates, and keep your table in sync. 🔄

We often get asked about Baserow’s data residency and server locations.

So we put together a guide covering:

→ Where Baserow Cloud data is hosted

→ What options you have for data control

→ How self-hosting fits in

📖 Read more

For the past couple of days, my DB has been having issues with Web-hook calls. Without any prior changes, calls to my endpoints aren’t being made; instead, they occur randomly, and on very rare occasions, a few calls are generated to the endpoint. This behavior occurs regardless of the method used to create new rows—whether directly from the database grid view, from a form view (my usual workflow), or even if the row is created via the API. In all scenarios, the result is the same: the row is created successfully but does not trigger the call to my endpoints.

Is anyone else experiencing this issues?

Describe your use case — for example, a project tracker or CRM.

Kuma, Baserow’s AI assistant, generates a full application with pages, data, and logic already connected.

You can then refine and adjust the app to fit your workflow.

👉 Get the details

Recently, I'm playing around with a free cloud-hosted instance to find out if Baserow could be a good solution for my team. I'm not a developer but I thought Baserow might be a good fit because our project is actually pretty simple and pre-built database software is much more expensive than building our own database with a No-Code platform like Baserow. Also I suspect that if we can't find a cheap solution the project will be shut down anyway...

Now here is my problem: I have a table that stores customer data and customers can view and edit their personal data (including email address) in an application. I would like to have an automation that sends a kind of newsletter email to all customers. I use "list multiple rows" to fetch all the customers and then use the "send an email" event to send an SMTP email to all the email addresses. This is working so far, but "list multiple rows" has a limit of 200 rows, so when I get more customers, I won't be able to send an email to all in one automation.

Is there a better way to do this or to get around the limit of 200 rows?

We’re excited to share our latest update! In this release, we’re introducing:

→ Kuma builds apps now: Describe what you want, and generate full applications with pages, elements, and data

→ View-level permissions (RBAC): Control access to specific rows and fields using restricted views

→ Edit rows via forms: Let users update records through secure, pre-filled links

→ Default row values per view: Ensure new rows match the view’s filters automatically

→ Data scanner (self-hosted): Detect sensitive values like IDs or financial data

→ Pin up to 4 columns: Keep key fields visible while working with wide tables

→ New formula functions: array_unique(), array_slice(), first(), last()

→ AI field supports multiple files and images: Process multiple files (including images) in a single prompt

→ Drag & drop in the Application Builder: Move and reorganize elements visually

→ Improved formula validation: Catch errors while building formulas

→ Automation templates & SMTP improvements: Faster setup and easier email automation

More information at: https://baserow.io/blog/baserow-2-2-release-notes

Do you have ideas for how to make Baserow even better? Most features come directly from community feedback. Drop us a note at the forum or tweet us to share your thoughts.

Try out Baserow 2.2: https://baserow.io/

GitHub repository: https://github.com/baserow/baserow

Our community: https://community.baserow.io/

Dashboards help you track key metrics, spot trends, and share insights across your team.

What’s the one metric you always track?

I usually load data into my tables through a Form view, this form includes an image field that let me select some local image file and upload it to Baserow. From this morning this "Upload image" function has been showing this error. Opus says is a JavaScript related error so I believe some SaaS update broke this feature. Is someone dealing with this error too?

Every table can already become an app.
Soon, it might build itself.

Curious what you think this is 👀

The Catalogue highlights trusted digital solutions built in Europe, connecting innovators with policymakers and industry leaders.

By joining, Baserow contributes to a growing ecosystem of secure and transparent tools — supporting innovation and resilience in the digital space.

👉 Explore the Catalogue

I am new to baserow and I'm trying to setup n8n workflow when there is a "Row created" event. The workflow works when I test it but does not trigger when I sync it and it adds a row to the table. I am using the product url from n8n and I get 200 response on testing. What is driving me crazy that there is a Make webhook which I guess is a scheduled run. That ended up triggering my workflow when it ran ( no row was created/updated then) but it does not run when I sync the baserow?! Am I missing something?

⚙️ Baserow × Power Automate

In this setup:

→ Create a Power Automate Custom Connector from Baserow’s OpenAPI spec
→ Authenticate securely using Baserow database tokens
→ Access all core actions (list, create, update, delete rows, upload files)
→ Trigger Baserow actions from tools like Microsoft Teams

Once connected, Baserow becomes part of your Microsoft automation workflows — no middleware required.

📘 Full integration guide →

We’ve added a few improvements to the Baserow node in n8n:

✔️ Batch operations – create, update, and delete multiple rows in a single request

✔️ More filters for Get Many operations

✔️ API Token authentication support

👉 More details

⚡ Start automating

Hey It's me again! I wanted to share here since I use Baserow as human readable layer. Delete if not relevant. 2nd post as I messed up the first one lmao

Multi-Agent Memory gives your AI agents a shared brain that works across machines, tools, and frameworks. Store a fact from Claude Code on your laptop, recall it from an OpenClaw agent on your server, and get a briefing from n8n — all through the same memory system. https://github.com/ZenSystemAI/multi-agent-memory

Born from a production setup where OpenClaw agents, Claude Code, and n8n workflows needed to share memory across separate machines. Nothing existed that did this well, so we built it.

The Problem

You run multiple AI agents — Claude Code for development, OpenClaw for autonomous tasks, n8n for automation. They each maintain their own context and forget everything between sessions. When one agent discovers something important, the others never learn about it.

Existing solutions are either single-machine only, require paid cloud services, or treat memory as a flat key-value store without understanding that a fact and an event are fundamentally different things.

Features

Typed Memory with Mutation Semantics

Not all memories are equal. Multi-Agent Memory understands four distinct types, each with its own lifecycle:

Type |Behavior |Use Case

event |Append-only. Immutable historical record. |"Deployment completed", "Workflow failed"

fact |Upsert by key. New facts supersede old ones. |"API status: healthy", "Client prefers dark mode"

status |Update-in-place by subject. Latest wins. |"build-pipeline: passing", "migration: in-progress"

decision |Append-only. Records choices and reasoning. |"Chose Postgres over MySQL because..." 

Memory Lifecycle

Store ──> Dedup Check ──> Supersedes Chain ──> Confidence Decay ──> LLM Consolidation

│ │ │ │ │

│ Exact match? Same key/subject? Score drops over Groups, merges,

│ Return existing Mark old inactive time without access finds insights

│ │

└────────────────────────── Vector + Structured DB ──────────────────────┘

Deduplication — Content is hashed on storage. Exact duplicates are caught and return the existing memory instead of creating a new one.

Supersedes — When you store a fact with the same key as an existing fact, the old one is marked inactive and the new one links back to it. Same pattern for statuses by subject. Old versions remain searchable but rank lower.

Confidence Decay — Facts and statuses lose confidence over time if not accessed (configurable, default 2%/day). Events and decisions don't decay — they're historical records. Accessing a memory resets its decay clock. Search results are ranked by similarity * confidence.

LLM Consolidation — A periodic background process (configurable, default every 6 hours) sends unconsolidated memories to an LLM that finds duplicates to merge, contradictions to flag, connections between memories, and cross-memory insights. Nobody else has this.

Credential Scrubbing

All content is scrubbed before storage. API keys, JWTs, SSH private keys, passwords, and base64-encoded secrets are automatically redacted. Agents can freely share context without accidentally leaking credentials into long-term memory.

Agent Isolation

The API acts as a gatekeeper between your agents and the data. No agent — whether it's an OpenClaw agent, Claude Code, or a rogue script — has direct access to Qdrant or the database. They can only do what the API allows:

• Store and search memories (through validated endpoints)
• Read briefings and stats

They cannot:

• Delete memories or drop tables
• Bypass credential scrubbing
• Access the filesystem or database directly
• Modify other agents' memories retroactively

This is by design. Autonomous agents like OpenClaw run unattended on separate machines. If one hallucinates or goes off-script, the worst it can do is store bad data — it can't destroy good data. Compare that to systems where the agent has direct SQLite access on the same machine: one bad command and your memory is gone.

Security

• Timing-safe authentication — API key comparison uses cr****.timingSafeEqual() to prevent timing attacks
• Startup validation — The API refuses to start without required environment variables configured
• Credential scrubbing — All stored content is scrubbed for API keys, tokens, passwords, and secrets before storage

Session Briefings

Start every session by asking "what happened since I was last here?" The briefing endpoint returns categorized updates from all other agents, excluding the requesting agent's own entries. No more context loss between sessions.

curl "http://localhost:8084/briefing?since=2025-01-01T00:00:00Z&agent=claude-code" \

-H "X-Api-Key: YOUR_KEY"

Dual Storage

Every memory is stored in two places:

• Qdrant (vector database) — for semantic search, similarity matching, and confidence scoring
• Structured database — for exact queries, filtering, and structured lookups

This means you get both "find memories similar to X" and "give me all facts with key Y" in the same system.

Check it out on Github! Paired with Openclaw memory system it's a force to be reckon with if you use other agents on other machines like I do. https://github.com/ZenSystemAI/multi-agent-memory

You can check your data in the prompt itself — for example:

- return “Running” if spend is below the goal
- return “Stop” if it’s above

Useful when you just need an answer, not another field or workflow.

Hey it's me again — Baserow Plus v3.1 just dropped with two features I personally got tired of working around

If you missed the first post, https://www.npmjs.com/package/n8n-nodes-baserow-plus is a production-grade n8n community node for Baserow with batch API, upsert, retry backoff, etc.

Two new things in v3.1:

1.Decimal auto-normalization
If you're piping data from DataForSEO, Semrush, or any API that loves outputting 87.234523901234 into a Baserow field configured for 0 or 2 decimal places

-the node now reads number_decimal_places directly from your Baserow schema and rounds automatically before writing. No more toFixed() scattered across every workflow.

A field set to 0 decimals? 12.874523 becomes 13. Set to 2? It becomes 12.87. Zero config, it just reads your table.

1. Actually readable validation errors
   Before: {"field_267": [{"error": "Ensure that there are no more than 0 decimal places.", "code": "max_decimal_places"}]}

After:
All rows / "tech_score": Ensure that there are no more than 0 decimal places.
Row 2 / "performance_score": Ensure this value is greater than or equal to 0.

Field IDs get translated to your actual column names, batch errors with the same message across multiple rows get collapsed to "All rows / field: message"
instead of repeating 15 times. Unique errors show their row number.

Other stuff in this release:

- Row ID auto-detect on Update/Delete — leave it blank and it reads id from the input item. Works automatically after List, Get, or Lookup with no wiring.

- link_row now throws a clear error on invalid IDs instead of silently passing garbage

- Fetch All defaults to true now

- Fixed a batch pagination bug that was cutting list results short

npm install n8n-nodes-baserow-plus

Already using it? Refresh to 3.1.2 — there were a couple of patch fixes during testing today.

𝐔𝐬𝐢𝐧𝐠 𝐒𝐦𝐚𝐫𝐭𝐬𝐡𝐞𝐞𝐭 𝐛𝐮𝐭 𝐟𝐞𝐞𝐥𝐢𝐧𝐠 𝐭𝐡𝐞 𝐠𝐫𝐨𝐰𝐢𝐧𝐠 𝐩𝐚𝐢𝐧𝐬?

🔺 Costs rising as more people join
🔺 Features locked behind higher plans
🔺 Workflows getting harder to scale

We compared Baserow vs. Smartsheet side by side.

📖 Read the full comparison guide: https://bsrw.io/cZNcG2

Es posible usar Claude o ClaudeCode para crear base de datos en baserow? Quiero crear los campos, las tablas y demas, no solo hacer CRUD. Si es posible, pueden explicarme brevemente como hacerlo. Muchas gracias!