Create Service Fusion customers from new TradeVulcan leads
Create a Service Fusion customer from each TradeVulcan lead so the office can keep intake and dispatch records aligned. Use this when your CSR, dispatcher, office manager, or owner needs every new TradeVulcan lead to show up in Service Fusion without manual copying.
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
- Service Fusion
- Zapier
Trigger
- TradeVulcan: New Lead
Action
- Service Fusion: Create Customer
Field mapping
Suggested fields to map.
| Source | Destination | Notes |
|---|---|---|
| TradeVulcan lead id | External ID | Use this to prevent duplicates when the destination app supports it. |
| Customer name | Name or contact name | Map when available. |
| Phone | Phone | Map when available. |
| Map when available. | ||
| Service address | Address | Map when available. |
| Service type or job type | Service, job type, or request type | Map when available. |
| Lead source | Source | Map when available. |
| Campaign or source page | Campaign, form, or UTM field | Map when available. |
| Lead status | Status or stage | Map when available. |
| Notes or latest message | Description, comments, or notes | Map when available. |
| Created date/time | Created date/time | Map when available. |
Setup instructions
Step-by-step setup.
- 1In Zapier, choose TradeVulcan as the trigger app.
- 2Select the new lead trigger and connect your TradeVulcan API client.
- 3Pull in a recent sample lead from the right workspace.
- 4Choose Service Fusion as the action app.
- 5Map customer name, phone, email, address, service type, source, status, notes, and created date/time.
- 6Add a filter if the workflow should only run for certain trades, sources, statuses, campaigns, or job values.
- 7Test the action and confirm the record appears in Service Fusion.
- 8Turn on the Zap and assign an owner to monitor the first week of runs.
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.
- 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
What TradeVulcan lead fields should I send to Service Fusion?
Map customer name, phone, email, service address, service type, source, campaign, lead status, notes, and created date/time so the destination record has enough context for follow-up.
Which Service Fusion destination record should this Zap update?
Use the Service Fusion workspace, channel, sheet, board, list, or pipeline that the office already checks for new lead work. Add a Zapier filter when only certain trades, sources, or job values belong there.
How should I test the Create Customer action?
Send one recent TradeVulcan lead through the Zap, confirm the destination record appears in Service Fusion, and verify phone, source, service type, owner, status, and notes with the team member who will act on it.
