Connect Neon to Codeless Sync
Step-by-step guide to syncing your API data to Neon PostgreSQL with Codeless Sync — no code required.
Connect Neon to Codeless Sync
Codeless Sync (CLS) lets you sync API data directly into your PostgreSQL database — no code, no webhooks, no custom pipelines. Pair it with Neon's serverless Postgres and you get a fully managed, auto-scaling database that stays in sync with your business tools automatically.
This guide walks through syncing Stripe data to Neon as an example. CLS also supports QuickBooks, Xero, and Paddle — the setup steps are nearly identical for each provider.
Video Tutorial
Sync Stripe Data to Neon PostgreSQL — No Code, 5 Minute Setup
Prerequisites
- A Neon account with a project created
- A Stripe account (or another supported provider)
- A Codeless Sync account
Step 1: Get Your Neon Connection String
- Log in to the Neon Console
- Select your project (or create a new one)
- Click the Connect button in your project dashboard
- Copy the connection string — it starts with
postgresql://orpostgres://
Enable connection pooling in Neon for better performance with CLS. You can find pooling options in your project's Connection Details panel.
Step 2: Select Provider and Data Type
- Log in to your CLS dashboard
- Click Create Sync Configuration to open the setup wizard
- Select Stripe as your provider
- Choose a data type to sync (e.g., Customers)
CLS also supports QuickBooks, Xero, and Paddle. You can create additional sync configurations for any supported provider after completing this guide.
Step 3: Connect Your Neon Database
- In the wizard, click New Project
- Enter a project name (e.g., "Neon Production")
- Select Neon as the database platform
- Paste your Neon connection string from Step 1
- Click Test Connection to verify
Your connection string contains your database password. Never share it publicly or commit it to version control.
Step 4: Enter Your Stripe API Key
- Paste your Stripe restricted key (
rk_test_orrk_live_) - Click Test Connection to verify access
We recommend using a restricted key for security. See the Stripe Setup Guide for step-by-step instructions on creating one.
Step 5: Create Your Database Table
CLS can auto-create the required table in your Neon database with one click.
- Click Auto-Create Table
- Wait for confirmation that the table was created
- Click Verify Table to confirm the schema
If auto-create doesn't work, you can use the manual fallback:
- Click Copy SQL Template to copy the CREATE TABLE statement
- Open the Neon SQL Editor in your project
- Paste and execute the SQL
- Return to CLS and click Verify Table
Step 6: Review and Create
- Give your configuration a name (e.g., "Neon Stripe Customers")
- Review all settings — provider, database, table, and data type
- Click Create Configuration
Run Your First Sync
- Go to your CLS dashboard
- Find your new configuration and click Sync Now
- Watch the progress bar as CLS fetches and writes your data
- Once complete, open the Neon Console and navigate to Tables to verify your data
Set Up Automated Syncs
Keep your Neon database in sync automatically with scheduled syncs.
- Navigate to Schedules in your CLS dashboard
- Click Create Schedule
- Select your configuration, choose a frequency, and pick a sync mode
- Save the schedule
Scheduled syncs require a paid plan. Free users can trigger syncs manually at any time from the dashboard.
Neon Tips
Scale-to-Zero
Neon can automatically suspend idle compute endpoints. CLS handles this seamlessly — your database will auto-resume when a sync starts.
Branching
Use Neon's database branching to test schema changes safely. Create a branch, point a test CLS configuration at it, and verify everything works before applying changes to your production branch.
Connection Pooling
Enable Neon's built-in connection pooling for better performance with CLS. Pooled connections reduce overhead and handle concurrent syncs more efficiently.
Next Steps
- Configurations — Learn about sync configuration options
- Schedules — Set up automated sync schedules
- SQL Templates — View all available table schemas
- Troubleshooting — Common issues and solutions