Publishing from your server

Your backend can push to connected clients: “your export is ready”, “the order shipped”, “maintenance in five minutes”. It doesn’t need a live connection to do it.

Decide who may publish (Studio)

Services → Realtime → Settings → Apps may publish. Off: only your servers and flows publish; apps can still listen. For notification-style channels turn it off, and set the channel rule’s Publish policy to Secret keys & Studio (Channel rules).

Publish from your server

// On a server with a secret key
await pawabase.realtime.publish("user:42", "export.ready", { url, name: "report.pdf" });

pb.realtime.publish("user:42", "export.ready", {"url": url, "name": "report.pdf"})     # the sync client is fine

The result gives the message id. With a secret key a message has from: "server". A publishable key is subject to the channel’s Publish policy, which is how a browser publishes without a socket.

Publish from a flow

Flows can publish too. In the flow editor (Logic → Flows), add the Realtime publish step, choose the channel and event, and map the payload from earlier steps. No code is needed.

Webhook subscriptions

Services → Realtime → Subscriptions → Webhook subscriptions. Webhooks that fire on every publish. New webhook subscription:

Field	Meaning
Name	`realtime-to-logs`
URL	`https://example.com/hooks/realtime`
Channel	The channel (or pattern) to watch, such as `orders`
Event	An event name, or all

Use it to mirror live traffic to a log, an analytics tool or another service. The list shows Delivered counts; with none it says No webhook is subscribed to realtime events.

Pattern: tell one person

Add a channel rule user:{{ auth.id }} (Kind Private), Subscribe Signed-in users, Publish Secret keys & Studio. A person can only open their own inbox.
Each signed-in client subscribes to user:<their id>.
Your server or a flow publishes to that channel when something happens.

const mine = pawabase.realtime.channel(`user:${user.id}`);
mine.onEvent("export.ready", (m) => toast(`Your export is ready: ${m.payload.name}`));
await mine.subscribe();

mine = pb.realtime.channel(f"user:{user_id}")
mine.on("export.ready", lambda m: toast(m["payload"]["name"]))
await mine.subscribe()

Messages are not storage

A client that’s offline when you publish only receives the message if the channel keeps history and the client replays (History). For anything that must reach the person, save a record (a notification row) and publish a message telling the app to look.

Tips

Keep payloads small: identifiers and a little text.
Name events for what happened (order.shipped), not what the client should do.
Publish after the change is saved, so a client that reacts can read the data.

Channel rules

Publish policy.

Playground

Send a test publish.

Getting started

Set up in Studio

Use it from your app

Build well

Publishing from your server

Decide who may publish (Studio)

Publish from your server

Publish from a flow

Webhook subscriptions

Pattern: tell one person

Messages are not storage

Tips

Channel rules

Playground

​Decide who may publish (Studio)

​Publish from your server

​Publish from a flow

​Webhook subscriptions

​Pattern: tell one person

​Messages are not storage

​Tips

Channel rules

Playground

Decide who may publish (Studio)

Publish from your server

Publish from a flow

Webhook subscriptions

Pattern: tell one person

Messages are not storage

Tips