Latenode

Store incoming webhook data in Latenode Database

This template stores inbound webhook JSON in Latenode Database so later scenarios can read it. Point any system that can POST JSON at the webhook.

JavaScript keeps a unique key plus the fields you care about, then Latenode Database creates the object. Use that unique key to update the same row when the source sends the record again.

Updated Sep 16, 2026Est. run: 8sEst. cost: $0.0005
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

  • Persists inbound webhook JSON in Latenode Database
  • Shapes fields in JavaScript before the write
  • Creates or updates by unique key so repeats stay one object
  • Lets later scenarios read the stored row

How it works

1
Trigger

Receive the webhook

A webhook starts the scenario when an external system posts JSON.

2
Logic

Shape the fields

JavaScript maps the payload into a unique key and the columns your Database table expects.

3
Action

Create the Database object

Latenode Database stores those fields so other scenarios can get the object later.

Setup guide

1

Create the Database table

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

2

Add a webhook trigger

Add a webhook trigger and copy its URL. Point the source system at that URL.

3

Map fields and write

In JavaScript, return a unique key and stable field names. Create the Latenode Database object. If the same key can arrive twice, look it up and update it instead of inserting a second row. POST a test payload and confirm the object.

Requirements

A source that can POST JSON to a Latenode webhook
A Latenode Database table with a unique key
The field names you want JavaScript to keep from the payload

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.