Skip to content
Nappai Documentation

Listen

Listen is a simple tool that lets your dashboard wait for a specific notification and then gives you the data that comes with it. Think of it as a “listening post” that watches for a message with a name you choose and hands that message over to the next step in your workflow.

How it Works

When you drop the Listen component into your flow, you give it the name of the notification you want to catch. The component then checks the system’s notification queue for a message with that exact name. Once it finds one, it grabs the whole notification (including any attached data) and passes it on as its output. No extra work or external services are needed—everything happens inside Nappai.

Inputs

  • Name: The exact name of the notification you want to listen for.
    Visible in: All

Outputs

The component outputs the full notification object (called Data). This object contains whatever information was sent with the notification, such as text, numbers, or links. You can feed this output into other components to trigger actions, update records, or display information to users.

Usage Example

  1. Add the Listen component to your flow.
  2. In the Name field, type NewOrder.
  3. Connect the output of Listen to a Send Email component.
  4. In the email component, use the data from the notification (e.g., order ID, customer name) to personalize the message.

When an order is placed elsewhere in your system, a notification named NewOrder is sent. The Listen component catches it, hands the order details to the email component, and the customer receives a confirmation.

  • Send Notification – Create and send notifications that the Listen component can catch.
  • Trigger – Start a workflow automatically when a specific event occurs.
  • Wait – Pause a workflow for a set amount of time before continuing.

Tips and Best Practices

  • Use clear, unique names for notifications so the Listen component can find the right one.
  • Test with sample notifications before deploying to production to make sure the name matches exactly.
  • Keep the notification payload small; only include the data you really need to avoid unnecessary load.
  • Chain multiple Listen components if you need to react to several different notifications in the same workflow.

Security Considerations

  • Notifications may carry sensitive data (e.g., personal information, financial details).
  • Ensure that only authorized components receive and process these notifications.
  • Use Nappai’s built‑in access controls to restrict who can create or listen for specific notifications.