Title: Wiwink Connector for Contact Form 7 Author: ricardochicheri26 Published: September 29, 2026 Last modified: September 29, 2026 --- Search plugins ![](https://s.w.org/plugins/geopattern-icon/wiwink-connector-for-contact-form-7. svg) # Wiwink Connector for Contact Form 7 By [ricardochicheri26](https://profiles.wordpress.org/ricardochicheri26/) [Download](https://downloads.wordpress.org/plugin/wiwink-connector-for-contact-form-7.1.0.2.zip) * [Details](https://wordpress.org/plugins/wiwink-connector-for-contact-form-7/#description) * [Reviews](https://wordpress.org/plugins/wiwink-connector-for-contact-form-7/#reviews) * [Installation](https://wordpress.org/plugins/wiwink-connector-for-contact-form-7/#installation) * [Development](https://wordpress.org/plugins/wiwink-connector-for-contact-form-7/#developers) [Support](https://wordpress.org/support/plugin/wiwink-connector-for-contact-form-7/) ## Description Developed by Wiwink. This plugin is not affiliated with or endorsed by the Contact Form 7 project. Connect Contact Form 7 submissions to Wiwink contacts. Configure field mappings for each form, optionally require an acceptance field, and review delivery status in WordPress. The administration interface is currently in Spanish. Requires Contact Form 7, PHP OpenSSL with AES-256-GCM support, and a Wiwink account with API access and contact creation permissions. Wiwink is an external commercial service; account and plan requirements are determined by Wiwink. Features: * Separate configuration for each form, also available inside the Contact Form 7 editor. * Map name, email, phone, company, message, address, city and postal code. * Optional Wiwink form code, source ID and status ID. * Encrypted background queue and the latest 100 delivery records. * Manual retries and confirmation of uncertain results to reduce duplicate contacts. Each valid submission creates a new contact. Existing contacts are not searched or updated. Separate submissions are not deduplicated. File uploads, custom fields and UTM tracking are not supported. #### External service This plugin connects to Wiwink at https://developers.wiwink.com/api/contacts. After an administrator saves an API key and enables a form, selected form fields and configured source/status/form identifiers are sent over HTTPS to the Wiwink account associated with that key. Requests include the API key as a Bearer authentication header. The transfer creates a contact in Wiwink and occurs when the background queue runs, or when an administrator manually processes it. If an acceptance field is configured, submissions are queued only when it is accepted. The “Comprobar conexion” action sends an authenticated GET request to read the first page of contacts. It checks the response format without storing or displaying those contacts. A successful read does not guarantee permission to create contacts. No requests to Wiwink are made merely by installing the plugin. * Service: https://wiwink.com/ * API documentation: https://wiwink.readme.io/reference/create-contact * Terms: https://wiwink.com/condiciones-contratacion * Privacy policy: https://wiwink.com/politica-de-privacidad #### Local data and retention Queued contact data is encrypted with AES-256-GCM using a key derived from the WordPress security salts. Changing those salts prevents decryption of pending data. This encryption does not protect against an administrator with access to both files and the database. The API key is stored in a WordPress option without additional encryption and is never displayed again in HTML. Alternatively, define WWCF7_API_KEY in wp-config. php. Administrators with manage_options permission can configure the integration and manage jobs. Contact payloads are removed after confirmed delivery or manual discard. Scheduled cleanup removes payloads after 7 days and job history after 30 days. Cleanup requires working WP-Cron; backups may retain older data. History does not contain contact names, emails, messages, API keys or response bodies. WordPress privacy export/erasure by email is not integrated; administrators must manage pending entries through the history screen and handle data already transferred in Wiwink. Deactivation stops the scheduled task and retains settings and data. Deletion removes settings, queue and history for the current site. It never deletes contacts from Wiwink. Network activation and network-wide cleanup are not supported; use a single- site installation. ## Installation 1. Install and activate Contact Form 7. 2. Upload the plugin ZIP through Plugins > Add New > Upload Plugin, then activate it. 3. In Wiwink, obtain your key under Preferencias > Marketing Hub > CONFIGURACION API > API key. 4. Open Settings > Wiwink + CF7 > Conexion. Save the key without the Bearer prefix and check the connection. 5. In Formularios, choose a form, map its name field and any additional fields, and enable the connection. Save that form. You can also configure it in the Wiwink tab of the Contact Form 7 editor. 6. Optionally select an acceptance field and Wiwink form/source/status identifiers belonging to your account. 7. Inform visitors about the transfer in your privacy notice. Submit fictional test data and check Historial and your Wiwink account. When updating, replace plugin files without uninstalling to preserve the key, form settings and existing history. ## FAQ ### Does a Contact Form 7 success message confirm delivery to Wiwink? No. The plugin queues the submission before Contact Form 7 sends mail. Check Historial for delivery confirmation. Contact Form 7 email behavior is preserved. If queue storage fails, the submission is aborted with an error. ### How is the queue processed? WP-Cron runs up to three jobs per execution, scheduled every minute. Execution depends on site traffic and a working loopback request. Low-traffic sites should configure a server cron. Administrators can also use Procesar cola ahora. Each API request has a 15-second timeout. ### What happens when a request fails? HTTP 201 confirms creation. HTTP 200 confirms it only when the returned contact includes an ID and matching name and, if supplied, email. Network interruptions, 429, 5xx and unrecognized responses require manual review. There are no automatic retries. Before retrying, verify that the contact was not already created and that the destination account is correct. Manual confirmation clears local contact data without repeating the request. HTTP 400, 401, 403 and 422 require reviewing fields, credentials or permissions. Changing the key or disabling a form blocks pending jobs. A retry uses the original encrypted data; changing field mappings does not change queued data. Discard invalid entries and submit corrected data instead. ### Which versions were checked? The local integration tests use WordPress 7.1, PHP 8.3 and Contact Form 7 6.1.7. Other supported versions should be tested in staging before deployment. Automated checks do not constitute a security certification or WordPress.org approval. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Wiwink Connector for Contact Form 7” is open source software. The following people have contributed to this plugin. Contributors * [ ricardochicheri26 ](https://profiles.wordpress.org/ricardochicheri26/) [Translate “Wiwink Connector for Contact Form 7” into your language.](https://translate.wordpress.org/projects/wp-plugins/wiwink-connector-for-contact-form-7) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/wiwink-connector-for-contact-form-7/), check out the [SVN repository](https://plugins.svn.wordpress.org/wiwink-connector-for-contact-form-7/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/wiwink-connector-for-contact-form-7/) by [RSS](https://plugins.trac.wordpress.org/log/wiwink-connector-for-contact-form-7/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.2 * Rename the plugin and align its directory, main file and text domain with the requested directory slug. * Clarify authorship and independence from the Contact Form 7 project. #### 1.0.1 * Prepare the plugin for directory review with standard English documentation and external service disclosure. * Use prepared SQL identifiers and explicit request validation in administration actions. * Raise the minimum WordPress version to 6.2 for SQL identifier placeholders. #### 1.0.0 * Per-form settings, encrypted queue, delivery history and manual reconciliation. ## Meta * Version **1.0.2** * Last updated **2 days ago** * Active installations **Fewer than 10** * WordPress version ** 6.2 or higher ** * Tested up to **7.1.2** * PHP version ** 7.4 or higher ** * [Advanced View](https://wordpress.org/plugins/wiwink-connector-for-contact-form-7/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/wiwink-connector-for-contact-form-7/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/wiwink-connector-for-contact-form-7/reviews/) ## Contributors * [ ricardochicheri26 ](https://profiles.wordpress.org/ricardochicheri26/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/wiwink-connector-for-contact-form-7/)