Docs menu · Developers

Push rows from n8n

The ChartOmodo community node turns the items in an n8n workflow into dataset rows, and reads your charts back.

Pro plan · Updated 25 October 2026

Before you start

  • Writing rows starts on the Pro plan. Reading charts and their data starts on the Starter plan.
  • You need a self-hosted n8n. n8n Cloud lists the node once n8n has verified it; until then, use the HTTP Request node there.

Install the node

  1. In n8n, open Settings → Community Nodes.
  2. Install n8n-nodes-chartomodo. Its page on npm is https://www.npmjs.com/package/n8n-nodes-chartomodo.
  3. Add a ChartOmodo node to a workflow. It asks for a ChartOmodo API credential: paste the token you create in the next step.

Create a token

  1. In ChartOmodo, open API in the sidebar.
  2. Type a Token name that says where it runs, such as n8n production.
  3. Pick the Full preset: Every scope, no expiry. For your own scripts and n8n.
  4. Press Create token and copy the token. It is shown once.

Give each n8n instance its own token, so you can Revoke one without stopping the others.

Push rows

Every item that reaches the node becomes one row. The node offers:

  • Dataset, Create: a new dataset from the input items.
  • Dataset, Append Rows: adds the items after the rows already stored. A column that is new gets an empty value in the older rows.
  • Dataset, Replace Rows: swaps every row for the items in one step. Embeds show the old rows or the new ones, never half.
  • Dataset, Get Many: lists your datasets, newest first.
  • Chart, Get, Get Data and Get Many: a chart, the categories and series it draws, or your chart list.

To chart the rows, open the dataset from Home in ChartOmodo and build a chart on it.

Retry safely

The node sends an Idempotency-Key with every append and replace, one per run. Once a write with a key has succeeded, the same key on the same dataset writes nothing for 24 hours. A write that fails frees its key, so the retry goes through.

  • On 429 and on a busy dataset, the node waits for the time the answer gives, 30 seconds at most, and retries up to three times. Then the run fails.
  • Retry On Fail runs the same run again, so it cannot add rows twice.
  • Running the workflow again from the execution history is a new run: it appends the rows again.
  • Create sends no key. Retrying it can make a second dataset.
Note Using the HTTP Request node instead? Send an Authorization header set to Bearer and your token, and an Idempotency-Key header that is new for each run and each item, such as {{ $execution.id }}-{{ $runIndex }}-{{ $itemIndex }}. The HTTP Request node sends one request per item, so the item index keeps each item’s rows from being taken for a repeat. If two HTTP Request nodes write to the same dataset in one execution, give each key a different prefix, such as the node name, or the second node’s rows are dropped as duplicates. Turn on Retry On Fail with a 5 second wait: it covers 503 busy and 503 idempotency_in_progress, and keeps the same key. The API reference has the details.

If it does not work

401 invalid_token

The token is missing, malformed, unknown or revoked. Create a new token and paste it into the node’s credential.

403 scope_required

The token does not have the scope this endpoint needs. The message names the scope. Create a token with the Full preset.

403 plan_required

Your plan does not include this. Reading needs the Starter plan or higher, writing the Pro plan or higher.

429 rate_limited

Each token gets 60 requests per minute. The node waits for the time the answer gives, 30 seconds at most, and retries up to three times before the run fails. Send more rows per run, fewer runs.

Questions

Can I use the node on n8n Cloud?

Not yet. n8n Cloud lists it once n8n has verified it. Until then, install it in a self-hosted n8n, or call the API from the HTTP Request node.

Which plan do I need?

Pushing rows starts on the Pro plan. Reading charts and their data starts on the Starter plan.

Can a retry add the same rows twice?

Not when the node retries itself or Retry On Fail runs it again: each run sends one Idempotency-Key, and a key ChartOmodo already applied writes nothing. Running the workflow again from history is a new run and appends again.

How do I cut n8n off?

Open API in the sidebar and revoke its token. Every request with that token answers 401 from then on.

Start free, then add a token

Pushing rows starts on the Pro plan.

Start free

May we use Google Analytics cookies to count visits to our public pages, and remember which link brought you here in case you sign up? Nothing inside the app or your embeds is ever tracked. Privacy Policy