Nelx Notification System Integration

Nelx JFB Email Templates can create an in-app notification for the same workflow that sends an email.

This feature is optional. It requires Nelx Notification System to be installed, active, and configured.

The Notification System remains responsible for the notification storage and its CCT field mappings. The email template only supplies the notification details that belong to that particular workflow.

Before You Start #

Make sure Nelx Notification System is:

• installed and active;
• configured with its notification CCT;
• configured with the field mappings it needs for recipients, type, message, URL, status, and related notification data.

Nelx JFB Email Templates checks for the Notification System’s local notification service and its configured CCT before the notification option can be used.

There is no separate notification endpoint to configure inside an email template.

Open the Template #

Go to:

WordPress Admin → Nelx JFB Email Templates → Form Templates

Open the email template you want to configure.

Scroll to:

Notifications Settings

Turn on:

Create notifications for recipients

If Nelx Notification System is not available or is not configured, the switch is disabled and the template shows a notice.

What You Configure in the Email Template #

The template only asks for three notification values:

• Event Type
• Notification Message Content
• Notification URL Content

The CCT field mappings remain in Nelx Notification System.

Event Type #

Event Type is the notification type stored for this event.

If the Notification System has configured event types available, the template shows them in a dropdown.

Choose the relevant type.

If no event types are available from the current notification configuration, you can enter the value manually.

For example:

ticket

or:

task

Use the values expected by your Notification System configuration.

Notification Message Content #

Use Notification Message Content for the short text the user should see in the notification.

For example:

A new task "{post_title:inserted}" has been assigned to you.

The message supports the same useful dynamic values used by the email workflow, including:

• normal form fields such as {task_title};
• recipient placeholders such as recipient:first-name;
• current-user placeholders;
• inserted-post placeholders;
• supported CCT placeholders when the template is working with a CCT item.

Keep the notification shorter than the email. Its purpose is normally to tell the user what happened and give them a reason to open the related page.

For placeholder syntax, see Dynamic Content, Placeholders & Macros.

Notification URL Content #

Use Notification URL Content for the page the notification should open.

You can use a direct URL or a dynamic value.

For example:

{post_url:inserted}

or:

https://example.com/account/requests/{request_id}

The template can also help you insert post data or select a WordPress page/post where the current UI provides that option.

If no URL is needed, the notification can be created without one.

Who Receives the Notification? #

The notification follows the recipient workflow that produced the email.

That means the notification can follow:

• Standard recipients that resolve to WordPress users;
• User ID Fields;
• User Roles;
• CCT Item recipients;
• Rotation;
• Smart Recipient;
• Conditional Recipients.

The Notification System ultimately needs a WordPress user or configured role target it can store.

Standard and User ID Recipients #

For normal user-based delivery, a notification is created for each resolved WordPress user.

Recipient placeholders in the notification message are processed for that user.

This lets a message such as:

Hello recipient:first-name, a new task is waiting for you.

use the actual recipient’s details.

User Role Recipients #

When the template sends to a WordPress role without Rotation, the notification integration can use the role mapping configured by Nelx Notification System.

The Notification System remains responsible for how role-targeted notifications are stored and displayed.

If Rotation is enabled, one user is selected from the recipient pool and the notification follows that selected user instead.

Rotation #

When Rotation selects one recipient, the notification is created for that rotated user.

The notification is created after the rotation email workflow has run.

If a Conditional Recipient rule has its own Rotation and notification settings, those condition settings are used for the selected recipient.

For Rotation setup, see Round-Robin Rotation & Assignment Tracking.

Smart Recipient #

Smart Recipient can also create notifications for the users selected by the conversation-routing workflow.

The same participants who are resolved for the email workflow are passed into the notification workflow when notifications are enabled.

For the conversation rules themselves, see Smart Recipient & Conversation Routing.

Conditional Recipients #

Each Conditional Recipient group can have its own notification settings.

Inside the condition, turn on:

Enable notifications for this condition

Then configure that condition’s:

• Event Type;
• Notification Message Content;
• Notification URL Content.

When that condition matches, its notification settings are used for the users resolved by that condition.

This is useful when different routes need different notification wording.

For example:

Sales enquiry

New sales enquiry from {full_name}

Support enquiry

New support request from {full_name}

The routing itself is covered in Conditional Recipients & Routing Rules.

Notifications With CCT Item Recipients #

If the email template uses CCT Item as its Recipient Type, the notification can follow the users resolved from that CCT item.

The notification message can also use supported CCT placeholders such as:

[quote_number]

or:

[client_name]

For CCT recipient setup and placeholder syntax, see CCT Recipients & CCT Placeholders.

Inserted Post Information #

When the JetFormBuilder submission creates a post, the notification integration can also carry the inserted post ID as the related object.

This happens automatically when {post_id:inserted} is available in the processed form data.

You can also use:

{post_url:inserted}

in the Notification URL Content when the notification should open that post.

What the Notification System Handles Automatically #

When Nelx JFB Email Templates hands the notification to Nelx Notification System, the Notification System handles the actual notification creation.

The email template does not ask you to configure CCT column names separately.

That mapping remains centralized in Nelx Notification System.

A Simple Example #

Suppose a task form:

• creates a task post;
• assigns it to a staff user;
• sends the staff member an email.

You could also configure:

Event Type

task

Notification Message Content

A new task "{post_title:inserted}" has been assigned to you.

Notification URL Content

{post_url:inserted}

The user receives the email and a matching in-app notification from the same form workflow.

If the Notification Switch Is Disabled #

Check:

1. Nelx Notification System is installed and active.
2. The Notification System has been configured and saved.
3. Its notification CCT is configured.
4. Reload the Form Templates page after completing the Notification System setup.

If the Email Sends but No Notification Appears #

Check:

1. Create notifications for recipients is enabled.
2. Event Type, Message, and URL values are valid for the workflow.
3. The email recipient resolves to a WordPress user or supported role target.
4. Nelx Notification System itself can create and display notifications.
5. For Conditional Recipients, confirm that notifications are enabled on the condition that actually matched.
6. For Rotation, confirm which user was selected for that submission.

Start by testing the Notification System independently if its own notifications are not appearing.

Where to Go Next #

For recipient selection, see Recipients & Delivery Options.

For per-condition notification settings, see Conditional Recipients & Routing Rules.

For Rotation, see Round-Robin Rotation & Assignment Tracking.

For CCT recipients, see CCT Recipients & CCT Placeholders.