Inbox

The Inbox Message node delivers a message to a contact's in-app or server-side Inbox. It is the action node you use to deliver Inbox content in both One-Time and Recurring flow campaigns.

This page covers only what is specific to the Inbox node — selecting content, choosing the delivery application, tags, expiry, and priority. For creating the campaign, scheduling, and selecting the audience, see One-Time Flow Campaigns or Recurring Flow Campaigns.

Prerequisites

Before adding an Inbox Message node, make sure that:

The Inbox content you want to send has been created and published in Content → Inbox Message. Contents still in Draft state appear in the selection list but cannot be selected — finish and publish the content first.
The application you plan to deliver to has been set up: an existing iOS / Android / Web application (SDK path) or a Custom Inbox application (server-to-server path).

Add the node to the flow

On the flow canvas, drag the Inbox node from the Actions panel onto the canvas, next to Email, SMS, Push, In App, and On-Site.

Connect the node after the Audience node (or after any decision/wait node in your flow).

Alternatively, from the content side: after publishing an Inbox Message, click Create Campaign to open the campaign builder with your content pre-selected.

Double-click the node to configure it. Configuration has two steps: 1 – Content and 2 – Settings.

Step 1 — Select the content

Element	Description
Node Name	Enter a descriptive name for the node. Named nodes are much easier to tell apart in multi-message flows.
Content drawer	Select a published Inbox Message, or create new content directly from the drawer without leaving the flow.
Select Application	Choose where the message will be delivered: your existing iOS / Android / Web applications (SDK path) or Custom Inbox applications (server-to-server path).

📘
One node, one path.
SDK applications and Custom Inbox applications cannot be selected in the same node. To deliver the same message through both paths, add a second Inbox Message node. Also note that the audience count may decrease according to the chosen applications: Custom Inbox apps count per contact, real apps per device (each contact's most recently active device).

Click Next to continue to the settings step.

Step 2 — Configure the settings

Setting	Default	Description
Tags	None	Tags belong to the campaign node, not to the content. Use them to group or filter sends in reporting.
Expiry	7 days (168 hours)	Choose a duration ("Remove from inbox in X days/hours") or a fixed date ("Remove from inbox on [date]"). The maximum is 7 days (168 hours).
Priority	—	Set a priority level from 1–5.

Supported features: Content Version, Multi-language, Content Preview, Test Sending, Drop Condition, Google Analytics, Blackout, Priority, Random Split, Decision Split.

Not supported: Hourly Capping, Frequency Capping, Skip Permission, A/B Testing, Optimize Channel, Optimize Time, Transactional Sending, Marketing Send Logs, Engagement Split, Conversion.

Test and save

Click Test to send the message to yourself or a test list. Always test before publishing — the test uses the selected content and settings exactly as configured.

Click Save to close the node.

Complete the rest of the flow — every path must end with an End node — then publish as described in One-Time or Recurring Flow Campaigns.

📘
An Inbox Message node is not limited to one per flow. Combine it with Wait and Decision Nodes to build sequences — for example: Inbox Message → Wait 2 days → Decision Split (opened) → follow-up Inbox Message to non-openers.

Example: a welcome notice

A team wants to greet new app users with a one-time Inbox message, without any follow-up logic:

In a one-time campaign, drag the Inbox Message node after the Audience node and select the Welcome Message content. Name the node Welcome Notice.
Click Select Application and choose your iOS / Android / Web app.
Open the Settings tab and set an Expiry (up to the maximum of 7 days / 168 hours).
Connect the node straight to an End node.
Click Test to preview it on a test device, then Save and publish.

That's the whole flow: Audience → Inbox Message → End. No Wait or Decision nodes are needed for a single, standalone send.

Troubleshooting

Symptom	Likely cause
A content is visible but cannot be selected	It is still in Draft — open it in Content → Inbox Message and publish it.
Application list is empty or missing an app	The application has not been set up as an iOS / Android / Web (SDK) app or a Custom Inbox app — set it up before creating the node.
Both SDK and Custom Inbox options are needed	Not possible in one node — add a second Inbox Message node for the other path.