On this page
VGraple CRM's own form builder does not read submissions from Gravity Forms, Formidable, WPForms or Contact Form 7 directly; the working route is Zapier's native support for each plugin (built into three of the four) feeding into VGraple CRM's Create Lead action, or, for a plugin whose own webhook add-on supports custom headers, calling the REST API directly. This walkthrough covers both.
Before you start
- Decide first whether you actually need this. If you are building new forms and have no existing WordPress plugin investment, VGraple CRM's own embeddable form builder skips this entire setup.
- You need an API key either way, generated by the organisation owner, whether Zapier uses it behind the scenes or you paste it directly into a plugin's webhook add-on.
- Confirm which plugin and tier you are on: Gravity Forms and Formidable Forms have Zapier support on their premium tiers; WPForms needs its Zapier addon, available on Pro and above; Contact Form 7 has no official Zapier feature and needs a separate webhook or automation add-on plugin.
Steps: Gravity Forms, Formidable Forms or WPForms via Zapier
- In Zapier, create a new Zap and search for your form plugin (Gravity Forms, Formidable Forms or WPForms). Choose its New Submission (or equivalently named) trigger.
Connect your WordPress site to Zapier, following that plugin's own connection instructions, typically an API key or site key generated inside the plugin's own settings.
Test the trigger by submitting a real test entry on your form, so Zapier can read the field structure and offer it for mapping.
Add VGraple CRM as the action app and choose Create Lead. Connect with an API key if this is your first VGraple CRM Zap.
Map the form's fields to Create Lead's fields, name, phone, email, and an optional pipeline; put any extra form answers you want to keep into the Notes field as free text.
Optionally add a second action, Send Template Message, mapping the form's phone field to the "To" field, so the person who submitted gets an instant WhatsApp acknowledgement.
Test both steps and turn the Zap on.
Steps: Contact Form 7 (no built-in Zapier support)
Install a webhook or automation add-on for Contact Form 7, since it has no native Zapier or webhook feature. Several free and paid options exist in the WordPress plugin directory; pick one that can either connect to Zapier's own "Webhooks by Zapier" trigger, or POST directly with custom headers.
If it connects to Zapier, use Zapier's "Webhooks by Zapier" as your trigger (Catch Hook), pointing your CF7 add-on's outgoing webhook at the URL Zapier generates, then continue with VGraple CRM's Create Lead action exactly as in steps 4 to 7.
If it supports direct HTTP requests with custom headers, skip Zapier entirely: point it at
https://crm.vgraple.co.in/api/v1/leads, method POST, headerAuthorization: Bearer vgk_your_key_here, and a JSON body withname,phone,emailandnotesmapped from your CF7 fields.
What you will see
A form submission creates a new lead in VGraple CRM within moments, visible on your leads pipeline with whatever fields you mapped, and, if you added the second action, an outbound WhatsApp template message appears in the inbox on that person's conversation.
Settings and options
| Setting or field | What it does | Default |
|---|---|---|
| Form plugin trigger | Fires when someone submits the WordPress form | Chosen per plugin in Zapier (or a webhook add-on's own trigger) |
| Create Lead action | Creates the lead in VGraple CRM | Requires at least a name, phone or email mapped |
| Pipeline mapping | Which pipeline the lead lands in | Your default pipeline unless mapped explicitly |
| Send Template Message (optional) | Sends an instant WhatsApp acknowledgement | Not added unless you build it as a second step |
| Direct API route (CF7 or advanced setups) | Skips Zapier using a webhook add-on with custom headers | Requires the add-on to support an Authorization header |
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Submissions do not create leads at all | The Zap (or workflow) was never turned on, or the form plugin's own connection to Zapier expired | Recheck the Zap's on/off state and reconnect the form plugin's account if its own token expired |
| A lead is created but with no phone number | The form itself did not collect a phone number, or the field was not mapped in the action step | Add a phone field to the form if you need WhatsApp follow-up, and confirm the mapping in the Zap |
| Contact Form 7 submissions never reach Zapier | CF7 has no native webhook feature; a required add-on plugin is missing, disabled, or misconfigured | Install and configure a webhook or automation add-on for CF7 specifically, since this is not built into CF7 itself |
| A direct API call from a plugin's webhook add-on returns 401 | The Authorization header is missing, malformed, or the API key was rotated | Recheck the header value against your current key in Settings > API Keys; confirm the add-on actually supports custom headers |
| Every submission lands in the wrong pipeline | No pipeline was mapped in the Create Lead action, so it used your default pipeline | Explicitly map the intended pipeline in the action step |
Example
A clinic's website runs on Gravity Forms for its "Book a Consultation" form. A Zap creates a lead in VGraple CRM's Appointments pipeline the moment someone submits, and a second action sends a WhatsApp confirmation template to the phone number they entered, all without the front desk touching the form plugin.
Once this is working, see Facebook Lead Ads if you also run lead ad campaigns, or VGraple CRM's own form builder if you decide to consolidate onto one embeddable form instead of a separate WordPress plugin.