n8n-nodes-datagol

This is an n8n community node. It lets you use DataGOL in your n8n workflows.

DataGOL is a data platform where teams organize records in workbooks made up of rows and typed columns. This node lets a workflow add rows, update rows, and query rows in a workbook, and lets a workflow start automatically whenever a row is added or updated — so you can sync data between two workbooks, or between DataGOL and any other n8n-connected system, in either direction.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history

Installation

Follow the installation guide in the n8n community nodes documentation.

Search for DataGOL in the community nodes installer, or install directly by package name:

n8n-nodes-datagol

Operations

DataGOL (action node)

Resource: Row

Both Add and Update also expose an Additional Cell Values (JSON) field for columns the schema mapper does not expose (for example, Link columns) — any keys there are merged on top of the mapped values.

DataGOL Trigger (trigger node)

A polling trigger that starts a workflow when rows change in a workbook:

The trigger needs a Date Column to key change-detection off of. Any column in the workbook can be picked, but a DATE-typed audit column (DataGOL's own created_at/updated_at) works best and is recommended and listed first. It uses that column, plus the workbook's primary key, to detect and de-duplicate changes across polls without emitting the same row twice.

Other trigger options:

• First Poll Behavior — on activation, either emit nothing (only react to changes from that point on) or backfill the last N existing rows.
• Additional Filter — an extra raw WHERE-clause fragment, ANDed with the internal change-detection filter, to scope the trigger to a subset of rows.
• Page Size — pagination size used while the trigger walks through changed rows on a given poll.

Credentials

This node uses the DataGOL API credential type.

Prerequisites:

1. A DataGOL account with access to the workspace/workbook you want to automate.
2. An API token for that account. Contact your DataGOL workspace admin, or generate one from your DataGOL account settings, if you don't already have one.

To set up the credential in n8n:

1. Base URL — your DataGOL API base URL (defaults to https://be.datagol.ai; only change this for a self-hosted/on-prem DataGOL deployment).
2. API Token — your DataGOL API token. It is sent as the x-auth-token header on every request and is never logged.

Use the credential's Test button to confirm it can list your workspaces before using it in a workflow.

Compatibility

• Minimum n8n version: 1.82.0 (requires the resource locator, resource mapper, and list-search UI features used by this node).
• Tested against n8n 1.9x self-hosted and n8n Cloud.
• Both nodes declare usableAsTool: true, so they can also be invoked by AI Agent nodes.

No known version incompatibilities at this time.

Usage

Add a row

1. Add a DataGOL node, set Resource to Row and Operation to Add.
2. Pick the Workspace and Workbook from the list (or paste an ID).
3. Use Cell Values to map incoming data to the workbook's columns.

Update a row

Same as Add, but set Operation to Update and provide the Row ID of the row to change (for example ={{ $json.id }} when the ID comes from a previous node).

React to changes with the trigger

Add a DataGOL Trigger node, choose Row Added or Row Updated, pick the workbook, and select a Date Column (an audit column such as created_at/updated_at is recommended, but any column works).

Avoiding self-triggering loops

A common pattern is: "When a row changes in Workbook A, update a related row in Workbook A or Workbook B." If the workflow writes back to the same workbook that a Row Updated trigger is watching, that write bumps the row's own updated_at column — which the trigger will see on its next poll, potentially re-running the workflow.

Guard against this by adding a Filter node between the trigger and the update action that only lets the item through when the target column is not already set to the value you're about to write. That way the loop naturally stops after one extra, harmless poll instead of repeating indefinitely. See examples/sync-with-loop-guard.workflow.json for a complete example: two triggers (Row Added / Row Updated) feed into an IF node that checks a source column, then a Filter node that only writes when the destination column is out of sync, then an Update Row action.

This loop-guard is also needed across workflows, not just within one: if Workflow A's action writes to a table that Workflow B's trigger watches (and vice versa), the two can keep re-triggering each other indefinitely even though each workflow looks correct in isolation. Apply the same "skip if already set" guard on every workflow that writes to a table another workflow polls.

Get Many → Update races within one poll batch

If a trigger delivers more than one item in a single poll (for example, several rows added at once), and your workflow does a Get Many lookup followed by an Update on the result, each item runs that lookup independently and before any of the batch's updates have been written back. Two items that both resolve to the same target row will both find it in its pre-update state and both write to it — redundantly, but not incorrectly, if the write is idempotent (e.g. "set status to done"). If your update is not idempotent (e.g. incrementing a counter), add a Split In Batches node (or otherwise serialize the items) before the Get Many step so each item's lookup sees the previous item's write.

Resources

• n8n community nodes documentation
• DataGOL

Version history

0.1.0

• Initial release: DataGOL action node (Row: Add, Update, Get Many) and DataGOL Trigger node (Row Added, Row Updated).