WordPress forms
Contact Form 7 Integration
Turn Contact Form 7 submissions into signed agreements
Connect WPsigner to Contact Form 7 so a form submission can start a signing request — with mapped fields and signed PDFs stored on your WordPress site.
Form submit → signing request · field mapping · signed PDF on WordPress
Signatures that start where your leads already are
Keep using Contact Form 7 for intake, then hand off to WPsigner for legally useful e-signatures — without a separate SaaS signing account.
Submit-to-sign triggers
Start a WPsigner signing request when a Contact Form 7 form is submitted successfully.
Field mapping
Pass name, email, and other form values into document fields so signers are not retyping data.
Self-hosted workflow
Forms, documents, and signed PDFs stay on your WordPress stack with WPsigner.
How the Contact Form 7 flow works
Configure the integration once per form — then each qualifying submission can open a signing path.
- 1
Choose the form
Select which Contact Form 7 form should trigger a WPsigner document or template.
- 2
Map form fields
Connect CF7 fields to signer details and document merge fields in WPsigner.
- 3
Send the signing request
On submit, WPsigner creates the request and notifies the signer through your configured channels.
- 4
Store the signed PDF
Completed documents stay on your WordPress site with WPsigner’s audit trail and download options.
Intake forms that finish with a signature
Contact Form 7 is often the first touch. WPsigner closes the loop so quotes, NDAs, waivers, and service agreements follow the same lead without exporting data to a cloud e-sign vendor.
- Trigger signing from successful CF7 submissions
- Reuse existing Contact Form 7 forms and mail tags
- Map lead data into agreement fields automatically
- Keep signed PDFs and evidence on your WordPress server
What you can automate
- Signing request after Contact Form 7 submit
- Form-to-document field mapping
- Signer email and name from form values
- Template selection per form workflow
- Signed PDF retained with WPsigner on WordPress
Built for WordPress intake workflows
Service inquiries
Follow a contact form with a proposal or service agreement ready to sign.
NDAs & confidentiality
Send an NDA as soon as someone requests access or pricing details.
Event & waiver forms
Collect contact details and a liability waiver in one connected flow.
Support & onboarding
Turn support or onboarding forms into policy acknowledgments with signatures.
Frequently asked questions
How does WPsigner integrate with Contact Form 7?
WPsigner connects to Contact Form 7 submissions so a successful form send can create a signing request, map fields into the document, and keep the signed PDF on your WordPress site.
Do I need to rebuild my Contact Form 7 forms?
No. Keep your existing CF7 forms and configure which ones should trigger WPsigner templates and field mapping.
Can form values fill document fields?
Yes. Map Contact Form 7 fields such as name and email into signer details and document fields so agreements start pre-filled.
Where are signed documents stored?
On your WordPress server with WPsigner — self-hosted with your site — not forced into a separate e-signature SaaS vault.
Does this replace Contact Form 7?
No. Contact Form 7 continues to handle the form; WPsigner handles the e-signature step after submit when you enable the integration.
Is a separate cloud signing account required?
No. WPsigner runs on your WordPress site alongside Contact Form 7 — no per-envelope cloud account is required for this WordPress workflow.
Connect Contact Form 7 to e-signatures
Trigger signing requests from form submissions and keep signed PDFs on your self-hosted WordPress site with WPsigner.
Stop paying per envelope
Choose an annual or lifetime license with unlimited documents and no per-envelope fees. Keep control of your data and signing workflows.