Destinations

Push your API data
directly to Postgres

No ETL pipelines. No data warehouse. Run a workflow in API Import and rows land in your configured database.

NeonSupabaseXataNileAny Postgres

How it works

Three steps to your first row

Choose Postgres as your destination, select a saved connection, choose a table, and run.

Choose Postgres as your destination

In the workflow editor, switch the destination from Google Sheets™ to Postgres. Works on new and saved workflows once a Postgres connection is available.

Destination

Postgres

Selected

Select your saved connection

Choose a saved Postgres connection, schema, table, and write mode. API Import can append rows or create/update the table structure before inserting rows.

Saved connection

jdbc:postgresql://host:5432/db

Run — rows appear in your table

API Import fetches from the API, maps the fields, and bulk-inserts into Postgres. Schedule it to keep the table fresh.

Result

amount

status

ch_8a..

$129

paid

ch_3f..

$84

paid

ch_2c..

$210

refund

Table modes

Control exactly how data lands

Each workflow lets you choose how API Import writes to your Postgres table. Pick the mode that fits your current table setup.

Append only

Add rows to a table you already manage.

The table and matching columns must exist before running. API Import inserts new rows and leaves everything else — existing rows, schema, columns — untouched.

Inserts new rows
Requires table and columns to already exist
Never creates or modifies the schema
Never deletes existing rows

Create / update table

Let API Import handle the setup.

API Import creates the schema, table, and any missing columns automatically. Columns are added as TEXT when new output fields appear. Existing rows are kept.

Creates schema and table if missing
Adds missing output columns as TEXT
Inserts new rows
Never deletes existing rows

Example setup

Don't have a Postgres database yet?

If you're starting from scratch, one option worth trying is Neon — a serverless Postgres provider with a free tier. We're not affiliated with them; it's just a convenient way to get a database ready quickly.

Neon offers a free tier — no credit card required. This is just one option; any Postgres provider works the same way.

Create a project and a table

Click "New Project" and Neon spins up a database in a few seconds. Open the SQL editor — it pre-loads a query that creates a sample table called playing_with_neon. Run it to have something to write to.

Prepare the JDBC connection details

Go to "Connection details" in the project dashboard and copy the database host, database name, username, and password. API Import stores saved Postgres connections as JDBC URLs that start with jdbc:postgresql://.

Choose the saved connection in API Import

In your workflow, choose Postgres as the destination, select the saved connection, and set the target table — for example playing_with_neon. Run the workflow and rows start appearing in your database.

What an API Import Postgres JDBC URL looks like

jdbc:postgresql://ep-mute-wave-123456.us-east-2.aws.neon.tech/neondb

Visit neon.tech

Works everywhere

Already have a Postgres database?

API Import works with standard Postgres databases reachable from Apps Script JDBC. Save a JDBC URL, username, and password, then select that connection in your workflow.

Supabase

Copy from Project Settings → Database

Xata

PostgreSQL connection string in settings

Nile

Tenant-aware Postgres, full compatibility

AWS RDS

Standard RDS endpoint, any region

Self-hosted

Local or private Postgres instance

Any provider

If it speaks Postgres, it works

Push your API datadirectly to Postgres