Add TradeVulcan workflow events to Notion
Create Notion database items for supported workflow events that need review, notes, or recurring ops visibility. This is a future template candidate and should stay marked as coming soon until the approved TradeVulcan Zapier app exposes the required trigger or 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
- Notion
- Zapier
Trigger
- TradeVulcan: Workflow Event
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 event id | External ID or reference | Map when available. |
| Customer name | Name | Map when available. |
| Phone | Phone | Map when available. |
| Map when available. | ||
| Service type | Service type | Map when available. |
| Workspace or company | Company or workspace | Map when available. |
| Event status | Status | Map when available. |
| Notes | Description or notes | Map when available. |
| Created date/time | Date/time | Map when available. |
Setup instructions
Step-by-step setup.
- 1This template is planned for a future TradeVulcan Zapier app capability: Workflow Event.
- 2Do not build a public Zap for this until the approved Zapier app exposes the required trigger or action.
- 3Document the field mapping and desired contractor outcome now so the template is ready when the app capability is approved.
- 4When supported, connect Notion, map the event fields, test with sample data, and turn the Zap on.
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
Can I use this template today?
Not yet. This workflow needs a future TradeVulcan Zapier trigger or action before it should be published as an active public template.
Would this require Zapier review?
Yes, if it requires a new public trigger, action, authentication scope, or API contract change in the TradeVulcan Zapier app.
