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.

Technical details