Disclaimer<\/strong><\/p>\n\nFormBridge 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 FormBridge for Zoho requires your own Zoho account, which is subject to Zoho's terms and pricing.<\/p>\n\n
How mapping works<\/strong><\/p>\n\nAll mapping is done in the WordPress admin under FormBridge \u2192 All Feeds<\/strong>, 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 FormBridge \u2192 Connections<\/strong> and use the Modules & fields<\/strong> button for that account.<\/p>\n\nExternal services<\/h3>\n\n
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.<\/p>\n\n
1. Zoho OAuth (accounts server)<\/strong><\/p>\n\n\n- What is sent:<\/strong> 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.<\/li>\n
- When:<\/strong> when you create or re-authorize a connection, and whenever a cached access token has expired and needs refreshing.<\/li>\n
- Why:<\/strong> to obtain and renew authorization to write records into your own Zoho account. No password is ever sent or stored, and the plugin never sees your Zoho login.<\/li>\n
- Where:<\/strong> the accounts host for that connection's data center, e.g.
accounts.zoho.com<\/code>, or the matching .eu<\/code>, .in<\/code>, .com.au<\/code>, .jp<\/code>, .ca<\/code>, .sa<\/code>, .com.cn<\/code> host.<\/li>\n<\/ul>\n\n2. Zoho application APIs<\/strong><\/p>\n\n\n- What is sent:<\/strong> 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.<\/li>\n
- When:<\/strong> 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<\/strong> on the Logs screen. Metadata reads (listing modules, fields, mailing lists, tags, departments) happen only while you are configuring a feed in wp-admin.<\/li>\n
- Why:<\/strong> to create the record (lead, contact, customer, ticket or list subscription) that the feed is configured to create.<\/li>\n
- Where:<\/strong> the API host for the connection's data center:
www.zohoapis.com<\/code> for CRM, Bigin and Books; desk.zoho.com<\/code> for Desk; campaigns.zoho.com<\/code> for Campaigns; marketingautomation.zoho.com<\/code> for Marketing Automation, each with the regional variant matching the chosen data center.<\/li>\n<\/ul>\n\nZoho's own terms govern what happens to the data once it arrives:<\/p>\n\n
\n- Zoho Privacy Policy: https:\/\/www.zoho.com\/privacy.html<\/li>\n
- Zoho Terms of Service: https:\/\/www.zoho.com\/terms.html<\/li>\n<\/ul>\n\n
3. Deactivation feedback (optional, opt-in)<\/strong><\/p>\n\nWhen you deactivate FormBridge for Zoho from the Plugins screen, the plugin asks why. Answering is entirely optional and can be skipped, and the plugin deactivates either way.<\/p>\n\n
\n- What is sent:<\/strong> 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.<\/li>\n
- When:<\/strong> only when you press Send Feedback & Deactivate<\/strong>. Pressing Skip & Deactivate<\/strong>, closing the dialog, or deactivating with JavaScript disabled sends no request at all. Nothing is sent at any other time.<\/li>\n
- Why:<\/strong> so the developer knows which problems make people stop using the plugin. It has no effect on how the plugin works.<\/li>\n
- Where:<\/strong> the developer's own feedback collector at
https:\/\/feedback.techwavesolutions.net\/index.php<\/code>, operated by Techwave Solutions. Service terms and privacy policy: https:\/\/techwavesolutions.net\/<\/li>\n- Failures are ignored:<\/strong> if the request fails or the service is unreachable, deactivation still completes and you are never asked to retry.<\/li>\n<\/ul>\n\n
Site owners who would rather it never ran can switch it off with one line in wp-config.php<\/code>, which stops the request being made at all:<\/p>\n\ndefine( 'FORM2ZOHO_FEEDBACK_ENDPOINT', '' );\n<\/code><\/pre>\n\nThe filter form2zoho_feedback_endpoint<\/code> does the same from a plugin or mu-plugin.<\/p>\n\nNothing else leaves your site.<\/strong> 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.<\/p>\n\nData stored on your own site<\/strong><\/p>\n\n\n- Delivery logs<\/strong> 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<\/strong> on; it is off by default. Log entries are kept until you delete them, unless you turn on Delete log entries automatically<\/strong> on the Settings tab (off by default), which removes entries older than the number of days you choose.<\/li>\n
- Retry data.<\/strong> 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.<\/li>\n
- Credentials.<\/strong> Client secrets and refresh tokens are encrypted (AES-256-GCM) before being saved; access tokens are short-lived and cached in transients.<\/li>\n<\/ul>\n\n
Privacy<\/h3>\n\n
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<\/strong> above. Review Zoho's privacy policy and make sure your own privacy notice covers this transfer.<\/p>\n\nOn 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<\/strong> is enabled, which it is not by default) until they are deleted, by hand on the Logs screen or automatically after a set number of days when Delete log entries automatically<\/strong> is turned on (it is off 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.<\/p>\n\nThe 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 \u2192 Export\/Erase Personal Data<\/strong> flows. Suggested privacy-policy text is added to Settings \u2192 Privacy<\/strong>.<\/p>\n\nAccess tokens, refresh tokens, client secrets and authorization headers are never written to the logs in readable form.<\/p>\n\n
The optional deactivation feedback described under External services<\/strong> 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.<\/p>\n\n\n\n- Upload the plugin folder to
\/wp-content\/plugins\/<\/code>, or install the zip from Plugins \u2192 Add New \u2192 Upload Plugin<\/strong>.<\/li>\n- Activate the plugin.<\/li>\n
- In your Zoho API console (https:\/\/api-console.zoho.com), create a Server-based Application<\/strong>. Set the Authorized Redirect URI<\/strong> to the value shown on the plugin's Connections<\/strong> tab.<\/li>\n
- Copy the Client ID and Client Secret.<\/li>\n
- In wp-admin go to FormBridge \u2192 Connections \u2192 Create Connection<\/strong>: pick your data center, paste the Client ID and Secret, and tick the Zoho app(s) this account will actually send to. Then connect and approve access on Zoho's own consent screen.<\/li>\n
- For Elementor: edit your form and, under Form settings \u2192 Additional Options<\/strong>, set a unique Form Name<\/strong>, then save the page. For every other supported plugin the form's own title is used, so no extra setup is needed. Either way, no submit action needs to be added, because the plugin listens for submissions itself.<\/li>\n
- Go to FormBridge \u2192 All Feeds \u2192 Add New Feed<\/strong>. Choose the form plugin, pick the form, choose the Zoho app, account, organization and module, map your fields, and save the feed. New submissions are sent from then on.<\/li>\n<\/ol>\n\n\n
\nWhich form plugins are supported?<\/h3><\/dt>\nElementor Pro Forms, Contact Form 7, WPForms, Gravity Forms, Ninja Forms, Fluent Forms, Formidable Forms, Forminator, Happy Forms and SureForms. Pick one source per feed; you only need the form plugin you actually use.<\/p><\/dd>\n
Which Zoho apps are supported?<\/h3><\/dt>\nZoho CRM, Zoho Bigin, Zoho Books, Zoho Desk, Zoho Campaigns and Zoho Marketing Automation. More Zoho apps come with the optional Pro add-on; see below.<\/p><\/dd>\n
Is there a paid version?<\/h3><\/dt>\nYes, an optional add-on called FormBridge for Zoho Pro. This plugin is complete on its own: every form plugin, Zoho app and feature listed on this page works without the add-on and always will. The add-on adds further triggers (WooCommerce, MemberPress, LearnDash, the booking plugins, Divi, an action hook for your own code, and others), further Zoho apps (FSM, People, Creator, Recruit, Projects, Sheet, Sign, Analytics, Cliq, Inventory, SalesIQ, Flow and ServiceDesk Plus Cloud), conditional logic per feed, and a Webhook destination for a URL that is not Zoho. Those triggers show here as locked tiles so you can see what they are; they are not locked on a site that has the add-on.<\/p><\/dd>\n
Do I need Elementor Pro?<\/h3><\/dt>\nOnly if you want to use Elementor forms as a feed's source. Any of the other supported plugins works without it.<\/p><\/dd>\n
Which permissions does the plugin ask Zoho for?<\/h3><\/dt>\nOnly the ones needed by the app(s) you tick when creating the connection: CRM permissions if you picked CRM, Desk permissions if you picked Desk, and so on. Nothing is pre-selected, and no app you did not pick is requested. You can widen a connection's access later with Edit access<\/strong> on the Connections tab, which re-runs Zoho's consent screen for the updated list.<\/p><\/dd>\nWhich data centers are supported?<\/h3><\/dt>\nAll of them: US, EU, India, Australia, Japan, Canada, Saudi Arabia and China. You choose the data center per connected account and the correct endpoints are used automatically.<\/p><\/dd>\n
Where are my tokens stored?<\/h3><\/dt>\nRefresh tokens and client secrets are encrypted (AES-256-GCM) before being saved in your WordPress database, using a key derived from a per-site secret and your AUTH_KEY<\/code> salt. Access tokens are short-lived and cached as transients. The plugin refuses to save credentials on a server without the OpenSSL extension rather than storing them unencrypted.<\/p><\/dd>\nWhat happens if a request to Zoho fails?<\/h3><\/dt>\nA failure that looks temporary (a network problem, a rate limit, Zoho briefly unavailable) is retried in the background a few times with an increasing delay. A failure that will never succeed on a retry (a rejected value, a bad mapping, a missing required field) is recorded immediately instead. Either way the outcome ends up on the Logs screen, and a form2zoho_submission_failed<\/code> action fires when a submission is given up on.<\/p><\/dd>\nIs form data stored on my site?<\/h3><\/dt>\nOnly if you ask for it. Store submitted values in the log<\/strong> is off by default: log entries then record the submitted field names<\/em> but never their contents. Turning it on stores the values too, which is what makes the Logs screen's one-click Resubmit<\/strong> possible, and means whatever your forms collect, including personal data, is kept in the log table until those entries are deleted, by hand or by Delete log entries automatically<\/strong> (off by default). Separately, a submission awaiting an automatic retry is held briefly in a transient (see External services<\/strong> above). Access tokens, refresh tokens and client secrets are always redacted from logs.<\/p><\/dd>\nMy submission did not reach Zoho. What do I check?<\/h3><\/dt>\nMake sure the form has a name and that a feed points at that exact form (pick it from the dropdown). Then open FormBridge \u2192 Logs<\/strong> and look for the entry. The error text there is the reason Zoho gave.<\/p><\/dd>\nHow do I remove everything the plugin created?<\/h3><\/dt>\nTurn on Erase all plugin data when the plugin is deleted<\/strong> under FormBridge \u2192 Settings<\/strong>, then delete the plugin from the Plugins screen. That drops the log table and removes every option, connection, feed and cached token belonging to this plugin, and nothing else. The setting is off by default so an accidental deactivate-and-reinstall does not destroy your setup. Deactivating alone never deletes anything; it only stops scheduled work.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.0 - 15 October 2026<\/h4>\n\n
The plugin is now called FormBridge for Zoho, and the admin screens have been rebuilt around it. Your feeds, connections, logs and settings are untouched and no reconnection is needed; the menu is now FormBridge<\/strong>, so anywhere older documentation says Techwave Sync, look for FormBridge instead.<\/p>\n\n\n- Renamed throughout the interface, including the deactivation prompt, the personal-data exporter and eraser, and the test email. Zoho Campaigns and Marketing Automation now record \"FormBridge for Zoho\" as the source on new subscribers; subscribers added before this update keep the source they were recorded with.<\/li>\n
- Feeds are now created in a four-step editor<\/strong> \u2014 Trigger, Details, Destination, Mapping \u2014 instead of one long form. The trigger step shows each supported form plugin as a tile with its logo and says so when the plugin behind a tile is not running.<\/li>\n
- New Dashboard screen<\/strong>, and the plugin's navigation has moved into a header bar above every screen.<\/li>\n
- Uploaded files are sent to Zoho<\/strong> from every supported form plugin, into the file field you map them to.<\/li>\n
- Field mapping reworked: the row for a required Zoho field is locked so it cannot be removed, a static value is checked against the kind of Zoho field it fills, \"Combine fields\" lists the fields it uses, duplicate matching only offers fields Zoho marks unique, and the field list loads once with a visible wait instead of being refetched.<\/li>\n
- Logs: entries are now kept until you delete them, with Delete log entries automatically<\/strong> as an opt-in setting (it replaces the old fixed 30-day retention, so logs no longer disappear on their own). The screen reads a page at a time, shows times in the WordPress timezone, and reports plainly when Zoho cannot be reached.<\/li>\n
- Zoho Campaigns and Marketing Automation: every mailing list and topic is read, not just the first page; a contact is added to the chosen list straight away; and commas and colons in submitted values are preserved.<\/li>\n
- Connections: pick the account first and only the apps it is authorised for are offered, a Zoho Books organisation's custom modules and fields are listed, the redirect URI confirms when it is copied, and \"Zoho API console\" links to the right region's console.<\/li>\n
- The plugin's notification emails now go through
wp_mail()<\/code>.<\/li>\n- Sources that need the Pro add-on appear as locked tiles on the trigger step, so you can see what it covers. Nothing is shown as locked on a site that already has it.<\/li>\n
- Added hooks so a companion plugin can extend this one without patching it:
form2zoho_loaded<\/code> for wiring, form2zoho_form_sources<\/code> to teach it another form plugin, form2zoho_feed_editor_fields<\/code>, form2zoho_save_feed<\/code> and form2zoho_build_job<\/code> for per-feed settings, form2zoho_should_deliver_feed<\/code>, form2zoho_job_form_values<\/code> and form2zoho_job_settings<\/code> on the delivery path, form2zoho_submission_succeeded<\/code> alongside the existing failure action, and form2zoho_settings_tabs<\/code> with form2zoho_render_settings_tab<\/code> for the settings screen.<\/li>\n- Tested against WordPress 7.1.<\/li>\n<\/ul>\n\n
1.0.0 - 3 August 2026<\/h4>\n\n
Initial release.<\/p>\n\n
\n- Send form submissions to Zoho CRM, Bigin, Books, Desk, Campaigns and Marketing Automation.<\/li>\n
- Works with Elementor Pro Forms, Contact Form 7, WPForms, Fluent Forms, Forminator, Ninja Forms, Gravity Forms, Formidable Forms, Happy Forms and SureForms.<\/li>\n
- Per-feed field mapping, duplicate-record protection, and organisation\/department targeting where the connected Zoho app needs it.<\/li>\n
- OAuth 2.0 connection with encrypted token storage and automatic refresh, across every Zoho data center. Only the permissions for the app(s) you pick are requested.<\/li>\n
- Instant delivery on submit, with automatic background retries if a first attempt fails for a transient reason. An unreachable or overloaded Zoho gives up after 10 seconds on the front end instead of holding the visitor's page; the filters
form2zoho_api_timeout<\/code> and form2zoho_oauth_timeout<\/code> change those values.<\/li>\n- Live-updating Logs screen with per-entry details, bulk delete, \"Select failed\", and one-click resubmit using each feed's current configuration.<\/li>\n
- Storing submitted values in the log is off by default; delivery logging itself stays on.<\/li>\n
- Optional one-question feedback prompt when the plugin is deactivated. Skippable, sends only the reason, your note and the version number, never blocks deactivation, and can be turned off from
wp-config.php<\/code>.<\/li>\n- Personal-data exporter and eraser, suggested privacy-policy text, and opt-in full data erasure on uninstall.<\/li>\n
- Fully translatable, keyboard accessible, and usable from 320px up.<\/li>\n<\/ul>","raw_excerpt":"Send WordPress form submissions to Zoho CRM, Bigin, Books, Desk, Campaigns and Marketing Automation.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/354090","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=354090"}],"author":[{"embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/kaderoishi"}],"wp:attachment":[{"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=354090"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=354090"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=354090"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=354090"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=354090"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/kea.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=354090"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}