Ynot Leads Publisher

Ynot Leads Publisher sends submissions from supported WordPress forms to your Ynot LMS endpoint.

Supported form plugins:

• Contact Form 7
• Gravity Forms
• WPForms
• Elementor Forms

Key features:

• Embed Ynot Lead Forms with a WordPress block or shortcode, without API credentials.
• Inline forms, popup buttons, and floating widgets with light/dark appearance and accent colors.

• Automatic iframe resizing and optional site-wide floating widget.

• AJAX metadata refresh with no page reload.

• Per-form field mapping with hardcoded values where needed.
• Lead source, location, program, and state mapping support.
• Dynamic custom API field mapping rows.
• Recent logs for posted, rejected, error, and skipped submissions.

External services

This plugin connects to the Ynot LMS API to submit lead data and retrieve metadata (locations, programs, lead sources, states, and education levels).

What data is sent and when

• Lead submissions: When a visitor submits a form on your site (Contact Form 7, Gravity Forms, WPForms, or Elementor Forms), the plugin sends the mapped form field values (e.g. name, email, phone, address) to your Ynot LMS leads endpoint via an HTTP POST request.
• Metadata refresh: The plugin fetches reference data (campus locations, programs, lead sources, states, education levels, and custom field definitions) from the Ynot LMS API to populate the mapping dropdowns. This happens when an administrator clicks “Load My Data” in the plugin settings, on an hourly scheduled task, and when an administrator opens the plugin settings screen if the stored data is more than two hours old. The scheduled and automatic requests only run once an Access ID and Access Key have been saved; no request is made before the plugin is configured. These requests send only your Access ID and Access Key — no visitor or form data.

Service details

• Service: Ynot LMS API
• Endpoints used: https://api-{workspace}.ynotlms.com/leads.json (lead submission), plus /locations.json, /programs.json, /states.json, /lead_sources-basic.json, /level_of_educations.json, and /fields (metadata).
• Authentication: Requests include an Access ID and Access Key configured by the site administrator.
• Terms of Use: https://ynotlms.com/terms
• Privacy Policy: https://ynotlms.com/privacy

Hosted Lead Forms load from https://connect.ynotlms.com inside an isolated iframe. Visitor answers are submitted directly to Ynot, not forwarded or logged again by this plugin. Production forms use Cloudflare Turnstile for bot protection; configured address fields may use Google Places. These services are loaded by the hosted form. Popup forms load when opened; inline forms load when the page is viewed.

Embed a Ynot Lead Form

1. Create and publish your form in Ynot Admin > Lead Forms.
2. Under Publish & integrate, allow your WordPress website origin (including scheme and any nonstandard port). Allow both www and non-www origins if both are used.
3. In WordPress, open Ynot Leads > Lead Forms. Paste the published Share link and give the placement a name.
4. Choose Inline form, Button opens popup, or Floating widget; choose Light/Dark, accent color, and button text. Save the placement.
5. Insert the Ynot Lead Form block and select your placement. In Elementor or another page builder, use its Shortcode widget with the copied shortcode, e.g. [ynot_lead_form id="admissions"].
6. For a floating widget on every page, enable Show on every page instead of adding a block. Only one site-wide widget can be enabled. A page-specific floating placement takes precedence over the site-wide one.

Test embed displays the published form: submitting it creates a lead. Use Ynot Admin’s non-submitting preview for submission practice. Unpublished forms or websites not allowed by the form cannot embed it. The test checks for a response; it does not automatically change the form’s allowed websites.

Placement settings are stored in one WordPress option, with no new database tables. Published form changes appear automatically; renaming a placement preserves its shortcode ID. Removing a placement hides it wherever used. Authors/editors may insert saved placements; only administrators with manage_options can create, edit, or remove placements. Standard WordPress page caches may need purging after placement changes.

Requires a WordPress installation that permits plugins. Keep the existing Forms tab for Gravity Forms, Contact Form 7, WPForms, and Elementor submissions; those continue to use API credentials and mappings.