Create TradeVulcan leads from Google Forms responses
Create TradeVulcan leads from Google Forms requests, quote forms, inspection requests, or internal intake forms. This inbound lead workflow helps contractors turn outside demand sources into clean TradeVulcan lead records. Use it for forms, paid ads, bookings, emails, phone messages, and webhook sources that need consistent customer details, service context, source attribution, and follow-up notes before a CSR or dispatcher takes action.
Who this is for
- Owners who want visibility
- CSRs and dispatchers who need faster handoffs
- Office managers who track lead source and follow-up
Apps required
- TradeVulcan
- Google Forms
- Zapier
Trigger
- Google Forms: New Form Response
Action
- TradeVulcan: Create Lead
What moves
- Customer identity and contact details
- Service address, requested work, urgency, and latest notes
- Lead source, campaign context, status, and created time
Filter guidance
- Filter by trade, campaign, source, urgency, status, or service area when not every lead belongs in this workflow.
- Use filters before the action step so the destination app only receives useful records.
Field mapping
Suggested fields to map.
Zapier can hide user-specific columns, board fields, pipeline fields, and database properties until you choose the destination workspace. Use this map as the source of truth, then finish the account-specific fields after selecting the exact TradeVulcan destination.
| Source | Destination | Notes |
|---|---|---|
| Name | TradeVulcan customer name | Map when available. |
| Phone | TradeVulcan phone | Map when available. |
| TradeVulcan email | Map when available. | |
| Address | TradeVulcan service address | Map when available. |
| Service requested | TradeVulcan job type | Map when available. |
| Message or form details | TradeVulcan description | Map when available. |
| Lead source app | TradeVulcan source | Map when available. |
| Preferred appointment window | TradeVulcan preferred appointment window | Use plain text if the source does not provide structured dates. |
Setup instructions
Step-by-step setup.
- 1In Zapier, choose Google Forms as the trigger app and select the account, form, inbox, calendar, webhook, or lead source that represents a real customer inquiry.
- 2Choose the trigger event that fires once per new inquiry, not every field edit, notification, or internal comment.
- 3Choose TradeVulcan as the action app, select Create Lead, and connect a scoped TradeVulcan API client for the correct workspace.
- 4Map name, phone, email, service address, requested service, lead source, campaign or page, preferred appointment window, and the full customer message into TradeVulcan lead fields.
- 5Add Zapier Filter steps to block spam, test submissions, duplicate source events, missing phone/email records, and requests outside the service area.
- 6When the source app provides IDs, response IDs, ad IDs, or booking IDs, map them into notes or external reference fields so the office can trace the lead later.
- 7Test with one real-looking sample and confirm the lead appears in TradeVulcan Leads with the right source, contact details, service request, and next-step notes.
- 8Turn on the Zap, review the first few live records with the office owner, and adjust filters before paid traffic or form volume increases.
Common mistakes
- Using the wrong TradeVulcan workspace credentials.
- Mapping phone or address fields into notes only.
- Skipping duplicate checks when the destination app supports lookups.
- Skipping a filter step when only certain lead sources, trades, service areas, or statuses should continue.
- Turning on the Zap before a real sample has been tested.
Testing checklist
- Sample data appears in Zapier.
- Destination record has name, phone, source, service type, status, notes, and date fields.
- The right channel, spreadsheet, board, or CRM pipeline is selected.
- The office owner knows where failures will be reviewed.
FAQ
Which Google Forms submissions should create TradeVulcan leads?
Use the New Form Response trigger only for real customer inquiries. Add filters for spam, test records, non-service-area requests, and forms that do not need CSR follow-up.
How should Google Forms fields map into TradeVulcan?
Map name, phone, email, service address, requested service, source, campaign/page, preferred appointment window, and the full customer message into TradeVulcan lead fields.
How do I prevent duplicate TradeVulcan leads?
Use the Google Forms submission ID, lead ID, or response ID in notes or an external reference field, then add lookup/filter rules for matching phone or email when the source can submit more than once.
