Add new TradeVulcan leads to Notion
Create a Notion database item for each new TradeVulcan lead when your team runs pipeline notes or ops reviews in Notion. This contractor lead automation is built for CSRs, dispatchers, sales reps, office managers, and owners who need clean lead routing without manual copy and paste. It keeps the customer name, phone, email, service address, requested job type, source, status, notes, and created time moving from TradeVulcan into Notion, where the next action can be assigned, tracked, reported, and followed up quickly.
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
- Notion
- Zapier
Trigger
- TradeVulcan: New Lead
Action
- Notion: Create Database Item
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 Notion destination.
| 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 so the workflow starts from the same lead record your team already sees in TradeVulcan.
- 2Select the New Lead trigger, connect a scoped TradeVulcan API client, and choose the workspace that owns the leads you want to route.
- 3Pull in a recent sample lead and check that the sample includes customer name, phone, email, service address, job type, source, status, notes, and created time.
- 4Choose Notion as the action app and pick the workspace, channel, sheet, board, list, pipeline, or database your team checks every day.
- 5Map the customer, contact, service, source, status, notes, and created date fields into clear destination fields instead of dropping everything into one notes box.
- 6Add a Zapier Filter step when only certain trades, campaigns, job types, urgency levels, sources, or lead statuses should continue into this workflow.
- 7Test the action with one real-looking lead and confirm the record appears in Notion with the right owner, location, source, service type, and follow-up context.
- 8Turn on the Zap, name an internal owner for failed task review, and check the first week of Zapier task history before treating the workflow as fully launched.
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
What TradeVulcan lead fields should I send to Notion?
Map customer name, phone, email, service address, service type, source, campaign, lead status, notes, and created date/time so the board item has enough context for follow-up.
Which Notion board item should this Zap update?
Use the Notion 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 Database Item action?
Send one recent TradeVulcan lead through the Zap, confirm the board item appears in Notion, and verify phone, source, service type, owner, status, and notes with the team member who will act on it.
