> ## Documentation Index
> Fetch the complete documentation index at: https://docs.worldvisagroup.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How WorldVisa Console works

> Follow a notification from an API event through subscriber resolution and workflow steps to delivery, and understand how the Inbox fits into that flow.

WorldVisa Console connects the event in your application to the notification your user receives. Your application triggers a workflow through the API, the workflow resolves its recipients and runs its steps, and messages reach the Inbox or a configured delivery provider.

## How does the Inbox fit into the notification lifecycle?

The Inbox component displays in-app notifications inside your application. It connects to the configured environment and subscriber so each user sees their own messages.

When a workflow reaches an in-app step, it creates a message for that subscriber. The Inbox displays the notification and provides controls for reading it, following its actions, and managing preferences.

Your application is responsible for identifying the correct subscriber and configuring Inbox authentication. Keep secret API keys on your backend.

## What are the core concepts?

These concepts work together within the selected environment:

```mermaid theme={null}
flowchart TD
    app[Application event] --> api[Event Trigger API]
    subgraph environment[Selected environment]
        api --> workflow[Workflow]
        subscriber[Subscriber and preferences] --> workflow
        workflow --> steps[Conditions and configured steps]
        steps --> inbox[In-app message]
        steps --> provider[Delivery provider]
        workflow --> activity[Activity Feed]
    end
    inbox --> user[Recipient]
    provider --> user
```

### Organizations and environments

An organization groups your notification resources. Environments separate the workflows, subscribers, integrations, and credentials used for testing from those used for live delivery.

Use an API key for the environment you intend to trigger. A provider configured in one environment does not make it available in another.

### Workflows and triggers

A [workflow](https://docs.worldvisagroup.com/developers/concepts/workflows.md) defines the steps for a notification. Channel steps deliver messages; action steps add behavior such as a delay, digest, throttle, or HTTP request.

A [trigger](https://docs.worldvisagroup.com/developers/concepts/trigger.md) starts that workflow. In the REST request, `name` identifies the workflow, `to` identifies its recipients, and `payload` carries the event details used in templates and conditions. You can also attach context and other supported trigger options.

### Subscribers and preferences

A [subscriber](https://docs.worldvisagroup.com/developers/concepts/subscribers.md) represents a recipient in an environment. Its `subscriberId` identifies the recipient, while fields such as email, phone, and provider credentials determine how external channels can reach them.

Subscriber data can also personalize a message. [Preferences](https://docs.worldvisagroup.com/developers/concepts/preferences.md) affect which channels should deliver according to the workflow’s configuration.

To notify a group, resolve the intended audience in your application and pass the subscriber IDs to the trigger API. The current guides do not rely on a topic-management API.

### Channels and integrations

A channel is a delivery medium: in-app, email, SMS, push, or chat. An [integration](https://docs.worldvisagroup.com/developers/concepts/integrations.md) connects an external channel to a provider using credentials configured for that environment.

An email step might use SendGrid or Resend, while an SMS step might use Twilio. In-app messages are stored for the subscriber’s Inbox instead of going through an external messaging provider.

## How does the full notification flow work?

**1. Your application triggers a workflow**

Your backend calls `POST /v1/events/trigger` with the environment’s API key, the workflow identifier in `name`, recipients in `to`, and any event details in `payload`.

For a lead-assignment notification, the payload could include the lead’s name and a link to the record. See [Trigger a workflow](https://docs.worldvisagroup.com/developers/workflow/trigger-workflow.md) for request examples.

**2. The recipient is resolved**

WorldVisa resolves each subscriber in the current environment and uses the relevant profile data, channel details, and preferences for the run.

**3. The configured steps execute**

The workflow evaluates its steps in order. Conditions determine whether a step runs, templates use the available data to render content, and action steps apply the configured timing or logic.

**4. Messages reach their channels**

In-app steps create messages for the Inbox. External channel steps use the selected provider integration and recipient details to attempt delivery.

A successful trigger response means the event was accepted for processing. It does not confirm that every provider has delivered its message.

**5. You review the result**

Open the Activity Feed to inspect the workflow run and its steps. Use the transaction ID to trace the event and review failures such as missing recipient details, invalid credentials, or provider errors.

See [Monitor and debug a workflow](https://docs.worldvisagroup.com/developers/workflow/monitor-and-debug-workflow.md) when you need to investigate delivery.

> [card] [Explore core concepts](https://docs.worldvisagroup.com/developers/concepts/notification-event.md)
>
> Understand events, notifications, and messages in more detail.

> [card] [Build a workflow](https://docs.worldvisagroup.com/developers/workflow.md)
>
> Put the concepts together in the workflow editor.


## Related topics

- [What is WorldVisa Console?](https://docs.worldvisagroup.com/developers/what-is-worldvisa-console.md)
- [How do contexts work in WorldVisa?](https://docs.worldvisagroup.com/developers/concepts/contexts.md)
- [How do workflows work in WorldVisa?](https://docs.worldvisagroup.com/developers/concepts/workflows.md)
- [How do subscribers work in WorldVisa?](https://docs.worldvisagroup.com/developers/concepts/subscribers.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.