Ninja Forms Sendy - WordPress Plugin

How to Set Up Ninja Forms Sendy for WordPress Subscriptions

Ninja Forms Sendy is useful when your WordPress form needs to do more than just save a submission or send an email to the site admin. It also needs to add the person to a Sendy list after the form is submitted. In this guide, we will walk through the practical setup flow for that connection: what to prepare in Sendy, which fields to create in Ninja Forms, how to map the data, where delivery usually breaks, and how to safely verify the result without creating unnecessary submissions from real visitors.

This article is not a replacement for the short product description at the top of the page. The focus here is practical use: how to build a subscription form or lead capture form, how not to confuse the list ID, what to do about user consent, how to tell a WordPress problem from a Sendy API problem, and when it makes more sense to choose a different integration method.

Facts about the add-on itself are confirmed by the WebHolics product page: it adds users to a Sendy list from Ninja Forms, supports different lists for different forms, can pass the name, email, and custom fields, and uses the Sendy API so the visitor never has to leave the site. The rest of the recommendations are based on the Ninja Forms, Sendy, and Amazon SES documentation, because the reliability of this setup depends not only on the add-on, but also on the form, the list, the API key, the mail infrastructure, and your data handling rules.

The core setup idea is simple: first make sure a standard Ninja Forms form submits correctly and saves properly, then connect the Sendy action, and only after that verify the subscriber in the specific Sendy list. If you start with the integration right away, troubleshooting becomes harder because it is unclear whether the issue is the email field, the form action, the API key, the list, the Sendy server, or Amazon SES limits.

What problem this form and Sendy integration solves

For a standard contact request, it is usually enough to email the administrator and maybe save the submission in the entries section. A marketing form works differently: after submission, the visitor needs to be added to a subscriber database so you can use newsletters, segments, autoresponders, or manual outreach in Sendy. Ninja Forms Sendy handles exactly that middle layer between a WordPress form and a Sendy list.

As a result, the form stays in the familiar Ninja Forms interface, while the subscriber list lives in Sendy. The visitor enters a name and email address, clicks submit, sees a success message, and the site passes the data to Sendy. If the form has additional fields, such as the service they are interested in, city, lead source, or marketing consent, those can be used as Sendy custom fields if they are prepared in advance and mapped correctly.

This approach is especially useful for sites where subscription is not the only purpose of the form. For example, the form may collect a consultation request, webinar registration, pricing request, or download request, while also adding the person to a separate Sendy list. That way, the administrator does not have to move addresses manually, and the mailing list grows automatically as soon as the form is submitted.

Where this product makes the most sense

This plugin is a strong fit for sites that already use Ninja Forms as their main form builder and Sendy as their email marketing system. In that case, there is no need to replace the form, redesign it, or embed a separate subscription widget on every page. You simply configure the necessary fields, add the integration action, and verify that the entry appears in the correct list.

• Lead capture forms where the user should be added to a list for later lead nurturing after submitting an inquiry.
• Update subscription forms where it is important to keep the form styled to match the site and avoid manually embedding external Sendy HTML.
• Different landing pages where each form needs to send subscribers to its own Sendy list.
• Scenarios with custom fields, where a simple name-and-email pair is not enough for segmentation.
• Agency sites and small teams where the administrator already knows Ninja Forms and does not want to train editors on a new form interface.

When this setup may be unnecessary

If all you need is a basic subscription form without Ninja Forms logic, it may be simpler to use a Sendy HTML form or a lightweight standalone widget. If the site builds all forms in another tool, such as Gravity Forms, WPForms, Elementor Forms, or WooCommerce checkout, it makes more sense to look for an integration that matches that data source. Ninja Forms Sendy should not become a universal bridge for every form on the site if Ninja Forms is barely used there.

There is also an infrastructure limitation. Sendy is a self-hosted application: it has to be installed, updated, connected to a mail service, and monitored for cron jobs, bounces, and complaints. If the team does not want to manage the server side of email marketing, a cloud service with built-in forms and built-in delivery may be a better choice, even if it is less flexible in terms of cost and control.

What to check before installation

Preparation matters more than the installation itself. The add-on sits at the intersection of three systems: WordPress, Ninja Forms, and Sendy. An error in any of them looks the same to the user - they submitted the form, but the subscriber never appeared in the list. That is why it helps to create a short dependency map before installation and go through it before activation.

Checking WordPress and Ninja Forms

First, make sure the core Ninja Forms plugin is installed, active, and able to create a normal form without any integration. Ninja Forms documentation describes a form as a set of fields and actions: a success message, email, submission record, redirect, and actions from add-ons. This matters because the Sendy integration should run as one of the post-submission actions, not as a separate page or external widget.

Open the WordPress admin panel and verify the following:

• The form can be created and saved with the Publish button in the Ninja Forms builder.
• The Emails & Actions tab includes an active success message so users can tell their submission was accepted.
• The submission record action has not been disabled without a reason, otherwise it will be harder to prove the form was submitted at all.
• The email field is required and uses a field type that validates the email format.
• The form is published on a page through a Ninja Forms block, shortcode, or metabox, rather than sitting hidden in a draft.

For the first round of testing, do not add complex conditional logic, multi-step flows, or unusual theme scripts. The simpler the starting form, the easier it is to see exactly where the problem appears.

Checking Sendy and the list

In Sendy, prepare the brand, list, custom fields, and working API access in advance. The Sendy API documentation shows that to add a subscriber you need the Sendy installation URL, API key, email address, and list ID. Name, country, page URL, IP address, and custom fields can be additional parameters if your data model requires them.

Pay special attention to the list ID. This is not the list name and not the page URL. In Sendy, it appears in the lists section as a separate ID. If you paste the list name instead of the ID, the integration may return an Invalid list ID error or simply fail to add the subscriber, depending on how the add-on displays the API response.

If you use double opt-in in Sendy, a new address may not be treated as active right away. The person has to confirm the subscription through email. So during testing, look not only at active subscribers, but also at statuses such as unconfirmed addresses if that logic is enabled for your list.

Email and Amazon SES

Sendy is commonly used with Amazon SES or another supported sending service. You do not need bulk sending yet just to add a subscriber through the API, but the mailing system as a whole still needs to be ready: the sender domain should be verified, SES limits should be understood, and bounce and complaint handling should be configured. Amazon SES documentation specifically warns that in sandbox mode you can send only to verified addresses and that limits apply. That does not stop you from adding an address to a list, but it does prevent full newsletter testing with real recipients.

Do not test the integration by sending a bulk campaign. For the first test, it is enough to add one internal email address to a separate test list, confirm that the record appears, and check the subscription status. Test newsletter campaigns separately after Sendy and SES are configured.

Consent and personal data storage

The add-on sends data from the form into an external system relative to WordPress - your Sendy installation. That means the form should include clear consent language, and the site's privacy policy should explain what happens to the email address. Ninja Forms provides tools for consent, export, deletion, and disabling storage for certain data, but the actual transfer to Sendy still needs to be documented in your site policies.

For a subscription form, it is usually helpful to add a required consent checkbox, separate explanatory text next to the email field, and a clear success message. If the form is only for subscriptions, you may want to limit storage of the full submission in WordPress. If the form also serves as a service request, keeping the data may be useful for support and auditing, but then you should define retention periods and admin-panel access in advance.

Installation and first launch with minimal risk

Installing the WordPress plugin is technically straightforward: upload the ZIP file through Plugins - Add New - Upload Plugin, activate it, and go to the settings. But with an integration add-on, what matters is not activation by itself, but the order in which you test things afterward. Do not connect it immediately to a live landing page form with traffic. Start with a test form and a test list.

Safe activation sequence

1. Create a restore point or make sure your hosting provider has a recent backup of the site.
2. Install and activate the core Ninja Forms plugin if it is not already installed.
3. Install Ninja Forms Sendy as a separate plugin and verify that no critical errors appear in the admin panel.
4. Open a test Ninja Forms form and check whether a new Sendy action type appears under Emails & Actions or in the form settings.
5. Save the form without publishing it on an important page, and test it only on a private page or temporary page with restricted access.

If the site shows an error after activation, disable the new add-on through the plugin list or your host's file manager if the admin panel is unavailable. Do not remove Ninja Forms or clear submissions before troubleshooting: you may need that data to understand at which stage processing broke.

Initial checks after activation

Right after installation, verify three things. First, the form submits normally without the Sendy action. Second, the Sendy action is available in the builder. Third, after adding the action, the user still sees the normal success message instead of a submit button that hangs. If the button stays stuck in the sending state, the problem is usually JavaScript, AJAX requests, cache, security plugins, or blocked admin-ajax.php, not the Sendy list itself.

It helps to run this test in a separate browser where you are not logged in as an administrator. That lets you see the form the way a visitor sees it and confirm that the theme is not hiding fields, cache is not breaking the submission, and no popup or script optimizer is interfering.

Quick takeaway: after installation, you should have a test form, a test Sendy list, and one successful test without real subscribers. Only then should you move the settings to the live form.

Configuring the Sendy action in the form builder

The most important part of the setup is correctly mapping form fields to Sendy fields and defining which list the subscriber should go to. In Ninja Forms, integrations like this usually live in the form action logic: email delivery, success message, database storage, webhook, or an action added by a third-party extension. Ninja Forms developer documentation specifically notes that many extensions rely on field mapping through keys and merge tags so the action knows which value to pull from the form.

Basic connection settings

In most scenarios, you will need three groups of data: the Sendy installation URL, the API key, and the list ID. The exact field names may vary depending on your version of the add-on, so focus on the meaning. The installation URL should point to your working Sendy install, not to a WordPress login page. The API key comes from Sendy, and the list is selected by its ID.

If the connection settings live on a global plugin settings screen, fill them out once and then configure the list inside each form. If the connection is configured directly inside the form action, repeat it carefully for each form and do not copy values from an old project without checking them. Different Sendy brands and lists can have different IDs, and errors here are almost invisible: the form submits, but the subscriber goes to the wrong place or is not added at all.

What counts as the minimum required setup

• The form's email field is mapped to Sendy email and is required.
• The list ID was taken from Sendy, not typed in from the list name.
• The Sendy URL uses the correct domain and opens over a secure protocol if HTTPS is configured on the server.
• The Ninja Forms success message does not promise an active subscription if the list requires email confirmation.
• The test address is not already on Sendy's suppressed, unsubscribed, or already-subscribed lists.

Mapping the name and custom fields

WebHolics states that the add-on can send the name, email, and custom fields. That does not mean every form field will automatically appear in Sendy. A custom field has to be created in Sendy, or you need to know its tag, and then it must be linked to the corresponding Ninja Forms field. The Sendy API documentation makes one important principle clear: a custom field is sent using its personalization tag as the parameter. That is why it helps to lock down the field name, case, and intended meaning in advance.

For example, if you collect city, requested service, and lead source, do not cram everything into one long comment field. Create separate fields in the form and separate fields in Sendy. That makes it easier later to segment the list, send a campaign only to people interested in a certain service, or exclude technical tests from campaigns.

Which fields are better left out

Do not send everything to Sendy by default. Fields containing detailed messages, internal comments, files, sensitive data, or internal flags are usually better kept in the WordPress submission or in your CRM, if you use one. Sendy is for email campaigns and segmentation, not for storing the full history of a request. The less unnecessary personal data you keep in a mailing database, the easier it is to keep things organized and stay compliant with data handling rules.

One list or multiple lists for different forms

One confirmed capability of Ninja Forms Sendy is that different forms can send people to different Sendy lists. That is useful if the site has separate funnels: newsletter signup, consultation request, event registration, document download. But you do not need to turn every landing page into a separate list just for the sake of organization. If the audience is the same and only their interests differ, it is often more practical to use a single list and a custom field for segmentation.

Separate lists make sense when the consent terms, email frequency, communication language, brand, content type, or legal basis for processing are different. If the only difference is the source, it is usually better to pass that source into a separate field and keep the user in a shared list.

The order of actions in the form

In Ninja Forms, form actions serve different purposes. For this integration, you will usually need at least a success message, a submission record, and the Sendy action. You can keep an email notification to the administrator if the inquiry requires manual follow-up. If the form is subscription-only and you do not want an email for every signup, that notification can be disabled, but it is still best to keep the record or test log while you are launching the setup.

Do not disable the submission record until testing is complete. If the subscriber does not appear in Sendy, the Ninja Forms record helps you determine whether the form made it to server-side processing and what values the user actually submitted.

Practical scenario: a consultation request form with newsletter signup

Let us walk through a specific example. A service business site has a page offering a free consultation. The visitor enters their name, email, phone number, and selects the service they are interested in. The administrator receives the inquiry, and the email address is added to a Sendy list for a follow-up email sequence. This is a typical scenario where Ninja Forms Sendy is more useful than a simple subscription form: one submission supports both sales follow-up and email marketing.

Goal and preparation

The goal is to receive the inquiry in WordPress and add the subscriber to a Sendy list with an extra interest field. Before setup, the following should be ready: a Ninja Forms form, a Sendy list, a Sendy field for the requested service, consent text, and a test email address you do not mind deleting after verification.

Step-by-step setup

1. Create a new form in Ninja Forms with Name, Email, Phone, a service selection field, and a consent checkbox for email marketing.
2. Make the Email field required and confirm that it uses the email field type rather than a plain text field.
3. On the Emails & Actions tab, keep the success message and submission record active.
4. Add the Sendy action and enter the Sendy installation URL, API key, and the test list ID, or choose the list in the action settings.
5. Map the form email field to Sendy email, the form name field to Sendy name, and the selected service to the Sendy custom field.
6. Save the form with Publish in the Ninja Forms builder.
7. Place the form on a private test page using the Ninja Forms block or shortcode.
8. Open the page in a private browser window, fill out the form with test data, and submit it.

Verifying the result

After submission, check three places. The public-facing page should display a success message. Ninja Forms should contain a submission record if you kept the save action enabled. In Sendy, the selected list should contain the test email or a record with the status that matches your confirmation mode.

If the record exists in Ninja Forms but not in Sendy, look at the integration settings: Sendy URL, API key, list ID, required fields, and the address status in Sendy. If there is no record even in Ninja Forms, the problem happens earlier: form publication, blocked submission, JavaScript, cache, security, a theme conflict, or an error in required fields.

A consent-related detail

If the form should add someone to the mailing list only when consent is checked, test both cases: with the checkbox checked and unchecked. Not every integration add-on can run the action conditionally based on a field value without extra Ninja Forms logic. If conditional execution is not confirmed in your version, do not promise the user a choice that the form cannot technically enforce. It is better to separate the inquiry form from the subscription form or rely on confirmation through the Sendy list.

How to verify the result on the site and in Sendy

Verification should be repeatable. A one-off submission from your personal email proves nothing if you do not know exactly what should appear in each place. Create a test checklist and use it after installation, plugin updates, form changes, theme changes, cache activation, and site migrations.

Successful submission checklist

• The user sees a clear success message, and the button does not hang in the sending state.
• A submission record appears in Ninja Forms with the fields that are supposed to be stored.
• The new address appears in the correct Sendy list, not in an old test list.
• Custom fields are filled with separate values, not merged into one unreadable string.
• If confirmation is enabled, the test email arrives at the recipient address and the status changes after confirmation.
• If the administrator email is enabled, it arrives with the correct sender address from the site's domain.
• No errors related to the form submission appear in WordPress, SMTP plugin, or hosting logs.

Why checking only the admin email is not enough

Many administrators assume the form is working if they received the notification email. For Ninja Forms Sendy, that is only a partial check. The email notification and adding the subscriber to Sendy are different actions. The first goes through wp_mail() and the site's mail infrastructure, while the second calls the Sendy API. One can work while the other fails.

Ninja Forms documentation and support regularly emphasize that email delivery depends on WordPress, action settings, and hosting. So the admin email is useful as a signal, but it does not prove the subscription succeeded. The real source of truth for this integration is a record in the correct Sendy list with the expected status and fields.

Testing after enabling cache and optimization

Once the form is working, test it again with cache, minification, and security plugins enabled. Forms often rely on AJAX and field validation scripts. If an optimizer combines or defers scripts without the right exclusions, the form may render but fail to submit. If a security plugin blocks WordPress AJAX requests, the button may show a long sending state with no result.

A safe way to test is simple: enable one optimization, clear the cache, submit a test form, and check Ninja Forms and Sendy. If it breaks, roll back only the last setting and add an exclusion for the form page or Ninja Forms scripts. Do not change five settings at once, or you will not know what caused the issue.

Consent, submission storage, and list hygiene

A subscription form is not only a technical setup, but also a database quality issue. Sendy can manage lists, custom fields, subscription confirmation, bounces, and complaints. Ninja Forms lets you configure fields, messages, storage, and GDPR-related actions. But the administrator still needs to decide what data to collect, where to store it, and how to prove that the user consented to receive emails.

How to handle consent in the form

Consent should be separate and easy to understand. Do not hide it inside the main submit button if the form also serves as a service request. The user should understand that they are submitting an inquiry and may receive emails afterward. The label next to the checkbox should state the type of emails, and the privacy policy should explain that the address is sent to Sendy.

If the Sendy list uses double opt-in, it is better to phrase the success message on the site carefully: not "You are subscribed," but "Check your email and confirm your subscription." That avoids misleading the user and reduces support questions.

What to store in WordPress and what to store in Sendy

For email marketing, you usually need an email address, a name, and a few segmentation markers. The full text of the inquiry, phone number, attached files, and internal comments should not be sent to the mailing system without a strong reason. In Ninja Forms, you can control data storage through the submission record action and its settings. If you need to reduce the amount of personal data stored in WordPress, disable or limit storage intentionally rather than manually deleting data after every test.

A practical model looks like this: Sendy stores what is needed for campaigns and segments; Ninja Forms stores the operational record of the inquiry for as long as it is needed for processing and auditing; unnecessary fields are not duplicated. Access to WordPress submissions should also be restricted by user roles, not opened to every site editor.

Protection against junk signups

If the form is on a public page, automated bots may submit it. Ninja Forms supports anti-spam approaches such as challenge questions, honeypot fields, and the Akismet action when Akismet is installed. The Sendy API also documents a honeypot parameter to protect the API call, but support for that specific parameter in your add-on version should be verified in practice or in the version documentation.

Do not start fighting spam with aggressive word or IP blocks if you do not understand the consequences. It is better to enable the form's built-in protections, verify that the email field is required, use subscription confirmation, and analyze where the junk submissions are coming from. Harsh rules can block real subscribers, especially if the form is available to an international audience.

Troubleshooting common problems

It is useful to classify integration problems by where the failure happens: the form does not submit, Ninja Forms accepted the submission but Sendy did not receive the address, Sendy received the address but added it to the wrong list, the subscriber appeared with incorrect fields, the email notification did not arrive, or Sendy campaigns are not sending. This structure saves time because each type of problem is checked with its own set of tools.

The form hangs on submission

Symptom: the user clicks the button, but the form keeps showing a sending state, no success message appears, and no Ninja Forms record is created. In this case, the Sendy integration may have nothing to do with it, because processing never reached the form actions.

Check the browser console, network requests, admin-ajax.php, cache, and security plugins. In Ninja Forms support discussions, a similar symptom is often linked to blocked AJAX or a conflict on the site side. Disable script optimizations one setting at a time and test again. If the form is embedded in a popup, temporarily place it as a regular block on a page to rule out a container conflict.

The subscriber does not appear in Sendy

Symptom: the success message appears, the Ninja Forms record exists, but the new address is missing in Sendy. At that point, you need to check the Sendy action: installation URL, API key, list ID, required email field, and API response. The Sendy API returns common errors such as missing key, invalid key, invalid email address, already subscribed, or invalid list ID.

Fix one parameter at a time. First confirm that the list ID was copied from Sendy. Then check whether you are trying to add an address that is already in the list, unsubscribed, bounced, or suppressed. After that, verify the API key and installation URL. If Sendy is protected by basic authentication, server-side security rules, or a redirect, the API call may not go through.

Custom fields are empty or mismatched

Symptom: the email is added, but the name, service, or source does not make it into Sendy. The cause is usually field mapping. In Ninja Forms, a field may have one visible label and a different key, while in Sendy a custom field may require a specific tag. If you changed the form after configuring the action, the old mapping may still be tied to a deleted or renamed field.

Open the Sendy action and select the fields again through the mapping interface instead of typing them from memory. Run a test submission with unique values, not just "Test," but something like "Test-service-one." That makes it easier to see which value ended up where.

The subscriber was added to the wrong list

Symptom: the address exists in Sendy, but not in the intended list. This is almost always a list ID error or copied settings between forms. If you use different lists for different landing pages, keep a simple reference table: form, page, list, purpose, segment field. Site visitors do not need that internal table, but it dramatically lowers maintenance risk.

If the number of lists has grown too large, consider moving to one list with a source field. That is not always the right approach, but it is often easier for segmentation and deduplication.

Emails are not arriving even though the subscriber was added

Symptom: the address appears in Sendy, but the user or administrator does not receive the email. Separate the two mail systems. The administrator email from Ninja Forms is sent through WordPress and the hosting environment or an SMTP plugin. Sendy campaign emails and confirmation emails go through Sendy and its sender configuration, such as Amazon SES. So the solution depends on which email is missing.

For Ninja Forms, check the email action, the From address, the sender domain, and mail logs. For Sendy, check the subscriber status, confirmation mode, the verified sender domain in SES, sandbox status, cron jobs, and bounce handling. Do not try to solve both issues with a single WordPress SMTP setting: it may help Ninja Forms notifications, but it will not fix a misconfigured Sendy installation.

Sendy shows campaign errors

Symptom: subscribers are added, but a campaign in Sendy does not start or remains stuck in preparation for a long time. Sendy documentation links cases like this to the cron job, the PHP path, and server restrictions. At that point, it is no longer a Ninja Forms Sendy issue. The form did its part, and Sendy now needs to be diagnosed as a separate application.

Check the cron configuration in your hosting panel, verify the PHP path, confirm that the Sendy URL is reachable, and review SES settings and bounce notifications. If a server security module is in use, it may interfere with Sendy when it tries to contact external services or receive notifications.

Compatibility with the theme, cache, and other extensions

Integration plugins rarely fail by themselves in isolation. More often, the issue appears after cache is enabled, the theme is changed, popups are added, security is installed, the site is moved to another domain, or the core Ninja Forms plugin is updated. That is why Ninja Forms Sendy needs not only installation instructions, but also a maintenance plan.

Cache and script optimization

Page cache usually does not interfere with the form display, but it can interfere with dynamic submission if an optimizer defers required scripts or breaks the loading order. If the form stopped submitting after optimization, exclude the form page, Ninja Forms scripts, or AJAX requests from aggressive rules. Do not disable all site cache forever if the issue is limited to one page: start with a targeted exclusion.

The theme and visual form output

The theme can affect the styling of fields, buttons, error messages, and the visibility of the consent checkbox. If the user cannot see a required-field error or the consent text, the form may technically work, but subscription quality will suffer. Test the form in the live theme, in desktop and mobile views, with long labels and real error messages.

Do not solve styling issues by editing plugin files. Use theme settings, Ninja Forms custom classes, a child theme, or safe CSS in the WordPress Customizer. If the add-on is updated, any changes made directly in plugin files will be lost.

Anti-spam, security, and access permissions

Security plugins can block suspicious POST requests, AJAX, REST requests, or calls to the external Sendy domain. If the issue appears only for logged-out users, check the security rules specifically for the public form. If the issue appears only for editors in the admin panel, check Ninja Forms permissions and role settings.

For ongoing maintenance, it helps to keep a separate test form page and one test Sendy list. After every major update, submit one test entry and follow the full path. That takes less time than trying later to figure out on which day subscribers stopped being added.

When Ninja Forms Sendy is the right choice

Ninja Forms Sendy is worth using when you already have a WordPress site built around Ninja Forms, a working Sendy installation, and a clear need to add form submitters to a mailing list. It is especially useful for lead forms where you need to combine an inquiry, a Ninja Forms record, an admin notification, and a Sendy subscription without manually transferring addresses.

Before launch, verify the base form, the Sendy list, the API key, the list ID, consent handling, custom fields, the success message, and the full test path from submission to the record in Sendy. After that, you can go to the Ninja Forms Sendy download, install it in a test environment or on a private page, and move the settings to the live form only after a successful control submission.

If you only need a simple subscription without a form builder, look at the built-in Sendy form or a lightweight widget. If your forms are already built in Gravity Forms, Elementor Forms, or another tool, look for an integration that matches that data source. But if Ninja Forms is the center of the form workflow and Sendy is the center of email marketing, the direct add-on remains the clearest path: the form collects the data, the action sends the subscriber, and Sendy manages the list and the follow-up communication.