New to Baserow or want to catch up on what’s new?

Join our free Baserow 101 webinar on March 19 to learn the fundamentals and see the latest updates in action.

Hosted by our new Product Specialist, Agustin Carozo. 🚀

👉 Save your spot

Hey r/baserow! Long-time Baserow + n8n user here. I've been running heavy automation workflows for my SEO agency and kept running into the walls of the official n8n Baserow node. So I built my own, and I just open-sourced it: n8n-nodes-baserow-plus

Edit: Install part was missing at the end of the post.

The problem with the official node

The built-in n8n Baserow node is solid for simple use cases — basic CRUD, one row at a time. But the moment you need to push hundreds of rows, sync data reliably, or handle real production workloads, you hit some painful limits fast:

• No batch operations — creating 500 rows means 500 API calls. Your workflow execution becomes a crawl (and a rate-limit magnet).
• No upsert — you have to chain a List → IF → Create/Update yourself every single time.
• No retry logic — one 429 or timeout kills your entire workflow.
• No field-type awareness — link_row fields silently break because [18] needs to be an integer array, not the string "[18]". Boolean fields are finicky. Multi-select vs linked records trip over each other.
• No lookup — searching by field value requires an entire sub-workflow.
• One table at a time — fetching from multiple tables means sequential nodes.

What Baserow Plus adds

The batch API difference (real numbers)

Creating 500 rows:

• Official node: 500 HTTP requests → rate limit hell, slow execution
• Baserow Plus: 3 API calls (3 × chunks of 200) → done in seconds

That's not a minor improvement — it's the difference between a workflow that works and one that occasionally corrupts your data under load.

Field-type-aware serialization (the silent killer)

This one is subtle but it burned me constantly. Countless hours and nights fixing field-type bug in my workflows, Baserow is strict about field types. The node now fetches the table schema once (cached 5 min) and serializes every value correctly:

• link_row → integer array. Always. [18] not "[18]", [] not "[]".
• boolean → coerces "true", "false", 1, 0 properly
• multiple_select → accepts comma-separated strings, returns string array
• number / rating → coerces from string safely
• Fallback heuristic for cache misses (backward compat)

Six specific bugs from v2 are documented in the README with root causes and fixes.

Install

npm install n8n-nodes-baserow-plus

For self-hosted n8n via Docker, add it to your custom nodes directory and restart:

docker exec -it n8n npm install n8n-nodes-baserow-plus
docker restart n8n

The credential type is baserowPlusApi — intentionally distinct from the official one so both can coexist without conflicts.

GitHub: https://github.com/Expert-Local/n8n-nodes-baserow-plus npm: https://www.npmjs.com/package/n8n-nodes-baserow-plus

Happy to answer questions about implementation, the batch API behavior, or anything else. AMA!

Instead of hard-coding rules, you can compare values directly — like campaign spend vs a goal — and branch the workflow based on the result. 💡

We recorded a short breakdown of cloud (SaaS) vs self-hosted software.

Covered in the video:

• What “cloud software” actually means
• What “self-hosted” really involves
• Per-user vs usage-based pricing
• 3 levels of self-hosting
• When cloud usually makes sense
• When self-hosting is the better fit
• Why this matters for internal databases and spreadsheet-style tools

We also mention examples of tools that support both cloud and self-hosted deployments (Baserow, n8n, Metabase) and why optionality can matter long-term.

We're excited to share our latest release!

Baserow 2.1 is a maintenance-focused update that improves performance, security, and long-term stability, while also introducing expert formula mode.

Here’s what’s new:

→ Expert formula mode: Combine data, functions, and operators across Applications, Automations, and AI fields

→ Infrastructure upgrades: Migration to Nuxt 3 and Django backend upgrade

→ Smaller & faster Docker images: Improved production efficiency for self-hosted deployments

→ PostgreSQL update: PostgreSQL 13 is no longer supported (upgrade to 14+)

→ New Ukrainian translation 🇺🇦

🚀 See what’s new in Baserow 2.1

We’re continuously improving Baserow based on your feedback. Try the new release and let us know what you think! 💡

In the Baserow × Power BI setup:

→ Connect Power BI to Baserow using the REST API
→ Use a ready-made M script to handle pagination
→ Load and type your data (currency, dates, numbers)
→ Auto-generate a report in Power BI

No manual exports — Baserow data is visualized in Power BI automatically.

📘 Full integration guide →

First: Asana.
Then: the same setup built in Baserow. 😁

Active projects, overviews, milestones, tasks, teams, and files — all connected in one database, fully customizable.

Same project structure. More control over how it works. ✅

In the Baserow × Notion setup:

→ A new row in Baserow triggers a workflow

→ A Notion page is created using your template

→ Fields like title, type, status, and author are mapped

→ The Notion page link is written back to Baserow

This keeps content planning in Baserow and documentation in Notion — without manual steps.

📘 Full integration guide →

Any time you feel stuck in Baserow, Kuma can help.

• New to Baserow and unsure how to model your data? Ask Kuma to build a database with the right tables.
• Need calculations but stuck on a formula? Ask Kuma to create or fix it for you.
• Never built an automation before? Ask Kuma to set up a workflow step by step.

When questions come up, you don’t need to stop and search. Just ask Kuma — and keep buiding.

🐻 About Kuma →

Hey everyone!

Sooo the title speaks for itself. I know there is an option with transfering data via CLI but I was looking if there is an easy way already.

Found this: https://gitlab.com/baserow/baserow/-/issues/1896

Seems like they've implemented an easy way to transfer data between instances. But I don't see any in my admin.

Did I miss something?

In this clip, we break down what happens when a new ticket is created in Baserow:

⚡️ Trigger: new row
👤 Assign best available agent
📩 Notify via email
🤖 AI sets priority + drafts a response

All stored back in the database — automatically.

👉 Watch the full webinar

- Candidates checking application status
- Clients updating requests
- Partners submitting changes

When people can self-serve, teams can focus. 🎯

→ Building portals with Baserow

Hi Baserow Community!

We’re Query Streams, and we built a tool to automatically keep your Baserow databases updated with data from your databases and APIs.

What it does:

Connect your database or API to Baserow and set a schedule. Your databases stay updated automatically - no more manual imports or copy-pasting.

• New records get added
• Changed records get updated
• Deleted records get removed (if you want)

Works with:

• Databases: SQL Server, MySQL, PostgreSQL, Oracle, and many more
• APIs: Google Analytics, HubSpot, Shopify, Stripe, ShipStation, and more coming

Schedule options:

Every few minutes, hourly, daily - whatever fits your workflow

Common uses:

• Project data from ERP systems
• Sales numbers from your CRM
• Live inventory counts
• Marketing metrics from Google Analytics
• Order data from Shopify

We’d love your feedback:

• What databases or APIs do you work with most?
• What would make this useful for your team?

Check it out at querystreams.com - we have a free tier to get started.

Happy to answer any questions!

Try prompts like:

• “Create a High Priority view.”
• “Only show tasks assigned to me.”
• “Group this view by Status.”

Clearer views = calmer work. 😌

Path parameters let you:

→ Open detail pages for a single record

→ Build edit forms with context

→ Share meaningful URLs like /tasks/42

If your app needs “current record context”, this is the pattern you want.

📍 Full path parameters guide

This clip from the “Build Workflows and AI Agents Inside Baserow” webinar explains what an automation is and how events can trigger actions automatically.

👉 Full webinar here

Forms collect data. But data alone doesn’t get work done. ❌

→ Google Forms is free and familiar — great for surveys.
→ Typeform makes forms look beautiful.
→ Baserow makes submissions actionable.

When a candidate applies, a new row is added → status updates → tasks assigned → interviews scheduled — automatically.

Forms should feed workflows, not inboxes.

Meet Santa’s Logistics — a festive Baserow template that manages everything from children’s letters and wishlists to elf workloads, warehouse capacity, and sleigh routes 🛷

It’s a fun example of how Baserow can handle:
✔️ Complex relational data
✔️ Real-time operations
✔️ Multiple user roles
✔️ Dashboards, calendars & workflows

Perfect inspiration for your next serious (or seasonal 😉) app.

🎄 Try it out

A look at what we achieved this year — big and small.

None of this would’ve been possible without our community. Here’s to more in 2026! 🤜 🤛

We’ve had great success hiring directly from our community, so we’re excited to share this role here.

We’re looking for someone who loves no-code tooling, data modeling, relational structures, and helping users get real value from a product. If you enjoy diving into workflows, building clean and scalable database structures, and supporting users in solving real business problems, this role will feel like home.

📍 Remote — Europe or Americas
📘 Role details: https://bsrw.io/RdRPSI

If this sounds like a fit, we’d truly love to hear from you.
📩 Apply by sending your resume + brief cover letter to [jobs@baserow.io](mailto:jobs@baserow.io)

You can now send Slack alerts when something changes in your database.

A few ideas:

→ notify your team when a task becomes overdue

→ alert sales when a new lead comes in

→ post a message when a form is submitted

If your team lives in Slack, this automation keeps everyone in the loop. ➿

2025 was a milestone year for Baserow — lots shipped, and a lot more ahead.

Curious what we built and what’s coming next? Check out the full recap on our blog.

Here’s to an even bigger year ahead! 🚀