Techwave Form Sync for Zoho

Techwave Form Sync for Zoho links the forms you already have to the Zoho apps you already use. When a visitor submits a form, the values you mapped are sent to the Zoho service configured for that form and a record is created in your Zoho account.

Each form is configured on its own, in one place. One form can create a lead in Zoho CRM, another a contact in Bigin, another a customer in Zoho Books, another a ticket in Zoho Desk, and another can subscribe someone to a Zoho Campaigns or Marketing Automation mailing list — with different forms pointing at different Zoho accounts, organizations and data centers if that is what you need.

What it covers

• Ten form plugins, one mapping screen. Elementor Pro Forms, Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Fluent Forms, Formidable Forms, Forminator, Happy Forms and SureForms — all configured in the WordPress admin, not inside each form plugin’s own editor, so a site running two form plugins still has one place to look.
• Six Zoho apps, not just CRM. Zoho CRM, Zoho Bigin, Zoho Books, Zoho Desk, Zoho Campaigns and Zoho Marketing Automation.
• Per-form feeds. A “feed” is one form → one Zoho destination. A form can be pointed anywhere, cloned, disabled, or switched to another account without touching the form itself.
• More than one Zoho account. Connect several accounts, each with its own data center and its own set of authorized apps, and pick per feed which one to use.
• Every Zoho data center. US (.com), EU (.eu), India (.in), Australia (.com.au), Japan (.jp), Canada (.ca), Saudi Arabia (.sa) and China (.com.cn). Endpoints switch automatically for the data center each account was created in.
• Field mapping with static values. Map each Zoho field to a form field or to a fixed value, with a duplicate check (upsert) for Zoho CRM and Zoho Bigin so the same person does not become two records.
• Retries that do not lose submissions. Delivery happens during the submission itself. A first attempt that fails for a transient reason is retried in the background instead of being dropped.
• Delivery logs and one-click resubmit. Every delivery is recorded with its outcome, the exact fields sent, and a link straight to the record in Zoho. Tokens and secrets are redacted.
• Privacy tooling built in. Log entries are covered by WordPress’s own personal-data exporter and eraser, storing submitted values is off by default, and everything the plugin created can be erased when it is deleted.

Disclaimer

Techwave Form Sync for Zoho is an independent third-party plugin developed by Techwave Solutions and is not affiliated with, endorsed by, or sponsored by Zoho Corporation Pvt. Ltd. “Zoho”, “Zoho CRM”, “Bigin”, “Zoho Books”, “Zoho Desk”, “Zoho Campaigns” and “Zoho Marketing Automation” are trademarks of Zoho Corporation Pvt. Ltd. All other product names referenced here — including Elementor, Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Fluent Forms, Formidable Forms, Forminator, Happy Forms and SureForms — are trademarks of their respective owners and are used only to describe which form plugins this plugin can read submissions from. Using Techwave Form Sync for Zoho requires your own Zoho account, which is subject to Zoho’s terms and pricing.

How mapping works

All mapping is done in the WordPress admin under Techwave Sync → Forms, not inside any form plugin’s own editor. You create a feed: pick the form plugin, pick the form by name, then choose the Zoho app, account, organization (where the app needs one) and module, and map each Zoho field to a form field or a static value. To find the exact Zoho API names, open Techwave Sync → Connections and use the Modules & fields button for that account.

External services

This plugin connects to Zoho, a third-party service operated by Zoho Corporation Pvt. Ltd. That connection is required for the plugin to do its job: without it there is nowhere to send a submission. Nothing is sent to Zoho until you connect an account and enable a feed on a specific form.

1. Zoho OAuth (accounts server)

• What is sent: the Client ID and Client Secret you entered from your own Zoho API console, the redirect URI of your site, and the permission scopes for the Zoho apps you ticked when creating the connection. Afterwards, the refresh token belonging to your connection is sent to obtain a short-lived access token.
• When: when you create or re-authorize a connection, and whenever a cached access token has expired and needs refreshing.
• Why: to obtain and renew authorization to write records into your own Zoho account. No password is ever sent or stored — the plugin never sees your Zoho login.
• Where: the accounts host for that connection’s data center, e.g. accounts.zoho.com, or the matching .eu, .in, .com.au, .jp, .ca, .sa, .com.cn host.

2. Zoho application APIs

• What is sent: the form field values you mapped for that feed (and only those — unmapped fields are not sent), plus the module or resource name, the selected account, and the organization/department where the Zoho app requires one. This can include personal data, because form submissions usually do: names, email addresses, phone numbers and message text.
• When: each time a visitor submits a form that has an enabled feed pointing at Zoho, and again on an automatic background retry if the first attempt failed for a temporary reason. Also when you press Resubmit on the Logs screen. Metadata reads (listing modules, fields, mailing lists, tags, departments) happen only while you are configuring a feed in wp-admin.
• Why: to create the record — lead, contact, customer, ticket or list subscription — that the feed is configured to create.
• Where: the API host for the connection’s data center: www.zohoapis.com for CRM, Bigin and Books; desk.zoho.com for Desk; campaigns.zoho.com for Campaigns; marketingautomation.zoho.com for Marketing Automation — each with the regional variant matching the chosen data center.

Zoho’s own terms govern what happens to the data once it arrives:

• Zoho Privacy Policy: https://www.zoho.com/privacy.html
• Zoho Terms of Service: https://www.zoho.com/terms.html

3. Deactivation feedback (optional, opt-in)

When you deactivate Techwave Form Sync for Zoho from the Plugins screen, the plugin asks why. Answering is entirely optional and can be skipped, and the plugin deactivates either way.

• What is sent: the reason you pick from the list, the note you type if you type one, and the plugin’s version number. Nothing else — no site address, no account or email address, no user details, no WordPress/PHP/server information, and no identifier of any kind. There is nothing in the request that says which site it came from.
• When: only when you press Send Feedback & Deactivate. Pressing Skip & Deactivate, closing the dialog, or deactivating with JavaScript disabled sends no request at all. Nothing is sent at any other time.
• Why: so the developer knows which problems make people stop using the plugin. It has no effect on how the plugin works.
• Where: the developer’s own feedback collector at https://feedback.techwavesolutions.net/index.php, operated by Techwave Solutions. Service terms and privacy policy: https://techwavesolutions.net/
• Failures are ignored: if the request fails or the service is unreachable, deactivation still completes and you are never asked to retry.

Site owners who would rather it never ran can switch it off with one line in wp-config.php, which stops the request being made at all:

The filter form2zoho_feedback_endpoint does the same from a plugin or mu-plugin.

Nothing else leaves your site. Apart from the three cases above, the plugin sends no analytics, telemetry, usage statistics, site address, admin email, WordPress/PHP version or installation identifier anywhere. It loads no script, stylesheet, font or image from a remote host, and it downloads no code.

Data stored on your own site

• Delivery logs are written to a table in your own database (timestamp, outcome, Zoho app, module, record id, and the error text when something failed). Submitted values are included only if you switch Store submitted values in the log on; it is off by default. Log entries are deleted automatically after the retention period on the Settings tab (30 days by default).
• Retry data. If a delivery temporarily fails and a retry is scheduled, the submitted values required for the retry may be temporarily stored by WordPress — in a transient on your own site — until the retry is completed or the retry data expires (at most two hours). It is deleted as soon as the retry runs, whether that attempt succeeds or fails for good, and it is never sent anywhere other than Zoho.
• Credentials. Client secrets and refresh tokens are encrypted (AES-256-GCM) before being saved; access tokens are short-lived and cached in transients.

Privacy

Form submissions usually contain personal data, and this plugin’s whole purpose is to transmit the mapped fields of a submission to Zoho, a third-party service, as described under External services above. Review Zoho’s privacy policy and make sure your own privacy notice covers this transfer.

On your own site, the plugin stores delivery log entries in a custom database table — including the submitted field values when Store submitted values in the log is enabled, which it is not by default — for the configured retention period (30 days by default). A submission waiting on an automatic retry is held in a WordPress transient until the retry runs or that copy expires, at most two hours.

The plugin registers a personal-data exporter and eraser, so log entries mentioning a given email address are included in, and removed by, WordPress’s own Tools → Export/Erase Personal Data flows. Suggested privacy-policy text is added to Settings → Privacy.

Access tokens, refresh tokens, client secrets and authorization headers are never written to the logs in readable form.

The optional deactivation feedback described under External services carries no personal data and nothing that identifies your site — only the reason you pick, the note you choose to type, and the plugin version — and it is sent only if you press the send button.