Home / Product / Custom event publication

Start the next experience

Tell the rest of the product when a meaningful action has happened.

Publish a named topic from an action so connected clients can respond to business events, not only raw record changes.

See what it changes Technical guide ↗

Custom event publication in a product

Complete meaningful workApproval, import, publish, or delivery

Name what happenedEmit a product topic from the action

Let clients respondRefresh, notify, or continue the experience

Actions can create product-level live signals

01Speak in product eventsPublish “request approved” instead of forcing clients to infer it.

02Connect backend work to live UXNotify relevant screens after the action succeeds.

03Keep event creation reusableEmit from the same named action used across clients and schedules.

Why it matters

A record update says what changed. A product event says why it matters.

A client can observe that a status field changed, but it may not know that a review completed, an import finished, or a publication became live. Reconstructing meaning from low-level changes couples every client to implementation detail.

Daptin actions can publish to named topics as one of their outcomes. The action already understands the user's intent and the work it completed, so it can emit a more useful live signal.

Connected clients can then refresh the right view or start the next experience without each one reverse-engineering the database change.

Give live updates meaningful names

Use the language of the product workflow.

Emit after the relevant operation

Keep event publication beside the action and its outcome.

Reuse across starting points

Whether a screen or schedule calls the action, the live signal keeps the same meaning.

How it fits

Part of one connected backend.

Custom event publication does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Invoke

A permitted caller starts the named action.

Step 2Complete

The action performs its required product work.

Step 3Publish

An outcome emits the selected topic and context.

Step 4React

Subscribed clients update the experience or fetch current durable data.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Approval completed

Tell the requester and reviewer views to refresh.

Import ready

Announce that new content is available to browse.

Publication live

Update dashboards or previews when content becomes public.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes custom event publication more useful.

Know the boundary

What Daptin leaves in your hands.

Topic publication is live delivery, not a durable message bus. Use stored records or audit history for replay and recovery, and design clients to reload authoritative state after reconnecting.

Understand the operating responsibility →

Build from one foundation

Make custom event publication part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get Daptin Explore all capabilities