Neon + Liveblocks

Neon provides serverless Postgres with branching and autoscaling. Using webhooks, you can set up one-way synchronization of your Liveblocks data to Neon for reporting, search, audit logs, or app workflows.

How data sync works

Liveblocks webhooks trigger when certain events happen, such as when a collaborative document updates. Liveblocks can trigger an endpoint in your back end, and from here, you can fetch the latest data and write it to Neon. Here’s an example of how it works with Liveblocks Storage.

Which data can be synced?

Various types of Liveblocks data can be synched to Neon with webhooks.

Setup

Quickstart for synching Liveblocks data to Neon. In this example, we sync Liveblocks Storage data to Neon, but you can use the same pattern with other APIs and webhooks to sync other types of data.

1. Create the Neon table

   Use one row for each Liveblocks room.

   create table liveblocks_documents (  room_id text primary key,  data jsonb not null,  updated_at timestamptz not null default now());

2. Create a webhook endpoint

   Add a back end endpoint in your app, for example at /api/liveblocks-webhook.

   export async function POST(request: Request) {  const body = await request.json();  const headers = request.headers;
     // Verify the webhook event, then sync to Neon  // ...
     return new Response(null, { status: 200 });}

3. Subscribe to Storage updates

   In the Liveblocks dashboard, navigate to the “Webhooks’ page inside a project,
   and create a webhook endpoint for your endpoint URL—this requires you to host your local project. Subscribe to storageUpdated, then copy the webhook secret.

4. Verify the webhook event

   In your endpoint, using WebhookHandler, verify the webhook event with the webhook secret from the dashboard.

   import { WebhookHandler } from "@liveblocks/node";
   const webhookHandler = new WebhookHandler(  process.env.LIVEBLOCKS_WEBHOOK_SECRET!);
   export async function POST(request: Request) {  const body = await request.json();  const headers = request.headers;
     // Verify if this is a real webhook request  let event;  try {    event = webhookHandler.verifyRequest({      headers: headers,      rawBody: JSON.stringify(body),    });  } catch (err) {    console.error(err);    return new Response("Could not verify webhook call", { status: 400 });  }
     // Sync to Neon  // ...
     return new Response(null, { status: 200 });}

5. Sync Storage to Neon

   Set up your Liveblocks and Neon clients, before fetching the Storage document data with getStorageDocument and upserting the Neon row with on conflict … do update.

   import { Liveblocks, WebhookHandler } from "@liveblocks/node";import { neon } from "@neondatabase/serverless";
   const liveblocks = new Liveblocks({  secret: process.env.LIVEBLOCKS_SECRET_KEY!,});
   const sql = neon(process.env.DATABASE_URL!);
   const webhookHandler = new WebhookHandler(  process.env.LIVEBLOCKS_WEBHOOK_SECRET!);
   export async function POST(request: Request) {  const body = await request.json();  const headers = request.headers;
     // Verify if this is a real webhook request  let event;  try {    event = webhookHandler.verifyRequest({      headers: headers,      rawBody: JSON.stringify(body),    });  } catch (err) {    console.error(err);    return new Response("Could not verify webhook call", { status: 400 });  }
     if (event.type === "storageUpdated") {    const { roomId } = event.data;
       // Get Storage document data    const data = await liveblocks.getStorageDocument(roomId, "json");
       // Upsert into Neon    await sql`      insert into liveblocks_documents (room_id, data, updated_at)      values (${roomId}, ${JSON.stringify(data)}::jsonb, now())      on conflict (room_id) do update set        data = excluded.data,        updated_at = excluded.updated_at    `;  }
     return new Response(null, { status: 200 });}

6. Data sync is set up!

   Your Liveblocks data is now automatically synched to Neon when the webhook event is fired.

Limits and troubleshooting

Storage or Yjs data is stale

storageUpdated and ydocUpdated webhooks are throttled because collaborative documents can be modified up to 60 times per second. Treat Neon as an eventually consistent mirror, not as the live editing channel.

Webhook verification fails

Check that LIVEBLOCKS_WEBHOOK_SECRET is the webhook secret for the webhook endpoint that sent the event. Also make sure your endpoint passes the same raw body string to verifyRequest that it received from Liveblocks.

Neon writes fail

Keep DATABASE_URL on the server only. Use a role with permission to write the mirror tables. If you use Neon’s pooled connection string, follow Neon’s guidance for serverless and long-running workers.

Duplicate writes happen

Webhook deliveries can be retried. Use on conflict … do update upserts with a stable primary key such as room_id, thread_id, or comment_id so repeated deliveries update the same row.

Liveblocks REST requests fail

Check that LIVEBLOCKS_SECRET_KEY is a secret key from the same Liveblocks project as the room. If the request still fails, return a non-2xx response so the webhook can be retried.

Related docs

• Supabase + Liveblocks.
• API references for, webhooks, Node.js, Python, and REST API.