Recipient & Workflow
- ✓Dynamic recipient routing
- ✓Conditional recipient groups
- ✓WordPress users and roles
- ✓Sequential rotation
- ✓CCT-driven recipients
- ✓Post meta assignment storage
- ✓Reply-to support
- ✓Smart recipient context
Build branded transactional emails, route recipients with real workflow logic, modernize file uploads and standard form fields, and keep attachments compatible with secure document storage from form to inbox.
Nelx JFB Email Templates adds a dedicated layer around JetFormBuilder for email routing, branded rendering, dynamic content, attachment handling, live media uploads and optional modern form-field styling — without replacing JetFormBuilder as the source of truth for form values, validation or field rules.
Send to email addresses, WordPress users, user IDs, roles or JetEngine CCT-driven recipients, with conditions and rotation.
Automatic round-robin rotation distributes submissions evenly across your team.
Structured two-way communication with automatic reply routing and context tracking.
Create in-app notifications alongside emails for seamless team collaboration.
Build reusable transactional emails with logos, containers, buttons, backgrounds, footers, responsive layouts and View in Browser.
Professional submission feedback with animations and customizable styling controls.
Optional drag-and-drop media fields with genuine live progress, guests, repeaters, multiple files and preset/edit-mode media.
Use form values, user context, post data, CCT fields, dates, terms, option labels and repeater data in the same template.
Apply a restrained modern UI to standard JFB controls, including a custom single-select experience backed by the native select.
The plugin adds workflow intelligence without replacing JetFormBuilder as the form engine.
JetFormBuilder handles the form, validation and submitted data. Optional Modern Form Fields and Modern Media Upload improve the frontend experience.
Recipient type, conditions, rotation, role rules, CCT context and smart-recipient logic determine who should receive the message.
Dynamic placeholders, repeater data, branding, buttons, attachments and responsive email structure are assembled into the final transactional email.
WordPress sends the email through your configured mail transport. Optional Nelx integrations can handle secure storage and in-app notifications.
Replies route intelligently between customer and staff.
Assigned user IDs stored for reporting.
One form workflow: capture cleanly, resolve the right recipients, compile the message, and deliver it with the context and attachments intact.
JetFormBuilder remains the form engine. Nelx adds the routing, rendering, attachment handling and optional frontend experience around it.
The goal is not to replace JetFormBuilder. It is to make transactional form workflows easier to maintain once they move beyond a basic notification.
Send emails based on form answers, WordPress users, user IDs, roles, CCT items, inserted post data or dynamic fields. Conditional groups and sequential rotation let the same form serve different teams without duplicating the workflow.
One template, multiple recipient pathsCreate reusable email layouts with logo, typography hierarchy, message containers, buttons, footer content, social elements, inbox preview text and optional View in Browser copies. Delivery and preview use the same compiler.
Reuse submitted form values, recipient and current-user context, inserted post data, post meta, CCT fields, dates, taxonomy terms, glossary labels, manual option labels and repeater rows inside the same transactional message.
The workflow can look polished before the user ever reaches the inbox. Modern Media Upload and Modern Form Fields are independent, optional enhancements. Turn on either one, both, or neither.
Drag and drop files with real browser-to-server progress and no second file transfer when the form is submitted.
Modern Media Upload works with guest forms, dynamically added repeater rows and JFB maximum-file rules.
Existing saved attachments are mirrored in the modern UI while JetFormBuilder keeps its native hidden preset value as the source of truth.
Submit controls are disabled while any live upload is still in progress and restored only when every upload has finished, failed or been cancelled.
Apply a consistent treatment to standard JFB inputs, textareas, checkboxes, radios and single-select controls without changing submitted values.
Use the same form and template infrastructure across support, client, appointment and internal workflows without giving up JetFormBuilder as the form engine.
Route requests, keep replies branded and attach submitted files with readable filenames.
Use edit forms, preset media and secure documents without falling back to a dated upload experience.
Send branded confirmations and updates around booking, provider and appointment workflows.
Use conditions, roles, rotation, post-meta assignment and notifications for approvals and business processes.
Reuse branded template and workflow patterns across operational client projects.
Route applications, approvals and documents by team, role, submitted values or assigned user.
Nelx JFB Email Templates extends existing WordPress and JetFormBuilder workflows instead of replacing their data and validation layer.
Its purpose is transactional and workflow communication around JetFormBuilder — not marketing automation.
Every version includes the core email workflow and modern form-experience system. Upgrade when you need more configuration scale and support.
Perfect for Getting Started
Scale Your Workflows
No separate feature tier for live uploads or modern form fields. Build the workflow first. Upgrade when you need more scale.
The free version is intentionally practical. You can build branded transactional emails, test routing, use Modern Media Upload and Modern Form Fields, and configure real workflows before you need a larger license.
Experiment with routing, branding and dynamic content
Enable live uploads and modern fields where the UX needs it
Use operational workflows for your own team
Run practical workflows before you need more scale
When the workflow grows, Premium removes configuration limits and adds priority support.
Build reusable branded messages, route recipients intelligently, modernize the form experience and keep attachments compatible with the workflows behind your WordPress system.
Search or browse through all 23 standard plugin questions below:
No additional external services are required for the core workflow system. The plugin works directly inside WordPress and JetFormBuilder, which keeps workflows centralized and avoids relying on multiple third-party automation platforms. Performance will still depend on factors such as hosting quality, SMTP configuration, and the complexity of your workflows.
Yes for standard workflows. Most features are configured through the WordPress admin interface without coding. However, advanced workflows involving conditional logic, post meta automation, or complex routing will be easier if you are already familiar with JetFormBuilder, WordPress users and roles, and dynamic form workflows.
The plugin falls back to your default recipients. This ensures submissions are still delivered even when conditional rules are not matched.
Yes. When rotation is disabled, emails can be sent to multiple recipients using BCC for recipient privacy. When rotation is enabled, submissions are assigned to one recipient at a time.
Yes. Each conditional recipient group can have its own rotation logic and assignment tracking. For example: Sales requests can rotate among sales staff, Support tickets can rotate among support agents, High-priority issues can rotate only among senior team members.
No. JetEngine is only required if you want to create CCT-based in-app notifications. Core email workflow features work independently.
Your existing JetFormBuilder forms continue working normally. Only the advanced workflow features provided by Nelx JFB Email Template become inactive until the plugin is reactivated.
Yes. The workflow structure is especially useful for agencies, client portals, support systems, HR platforms, and operational business websites. The 100-site license is designed specifically for multi-site or client-based usage.
Yes. The plugin supports inserted post workflows and can use inserted post IDs, post URLs, post titles, and post meta values within email logic and notifications.
Because workflow limitations are easier to evaluate through real usage than through feature restrictions. Instead of disabling core functionality, the free version limits how many templates and modal configurations you can create. This allows you to test complete workflows before deciding whether you need more scale.
Simply use {repeater_name} in your email content. The plugin automatically formats repeater data as an HTML table on desktop (with horizontal scroll, sticky headers, and alternating row colors) and switches to stacked cards on mobile for optimal viewing. All repeater sub-fields are displayed in both layouts.
Use {field_name:glossary|id} for fields with options fetched from glossaries (displays the label instead of raw value). Use {field_name:options} for manual options (automatically converts private_limited to Private Limited while preserving acronyms like CEO, API, PDF). Without these placeholders, raw values like private_limited will be shown.
Yes. Use the syntax {repeater_name|subfield1:glossary|id,subfield2:options}. For example: {footballer|nationality:glossary|55,clubs:options,trophies:options}. This will process only the specified sub-fields while displaying ALL sub-fields in the email. Sub-fields without configuration show their raw values.
The plugin intelligently preserves common acronyms like CEO, CFO, API, PDF, URL, ID, HR, IT, CRM, ERP, and 200+ others. For example, ceo_approval becomes CEO Approval (not Ceo Approval), and pdf_file_upload becomes PDF File Upload.
Absolutely. When configuring repeater sub-field processing, you can specify glossary lookups for any sub-field. Example: {order_items|product_type:glossary|45,status:glossary|78}. This is perfect for displaying clean labels from your JetEngine glossaries instead of raw option values.
Yes. The plugin uses a dual-layout system: HTML tables with horizontal scroll on desktop/tablet, and stacked card layout on mobile (screens ≤ 600px). This ensures your repeater data is always readable regardless of the device your recipients use.
Go to JetEngine Dashboard - Glossaries. Each glossary has its ID beside it labelled, for example: ID:3
No. The :options placeholder only affects fields you explicitly use it with. Text fields like registration numbers (e.g., QYR-4500R-KE) will remain unchanged. Only fields using {field_name:options} are processed.
No. The modern uploader changes the interaction layer, but JetFormBuilder remains authoritative for field restrictions, validation, maximum files, MIME types and submitted values.
Yes. The live uploader supports guest and logged-in submissions, Media Fields inside JetFormBuilder repeaters, multiple files where allowed, and preset attachments on edit forms. Existing preset values remain under JetFormBuilder control.
When Nelx Secure Document Storage is enabled for the form, live uploads can enter protected pending storage and are finalized through the secure storage workflow. Original filenames are preserved for outgoing email attachments even when the stored file uses a hashed secure name.
Yes. They are independent settings. You can enable Modern Form Fields, Modern Media Upload, both features, or neither.
No. The enhanced dropdown is the visual interaction layer. The original native select remains the actual form control, receives the selected value and continues to drive JetFormBuilder validation, conditions and form submission.
No matching questions.