Errors and Solutions

This guide contains the most common errors when using the WPify Raynet plugin and steps to resolve them.

Connection Errors

Update code lists fails or shows an error

Cause: The API credentials are incorrect or the Raynet API is unreachable.

Solution:

1. Verify that Email, API Key, and Instance name are correctly filled in
2. Make sure you copied the values without extra spaces
3. Check that your Raynet account is active and has API access enabled
4. Try again — the Raynet API may have been temporarily unavailable

Lead is not created in Raynet after form submission

Cause: The form mapping is incorrect, the API connection failed, or the required Topic field is missing.

Solution:

1. Check that the Topic field is mapped — it is required for every lead
2. Verify the API connection by clicking Update code lists
3. Check the logs at WPify → WPify Logs for error details
4. Make sure the form plugin integration is enabled in Enabled integrations
5. Verify that the form you are using is selected in the Forms mapping section

Form Integration Errors

Forms are not listed in the form selector dropdown

Cause: The form plugin integration is not enabled, or no forms have been created yet.

Solution:

1. Go to WPify → Raynet and check that the correct form plugin is selected in Enabled integrations
2. Save the settings and reload the page
3. Make sure you have created at least one form in the respective form plugin

Form fields are not showing in the field mapping dropdowns

Cause: The form needs to be saved first, or the code lists have not been updated.

Solution:

1. Save or re-save your form in the form plugin
2. Click Update code lists in the Raynet settings
3. Reload the settings page

Plugin conflicts with Divi theme or other page builder

Cause: Some page builders load form plugins in a non-standard way that may interfere with the form submission hooks.

Solution:

1. Ensure your form plugin and WPify Raynet are both updated to the latest version
2. Test the form submission without the page builder’s form wrapper
3. Check the browser console (F12) for JavaScript errors
4. Contact support if the issue persists

Data Mapping Errors

Custom fields are not saved to Raynet

Cause: The Raynet field ID is incorrect or the code lists are outdated.

Solution:

1. Click Update code lists to refresh available fields
2. Copy the exact field ID from the code list display
3. Make sure the custom field has a value (either from the form or as a static value)
4. Check the logs for any API error responses

Email notifications are not sent

Cause: Notification emails are not configured for the form mapping.

Solution:

1. In the form mapping, add email addresses to the Notification emails field
2. Verify the email addresses are correct
3. Check your server’s email sending capability (some hosts block outgoing emails)

Frequently Asked Questions (FAQ)

Which form plugins are supported?

The plugin supports Contact Form 7, Fluent Forms, Ninja Forms, and WP Forms. You can enable multiple integrations simultaneously if you use more than one form plugin.

Can I send data from multiple forms to Raynet?

Yes, add a separate form mapping for each form in the Forms section. Each form can have its own field mapping and notification settings.

What happens if a contact with the same email already exists in Raynet?

The plugin creates a new lead in Raynet. Raynet CRM handles duplicate detection and merging on its own based on your CRM settings.

Can I use static values instead of form fields?

Yes, for any field mapping you can enter a Custom value instead of selecting a form field. This static value will be sent to Raynet with every form submission.

Does the plugin require WooCommerce?

No, WPify Raynet is a standalone WordPress plugin. It does not require WooCommerce — it works with any WordPress site that uses one of the supported form plugins.