Fluent Forms Integration

Automate your document signing workflow by connecting Fluent Forms with WPsigner. When a form is submitted, WPsigner automatically creates a document from a template, maps the signer information, and sends it for signature — all without writing any code.

Note

This integration works with both Fluent Forms Free (v5.x+) and Fluent Forms Pro. No additional plugins or add-ons are required.

---

How It Works

The integration uses a feed-based system. Each feed connects one Fluent Form to one WPsigner Template:

Form Submitted → Feed Triggers → Document Created from Template → Email Sent to Signer

Component	Description
Feed	A connection rule that links a form to a template
Template	A pre-configured PDF with signature fields positioned via drag & drop
Signer Mapping	Links form fields (Name, Email) to the document signer
Variable Mapping	Passes extra form data as template variables
Auto-send	Optionally sends the signing email immediately

---

Two Ways to Sign

WPsigner supports two Fluent Forms workflows. Choose based on whether you need a pre-built PDF template or a PDF generated from the form content itself.

Mode	Best for	Requires template?	Requires feed?
Content signing	Applications, registrations, agreements built from form answers	No	No (feed optional)
Template + feed	Fixed PDF contracts (NDA, lease, offer letter)	Yes	Yes

Tip

For most new setups, start with Content signing — add the WPsigner Signing field to your form and publish. No feed required.

---

Content Signing (Recommended)

Generate a signed PDF from the form submission content plus an inline signature. WPsigner builds the PDF automatically — you do not upload a template.

How It Works

Form Submitted → PDF Generated from Answers → Signature Applied → Audit Trail + Certificate

Setup

1. Install Fluent Forms and WPsigner (v3.0.0+)
2. Go to WPsigner → Integrations → Fluent Forms and ensure the integration is enabled
3. Edit your Fluent Form and add:
   • Name field (or first + last name)
   • Email field
   • WPsigner Signing field (Draw / Type / Upload tabs)
4. Publish the form

When a visitor submits the form:

• WPsigner captures the signature and form data
• A signed PDF is generated with audit trail and Certificate of Completion
• The signer receives the completion flow configured in WPsigner

Optional Feed (CC, Custom Title, Template Mode)

Feeds are optional for content signing. Create one only if you need:

• CC emails on the signed document
• A custom document title
• To force template-based signing instead of content PDF

1. WPsigner → Integrations → Fluent Forms → New Feed
2. Select a form that includes a WPsigner Signing field
3. Configure CC emails or title as needed

If the feed is misconfigured, WPsigner falls back to automatic content signing when a Signing field is present.

Submission Validation

If PDF generation fails (for example missing signature data or server error), the form submission is blocked. Fluent Forms will not save a submission without a completed signed document — you will not get orphaned entries.

---

WPsigner Signing Field + OTP

The WPsigner Signing custom field supports one-time password verification before the user submits.

Enable OTP

1. Edit your Fluent Form
2. Click the WPsigner Signing field
3. Set OTP verification to Enabled
4. Choose OTP delivery method:

Method	Requirements
Email	Email field on the form
SMS	Phone field + Twilio configured
Email + SMS	Both email and phone fields
WhatsApp	Phone field + WhatsApp configured

5. Save and publish the form

Signer Experience

1. User fills out the form and draws/types/uploads a signature
2. User clicks submit → OTP modal appears
3. User enters the 6-digit code
4. After verification, the form submits and the signed PDF is created

Submit is blocked until OTP is verified. Phone numbers for SMS/WhatsApp should use valid international format (E.164).

---

Merge Tags in Fluent Forms Emails

Use these merge tags in Fluent Forms confirmation emails or notifications after content signing:

Tag	Output
{inSigner:signed_pdf_url}	Direct URL to download the signed PDF
{inSigner:download_button}	HTML button linking to the signed PDF

Example

In Form → Settings → Email Notifications, add to the message body:

<p>Your signed document is ready:</p>
{inSigner:download_button}

Tags resolve when the signed PDF URL is available (after successful signing).

---

Integration Settings

Global options are under WPsigner → Integrations → Fluent Forms:

• Enable or disable the integration
• View connected forms and feed count
• Create and manage feeds

Ensure Fluent Forms is active before configuring feeds. If the integration page shows “Fluent Forms is not installed”, activate the plugin first.

---

Template + Feed Mode

The steps below describe the classic template workflow — use this when you have a fixed PDF and want to map form fields into signature positions.

---

Prerequisites (Template Mode)

Before setting up template feeds, you need:

1. WPsigner installed and activated (v3.0.0+ recommended)
2. Fluent Forms installed and activated (Free v5.x+ or Pro)
3. At least one Fluent Form created with name and email fields
4. At least one WPsigner Template with signature fields configured

---

Step 1: Create a WPsigner Template

A template is a reusable PDF document with pre-positioned fields (signature, name, email, date, etc.). The template defines where the signer will sign and what information they need to fill in.

Creating a Template from the Document Editor

1. Go to WPsigner → New Document
2. Upload your PDF document (e.g., NDA, contract, service agreement)
3. Add a signer in Step 2 (Signers)
   • Enter any placeholder name and email — these will be replaced by the form data
4. Position your fields in Step 3 (Fields)
   • Drag and drop Signature, Name, Email, Date, or Text fields onto the PDF
   • Position them exactly where you want them to appear
   • Resize fields as needed
5. Go to Step 4 (Review) and click Save as Template
6. Enter a template name (e.g., “NDA Contract”) and optional description
7. Click Save Template

Tip

Take your time positioning the fields accurately. The positions you set here will be used for every document created from this template.

Verifying Your Template

After saving, verify the template was created correctly:

1. Go to WPsigner → Templates
2. You should see your new template listed with the field count
3. You can preview the template to confirm field positions

---

Step 2: Create a Fluent Form

If you don’t already have a form, create one in Fluent Forms:

1. Go to Fluent Forms → New Form
2. Add at minimum:
   • A Name field (Full Name or First + Last Name)
   • An Email field
3. You can add additional fields that will be available for variable mapping (company, phone, address, etc.)
4. Save and Publish the form

Recommended Form Fields

Field	Purpose	Required
Full Name	Maps to document signer name	✅ Yes
Email Address	Maps to signer email for signing link	✅ Yes
Company Name	Can be mapped to template variables	Optional
Phone Number	Can be mapped to template variables	Optional
Address	Can be mapped to template variables	Optional
Custom fields	Any additional data for the document	Optional

---

Step 3: Connect the Integration

Navigate to the Integration Page

1. Go to WPsigner → Integrations in your WordPress admin
2. Locate the Fluent Forms card under WordPress Plugins
3. Click Configure

You’ll see the Fluent Forms Integration page with:

• A status badge showing Connected (if Fluent Forms is active)
• The count of available forms and configured feeds
• A New Feed button

Caution

If you see a warning that “Fluent Forms is not installed”, you need to install and activate Fluent Forms first. Click the Install Fluent Forms button to go to the plugin installer.

Create a New Feed

1. Click the New Feed button
2. A modal window will appear with the following configuration options:

Feed Name

• Give your feed a descriptive name (e.g., “NDA Contract Feed”, “Service Agreement - Signup”)
• This name is shown in the feeds list for easy identification

Fluent Form

• Select the Fluent Form that will trigger this integration from the dropdown
• All active Fluent Forms on your site will be listed

WPsigner Template

• Select the WPsigner template to use when creating documents
• Only templates with configured fields will work correctly

Document Title

• Define the title for each generated document
• You can use dynamic variables that will be replaced with actual data:

Variable	Replaced With	Example
{{signer_name}}	Signer’s full name	John Smith
{{signer_email}}	Signer’s email	john@example.com
{{date}}	Current date	2026-02-07
{{company_name}}	Company name (if mapped)	Acme Corp

Example title: NDA - {{signer_name}} - {{date}} This would generate: “NDA - John Smith - 2026-02-07”

Primary Signer

Map the form fields to the signer information:

• Name Field: Select which Fluent Forms field contains the signer’s name
  • This can be a Full Name field, or a text field where the user enters their name
• Email Field: Select which Fluent Forms field contains the signer’s email
  • The signing link will be sent to this email address

Both the Name and Email fields are required. If either is missing when the form is submitted, the integration will skip the submission silently.

Variable Mapping (Optional)

Map additional form fields to template variables. This allows you to pass extra data from the form into the document:

1. Click Add to add a new mapping row
2. In the left input, enter the variable name (e.g., custom.company, custom.phone)
3. In the right dropdown, select the corresponding Fluent Forms field
4. Repeat for each variable you want to map

Example mappings:

Variable	Form Field	Use Case
custom.company	Company Name	Include company in document
custom.phone	Phone Number	Add phone to document
custom.address	Address	Include address in document
custom.amount	Payment Amount	Add pricing to contract

Auto-send Document

• Enabled ✅ (default): The signer receives an email with the signing link immediately after form submission
• Disabled: The document is created but stays in “Draft” status. You can manually send it later from the WPsigner dashboard

Feed Enabled

• Enabled ✅ (default): The feed is active and will trigger on form submissions
• Disabled: The feed is paused and will not create documents

Save the Feed

Click Save Feed to save the configuration. The page will reload and you’ll see your new feed in the list.

---

Step 4: Test the Integration

1. Open your Fluent Form on the frontend (or use the preview)
2. Fill in the form with test data:
   • Enter your own name and email so you receive the signing email
3. Submit the form
4. Check your email for the signing link (if Auto-send is enabled)
5. Verify in WPsigner:
   • Go to WPsigner → Documents
   • You should see a new document with the title you configured
   • Open the document to verify:
     • The signer’s name and email are correct
     • The fields (signature, name, email, date) are positioned correctly on the PDF
6. Complete the signing to verify the full end-to-end flow

---

Managing Feeds

Edit a Feed

1. Go to WPsigner → Integrations → Fluent Forms
2. Click the Edit button on the feed card
3. Modify the settings as needed
4. Click Save Feed

Enable/Disable a Feed

• Click the Enable or Disable button on the feed card to toggle the feed status
• Disabled feeds will not trigger on form submissions

Delete a Feed

1. Click the Delete button (trash icon) on the feed card
2. Confirm the deletion
3. The feed will be permanently removed

Note

Deleting a feed does not affect documents that were already created. Only future form submissions will stop creating documents.

---

Use Cases

Scenario	Setup
Client onboarding	Contact form → NDA template → Auto-send
Quote requests	Quote form → Service agreement template
Job applications	Application form → Offer letter template
Event registration	Registration form → Waiver template → Auto-send
Lead capture	Lead form → Follow-up contract template
Rental agreements	Booking form → Rental agreement template → Auto-send
Service agreements	Order form → Service contract template

---

Multiple Feeds

You can create multiple feeds for the same form or template:

• One form, multiple templates: Submit one form and generate different documents based on different templates
• Multiple forms, one template: Different forms can all use the same document template with different signer data
• One-to-one: Each form has its own dedicated template

Each feed operates independently. When a form is submitted, all active feeds linked to that form will trigger.

---

Confirmation & Follow-up

After the form is submitted and the document is created, you can customize what the user sees:

In Fluent Forms

1. Go to Form → Settings → Confirmations
2. Set the confirmation type to Message
3. Customize the message:

Thank you! Please check your email for a signing link. You will receive a document to sign shortly.

In WPsigner

Once the signer signs the document:

• They see a completion page with a success message
• A signed copy is stored in WPsigner
• The document status updates to Completed

---

Troubleshooting

Common Issues

Issue	Cause	Solution
No document created after form submission	Feed not active	Check feed is enabled
No document created	Form or template not selected	Verify feed configuration
Signer not receiving email	Auto-send not enabled	Enable “Auto-send document” in the feed
Signer not receiving email	SMTP issue	Check your WordPress email configuration
Fields not appearing on signed PDF	Template has no fields	Re-create the template with fields positioned correctly
Wrong signer name/email	Field mapping incorrect	Edit the feed and check the Primary Signer mapping
”Fluent Forms is not installed” warning	Plugin not active	Install and activate Fluent Forms
Form submission blocked / validation error	Content signing PDF failed	Check signature field, OTP, and debug log — submission is intentionally blocked on failure
OTP not sending	Channel misconfigured	Verify Twilio/WhatsApp for SMS; email field for email OTP
Merge tags empty in email	Tags used before PDF ready	Use in post-submission notifications, not pre-submit messages

Checking Error Logs

If documents are not being created, check the WordPress debug log:

1. Enable debug logging in wp-config.php:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);

2. Check the log file at wp-content/debug.log
3. Look for entries starting with WPS or FluentForms

Rate Limiting

The integration has a built-in rate limit of 10 documents per minute per form to prevent abuse. If you’re testing rapidly, wait a minute between submissions.

---

Compatibility

Component	Supported Versions
Fluent Forms Free	v5.0+ ✅
Fluent Forms Pro	All versions ✅
WPsigner	v3.0.0+ (content signing, OTP, merge tags)
WordPress	5.8+
PHP	7.4+

Note

The integration uses the fluentform/submission_inserted hook, which is available in both the Free and Pro versions of Fluent Forms. No Pro-only features are required.

---

Next Steps

• Smart Signing Forms — Standalone signing forms without Fluent Forms
• Templates — Learn more about creating and managing templates
• Document Workflow — Understanding document statuses and actions
• REST API — For advanced programmatic integrations
• WhatsApp Integration — Send signing links via WhatsApp