Module guide
Forms (intake)
Public forms that mint tasks into a target project.
Overview
Tenant-authored intake forms with a public slug. Each submission mints a task in the configured project, using the titleField as the title and the remaining answers as the description.
Highlights
The capabilities worth knowing before you dive in.
- Public slug with an optional auth gate
- Built-in HMAC signature verification on submissions
- Approval state can be wired via the built-in ApprovalState state machine
Important to know
Limits, permissions, and sharp edges to keep in mind.
- Toggle "enabled" off to stop accepting submissions. The public URL returns 404 without deleting history.
- Required fields are enforced before a task is minted; a missing field returns 400.
How to use it
The primary workflow, start to finish.
- Open a project and choose "Intake form" in settings.
- Define the fields and pick the titleField.
- Share the public URL, and every submission becomes a task you can triage.
FAQ
- How do I stop a form accepting submissions without losing the responses?
- Turn the enabled switch off. The public address then returns 404 while every submission already received stays exactly where it is. Deleting the form is a different action and is not required.
- What does a submission actually create?
- One task in the project the form is configured for. The field nominated as the title field becomes the task title, and the remaining answers are written into the description.
- Why was a form submission rejected with a 400?
- A required field was missing. Required fields are enforced before a task is minted, so an incomplete submission is refused rather than creating a task with a gap in it.
Automate this module
Everything on this screen is scriptable. Drive it from the REST API, or let an AI agent run it through the MCP server.
Was this page helpful?