Forms
Public intake artifact — publish a share link, capture into tables or audit-only.
Forms
Form is Onnie’s intake deliverable artifact: a product-owned capture surface members publish, and public people fill via a stable share link. Use it for leads, requests, and continuous intake — not as a page embed and not as a public canvas write.
Where in the product
Open a form from the Artifacts library. Author and publish from the form panel. Share the public
link (/f/…) with people outside the workspace.
How to use it
- Create a form (UI or ask the agent with
/form). - Prefer table-bound mapping to columns (default teach path), or keep unbound for audit-only capture.
- Map fields; use settings for collect submitter email (on by default).
- Publish when ready — agents can draft unpublished forms; a human confirms first publish.
- Share the public link; review submissions in the panel.
Successful submits can trigger Automations afterward — the submit response does not wait on those rules.
Mental model
| Mode | What happens on submit |
|---|---|
| Table-bound | Submission audit, and usually a new table row for mapped fields |
| Unbound | Submission audit only (no table insert) |
Key distinctions
Pages publish writing. Canvas showcases (and may allow member-host portal actions). Forms own public intake with a stable share link. Do not use a public canvas as a form.
- Forms soft-delete with the workspace trash family (recover while still in trash).
- Multi-table follow-on writes belong to Automations, not a second form binding.
Related
[ Placeholder · shipped UI screenshot ]