Module guide
Forms (intake)
Public forms that mint tasks into a target project.
Overview
Intake forms with a public address at /f/ followed by the form slug. Each submission creates a task in the destination project, using the title field as the task title and writing the other answers into the description.
Highlights
The capabilities worth knowing before you dive in.
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 Forms and choose New form.
- Choose the destination project, define the fields, and mark one field as the title field.
- Copy the public address and share it, and every submission becomes a task you can triage.
FAQ
- How do I stop a form accepting submissions without losing the responses?
- Choose Disable on the form. 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, with the status to do and no priority, created in the name of the form owner. 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, or the title field was empty. Required fields are enforced before a task is created, 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?