Triggers and forms
Growth tools under Marketing → Triggers capture inbound leads and can start Smart Flows. Each asset embeds on sites or print collateral and creates CRM contacts when submitted.
Video
Who can do this
Marketing or automation permission.
Before you begin
- Landing page or print placement for QR/button
- Optional Smart Flow for new-lead routing
- Appointment types if using calendar links
What you'll accomplish
- Live capture asset deployed
- Test submission creates/updates contact
- Optional automation execution logged
Step-by-step procedure
| Tool | Path | Typical use |
|---|---|---|
| Form Builder | /form-builder-embed-generator | Multi-field lead forms |
| Button Builder | /button-builder | CTA buttons with tracking |
| QR Code Generator | /qr-code-generator | Event or print campaigns |
| Link Shortener | /link-shortener | Tracked short URLs |
| Calendar Links | /triggers/calendar-links | Self-serve booking links |
Deploy a form
- Open Form Builder.
- Add fields mapped to contact columns/custom fields.
- Copy embed code or hosted URL.
- Publish on website.
- Submit test lead; confirm contact in CRM.
Connect automation
- Create Smart Flow triggered on form submit (see Trigger Events).
- Add actions: assign owner, send WA template, create task.
- Activate; re-test submission.
Calendar links
- Calendar Links → create link tied to appointment type.
- Share in email signature or SMS.
- Booking creates calendar event + contact activity.
Extended guidance
UTM-tagged Link Shortener URLs make ad spend visible in Lead Sources reports. QR codes on print should point to mobile-friendly forms—test iOS and Android scans. Deactivate old forms after events to prevent stale leads entering Smart Flows.
Practice scenarios
Deploy a test Form Builder embed, submit twice (new + returning email), confirm Smart Flow branches correctly.
Sandbox validation
Repeat the procedure in a test workspace or with two internal colleagues before customer-facing launches. Document who approved each step (marketing, legal, ops). Screenshot Verify your work outcomes for audit trails. When something fails, capture the URL, role, timestamp, and exact UI label clicked—Support resolves tickets faster with that context. Re-read See also links after your first successful run; adjacent topics often cover edge cases you have not hit yet.
Team rollout checklist
Assign a single owner for this workflow per workspace. Schedule a 30-minute handoff training with screen share. Add the See also links to your internal Notion or wiki. Re-verify after each major product release (labels move occasionally). Pair junior staff with a senior reviewer for the first live execution. Log lessons learned in your team retro—especially permission surprises and integration timeouts.
Keep learning
Bookmark this page and the Product module map. After major releases, re-walk Step-by-step procedure—UI labels move occasionally. Share feedback with your workspace Admin so Help stays aligned with how your team actually works.
Verify your work
- Test contact visible with correct source
- Smart Flow execution success in monitor
- Calendar booking appears on All Events
Tips
Use Link Shortener on paid ads so Reports attribute lead source accurately.
Troubleshooting
| No contact created | Field mapping or required email missing | | Flow silent | Trigger filter excludes test data | | QR scan 404 | Regenerate after domain change |