Nelx JFB Email Templates can pass selected email activity to Nelx CRM Communication so the email can be tracked as a CRM lead communication.
The integration is enabled per email template. This means you can track only the emails that belong in the CRM and leave other templates unchanged.
Before You Start #
Make sure Nelx CRM Communication is installed and active.
If it is not available, the CRM Communication switch in the email template is disabled and the plugin shows:
Install and activate Nelx CRM Communication to enable this integration.
You do not need to enable CRM tracking on every email template.
Enable CRM Communication for a Template #
Go to:
WordPress Admin → Nelx JFB Email Templates → Form Templates
Open the template you want to track.
Near the bottom of the template, find:
CRM Communication
Turn on:
Track this template as a CRM lead communication
Then click Save Changes.
From that point, email sends from that template can be passed to Nelx CRM Communication.
What the Integration Passes to the CRM Plugin #
When CRM Communication is enabled for a template, Nelx JFB Email Templates exposes the details of the actual email send to Nelx CRM Communication.
That includes:
- the template ID;
- the JetFormBuilder form ID;
- the submitted form data available to the email workflow;
- the recipient used for the email;
- the final subject;
- the final rendered email body;
- the email headers;
- the resolved email attachments;
- the Media attachment IDs where available;
- the actual mail result;
- the Message-ID used by the sent email.
Nelx CRM Communication decides how that information is stored and used on the CRM side.
Why the Message-ID Matters #
Every tracked email send carries the Message-ID from the actual mail operation.
Nelx JFB Email Templates captures the Message-ID used by PHPMailer for that specific email.
If PHPMailer has not already created one at that point, the plugin sets one on the same mail operation so the value passed to the CRM is the value used by the outgoing message.
This gives the CRM integration a reliable identifier for the email that was actually sent.

The Mail Result Comes From the Actual Send #
The CRM integration also receives the result returned by the email send.
This tells the integration whether WordPress reported the mail operation as successful or unsuccessful.
The CRM tracking does not replace the email send. It works around the same wp_mail() operation used by the template.
Attachments #
If the template sends attachments, the CRM integration receives:
- the resolved attachments used for that email;
- the related Media attachment IDs where those IDs can be resolved from the configured template attachments.
This also works with the attachment handling used by Nelx JFB Email Templates before the email is sent.
For configuring which form uploads belong to an email, see File Attachments & Secure Documents.
It Works With the Template’s Recipient Workflow #
CRM Communication is attached to the email template, not to one particular Recipient Type.
If that template uses a supported recipient workflow such as:
- Standard recipients;
- User ID Fields;
- User Roles;
- Rotation;
- Conditional Recipients;
- Smart Recipient;
- CCT Item recipients;
the CRM integration receives the send context produced by that workflow.
You do not configure the recipient again under CRM Communication.
Configure the email recipient normally, then turn on CRM Communication if that template should be tracked.
Multiple Email Templates on the Same Form #
A single JetFormBuilder form can have more than one email template.
For example:
- one template might send an internal lead notification;
- another might send a confirmation to the person who submitted the form.
CRM Communication can be enabled on one template and left off on the other.
The switch affects that template only.
This is useful when only the internal or customer-facing part of the workflow should be recorded as CRM communication.
CRM Communication Does Not Change the Email Content #
Turning on CRM Communication does not add text to the email and does not change the template design.
Your existing:
- subject;
- email content;
- recipient logic;
- branding;
- attachments;
- View in Browser setting;
- notifications;
continue to work as configured.
The CRM integration receives information about the email operation in addition to the normal send.
A Practical Lead Workflow #
Suppose a website has a lead form and an internal email template.
The template:
- receives the new lead form submission;
- sends the email to the assigned staff member;
- includes the submitted lead details;
- may attach uploaded documents;
- has CRM Communication enabled.
When the template sends the email, Nelx JFB Email Templates also provides Nelx CRM Communication with the form data and details of that exact send.
A separate customer confirmation template for the same form can leave CRM Communication disabled if it should not be tracked.
If the CRM Communication Switch Is Disabled #
Check:
- Nelx CRM Communication is installed.
- The plugin is active.
- Reload the Form Templates page after activating it.
- Open the template again and check the CRM Communication setting.
The switch is intentionally unavailable when Nelx CRM Communication is not detected.
If the Email Sends but the CRM Does Not Record It #
Check these points:
- Make sure Track this template as a CRM lead communication is enabled on the correct template.
- Click Save Changes after enabling it.
- Confirm that you are testing a new form submission after the setting was enabled.
- Confirm that Nelx CRM Communication itself is active and working.
- Check that you are looking for the communication related to the template you enabled, especially when the same form has several email templates.
- If attachments are important to the CRM record, confirm that the template attachment fields are resolving correctly.
Nelx JFB Email Templates provides the send context to the CRM integration. The CRM plugin is responsible for how that communication is stored and displayed.
For Developers #
When CRM Communication is enabled for a template, the integration exposes the email operation through:
nelx_jfb_email_crm_before_sendnelx_jfb_email_crm_after_sendnelx_jfb_email_crm_send_result
These hooks apply to CRM-enabled templates only. Templates without CRM Communication enabled continue through the normal email path.
Where to Go Next #
For the email itself, see Creating Your First Email Template.
For recipient routing, see Recipients & Delivery Options.
For attachments, see File Attachments & Secure Documents.
For in-app notifications, see Nelx Notification System Integration.

