Baserow

n8n has a native Baserow node that can read, create, update, and delete rows in Baserow tables. Small businesses using Baserow as a free, self-hosted database use n8n to automate workflows around it — for example, logging support ticket data from email into Baserow, or syncing Baserow rows to another tool when a field changes.

There is no native or Zapier connector between Clockify and Baserow — you connect them via n8n, which requires setting up an n8n instance (cloud or self-hosted). The most common workflow uses the Clockify Trigger node, which fires when a time entry is created or stopped, then passes that data into Baserow using the Baserow node to insert or update a row. Data that flows includes workspace, project, task name, duration in seconds, billable status, the team member who tracked, and start/stop timestamps. You can also run the flow in reverse: a new row added to a Baserow table (for example, a new client or project) triggers n8n to create the matching project in Clockify so tracking is ready to go. This is valuable for SMBs using Baserow as a custom project tracker or lightweight CRM who want time data and client data in one searchable table. Data flows: Bidirectional via n8n workflows. Clockify time entries → Baserow rows (project, task, duration, billable status, timestamps). Baserow new rows → Clockify project or task creation. No built-in two-way sync; each direction is a separate n8n workflow. Pain points: The Clockify Trigger node uses your n8n workflow's timezone setting to determine which time entries to retrieve — if that timezone is wrong, entries can be missed or duplicated. n8n is not a point-and-click tool like Zapier; setting up nodes and testing flows has a steeper learning curve. Self-hosting n8n adds infrastructure overhead; n8n Cloud removes that but adds a monthly cost.