Examples & Use Cases
Recipes for the most common things teams build with Snapi — and who ends up handling each card. Each example lists the fields to create, the workflow setup, and the features that make it work.
Contact page
The classic: a page on your website, submissions on a board, nothing falls through the cracks.
| Field | Type | Options |
|---|---|---|
| Name | Text | Required, show on board card |
| Required | ||
| Message | Textarea | Required |
| Triage | Select (hot / warm / cold) | Internal, show on board card |
- Create a board (the default To Do / In Progress / Done columns work fine to start).
- In the page's Kanban tab, set it as the Default Board — every submission becomes a card automatically.
- Enable Public Page, add your website to Allowed Domains, and paste the embed snippet into your site.
The Triage field never appears to visitors — your team sets it after reading the message, and because it's marked show on board card, the rating is visible at a glance on the board.
Quote / estimate request
Capture enough detail to price the job, and route hot leads to your automation.
| Field | Type | Options |
|---|---|---|
| Company | Text | Required, show on board card |
| Required | ||
| Service | Select | Required, show on board card |
| Budget | Select (ranges) | — |
| Details | Textarea | — |
| Quoted amount | Number | Internal |
On the Single plan or higher, add a post-submit webhook pointing at n8n, Make, or your own endpoint — notify Slack, create a CRM lead, or draft a reply automatically. A pre-submit webhook can also enrich or validate the data before it's stored (for example, rejecting free-mail addresses for B2B quotes).
Job applications
A hiring pipeline where the board columns are your stages.
- Fields: Name, Email, Phone (Tel), Resume (File), Portfolio URL (Text), plus an internal Rating select (1–5) and internal Notes textarea.
- Rename the board columns to match your process: Applied → Phone screen → Interview → Offer → Hired. Drag cards forward as candidates progress.
- Mark Name and Rating as show on board card so screening happens without opening each record.
- File uploads are stored with the record and count toward your plan's storage.
Support / bug intake
Replace "email us and hope" with structured intake your agents can act on.
- Fields: Summary (Text, required), Steps to reproduce (Textarea), Severity (Select: low / medium / high), Screenshot (File), plus an internal Assignee field.
- Auto-place new tickets in a Triage column via the page's Default Board + Default Column.
- Use an API key to let scripts or AI agents read and update tickets programmatically.
- WIP limits on the "In Progress" column keep the team honest about focus.
Event registration
A lightweight RSVP flow with a capped guest list.
- Fields: Name, Email, Ticket type (Radio), Dietary notes (Textarea), Party size (Number).
- Paid plans have no submission quota to watch; Free allows 1,000 submissions/month (see Plans & limits).
- Export or process registrations via the REST API, or push each one to a spreadsheet with a post-submit webhook.
Internal request desk (no public site needed)
Pages don't have to be public. Keep the Public Page toggle off and your team creates records directly inside Snapi — IT requests, purchase approvals, content briefs — with the same board workflow, comments, file attachments, and audit log on every record.