Latenode

Table export to Database

This template copies a table of records into Latenode Database on a schedule.

JavaScript loads the source over HTTPS, maps each row, and uses a unique key so later runs update the same objects. Latenode Database then creates or updates those objects. Put the source API key in that JavaScript node.

Updated Sep 16, 2026Est. run: 7sEst. cost: $0.0004
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Copies a source table into Latenode Database on a schedule
  • Normalizes rows in JavaScript before the write
  • Creates or updates by unique key so repeats stay one object
  • Keeps the source API key in the JavaScript node

How it works

1
Trigger

Run on a schedule

The scenario starts on the cadence you set, such as hourly or once a day.

2
Logic

Fetch and normalize rows

JavaScript calls your tabular HTTP or CSV source, maps fields, and keeps a unique key per row. Put the source API key in that JavaScript node.

3
Action

Write Latenode Database

Each normalized row is created or updated in Latenode Database so repeats do not duplicate the same key.

Setup guide

1

Create the Database table

In Latenode Database, create the table your other scenarios will read. Include a unique key and the columns you want to keep in sync.

2

Set the schedule

Add a schedule for how often the export should run.

3

Fetch, map, and upsert

In JavaScript, load the source, map rows, and store the source API key in that node. Then create or update each object in Latenode Database using the unique key.

Requirements

A reachable HTTPS table, API, or CSV URL
The source API key stored in the JavaScript node
A Latenode Database table with a unique key for upserts
A schedule

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.