WordPress to Zoho Sign Integration

Supported form plugins and Zoho apps

FormBridge for Zoho connects these WordPress form plugins with your Zoho apps. This guide covers the Zoho Sign destination.

Before you start

• FormBridge for Zoho Pro is installed and your licence is active.
• Your WordPress form is published and its trigger is set up in FormBridge for Zoho.
• Your Zoho account is authorised for Zoho Sign under FormBridge for Zoho → Connections. If it isn’t, follow the guide to creating a Zoho connection.
• The template exists in Zoho Sign, with its recipients and signing order already set, and your form collects a name and an email address for every signer.

How to set up a WordPress to Zoho Sign integration

Once your form trigger and feed details are ready, follow these seven steps. Zoho Sign has no Organization dropdown, so the destination panel goes straight from the account to the app and then the template.

1. Step 1: Select your account

   Destination › Account

   On the Destination step, open the Account dropdown and choose the Zoho account you authorised under FormBridge for Zoho → Connections. Documents are created in this account.

   No account in the list?

   Use Connect account at the top of the panel, or create the connection first and return to the feed. Learn how to create a Zoho connection.

   

2. Step 2: Select Zoho Sign as the Zoho app

   Destination › Zoho app

   Open the Zoho app dropdown and select Zoho Sign. The dropdown lists every app your account is authorised for.

   Zoho Sign not in the list?

   The connection must include Zoho Sign. Open FormBridge for Zoho → Connections, choose Edit access for the account, tick Zoho Sign and reauthorise. Zoho grants only the permissions asked for when a connection is made.

   

3. Step 3: Select the template and what it should do

   Destination › Module

   From the Module dropdown, choose the Zoho Sign template the document should be built from. Each template is listed twice, once for each action:

   • Template “…”: create a draft (not sent) — builds the document and leaves it as a draft, so you can check it and send it yourself from Zoho Sign.
   • Template “…”: create and send for signature — builds the document and emails the signature request straight away.

   Start with the draft option while you are testing, then switch to send for signature once the mapping is right. Use the reload button beside the dropdown if a template you just built isn’t listed yet.

   

4. Step 4: Set duplicate handling and continue

   Destination › Duplicate handling

   Duplicate handling decides what happens when Zoho already holds a record for the same person. Leave Update the matching Zoho record instead of creating a duplicate clear if every submission should produce its own document, which is usually what you want for signatures.

   Then click Continue to move on to the mapping step.

   

5. Step 5: Map the signer fields

   Mapping › Field mapping

   On the Mapping step, give each Zoho field a form field. Both lists load on their own: the Zoho fields come from the template you chose, and the form fields from your form.

   Every recipient in the template gets its own locked Required rows — Recipient 1: signer name and Recipient 1: signer email, then the same pair for each further recipient. Map a form field to each one, so Zoho Sign knows who to send the document to. A two-signer template needs four values, so the form must collect a name and an email for both people.

   

6. Step 6: Send fixed values and add more rows

   Mapping › Static value

   Click + Add mapping row to fill more of the template’s fields. To send the same value every time, set Source to Static value: the form field column greys out and you type the value in the Static value box instead.

   Two worth setting this way are Document name, which is what the signer sees in their inbox and in Zoho Sign, and Note to recipients, the short message that goes out with the signature request.

   

7. Step 7: Set conditions and create the feed

   Mapping › Conditional logic and Create feed

   Conditional logic lets a feed send a document only for the submissions you want, which matters here because each one emails a real person. Turn on Only send when the conditions below match, then build your rules: conditions inside a group must all match, and a record passes if it matches any one group. While the switch is off the feed sends every record it receives, and any rules you have written are kept but not applied.

   Read the full conditional logic guide →

   When the mapping is ready, click Create feed. The feed starts listening to the selected form straight away, so submit the real form once, using your own email address, to confirm the whole flow.

   

   A test sends a real signature request

   With the module set to create and send for signature, a test creates a document from the template and emails a real request to the mapped addresses. Use your own addresses while testing, or pick the draft option until you are ready.

   Delivery logs

   Every delivery, successful or failed, is recorded under FormBridge for Zoho → Logs. Failed deliveries can be sent again with Resubmit.

Verify the integration

1. Submit the real form using your own name and email address as the signer.
2. Check the log under FormBridge for Zoho → Logs and confirm the delivery succeeded.
3. Find the document in Zoho Sign and check its status: a draft, or out for signature.
4. Check the details: the document name, the note, and every recipient.
5. Open the email you received and make sure the signing link works.

Troubleshooting

Pick the symptom you’re seeing to get the fix.

Still stuck? Email the failed entry from the Logs screen to support@techwavesolutions.net.

Frequently asked questions