Blueprint

Intake form and survey

A public form that takes submissions without a sign-in, a triage queue for the team behind it, and a change log on every record.

Intake and surveysFor operationsIllustrative until verified
2
objects
2
forms
2
workflows
2
grids
3
screens
15
named operations

tbd "Open in CodeMonster" arrives when the desktop app ships deep links. Until then: copy the prompt, paste it into your agent.

Jump to the starter prompt Request an invite

What it builds

A form anyone can reach without an account: pick a topic, describe the request, leave an email. The submission lands in a real table with tenant handling built in, the Intake Team gets an email, and the request tops the triage grid. A team member takes it, works it, resolves it, and the submitter hears back.

The same shape is a survey. Swap the description field for the questions you want answered; keep the triage queue for the answers you need to act on.

The primitives map

  • Objects — ntk_submissions, ntk_topics. Real tables; topics carry a default owner so triage starts assigned.
  • Forms — Intake, set public, change log on; Triage for owner, status and resolution.
  • Workflows — on submit, email the Intake Team; on resolved, email the submitter.
  • Grids — new submissions, newest first; open by topic.
  • Screens — the public form, the triage queue, the submission detail.
  • Groups — one, Intake Team. The public can submit; only the team can read.

The build, as an op-log

The public flag on the form, not object permissions, is what lets anyone submit; the submissions object stays readable only to the Intake Team. update-form-settings sets that flag and turns the change log on, and publish-solution copies Current to Testing and Production in one shot — the form is live when it lands.

Starter prompt

Build a solution called Public Intake with the prefix ntk for a team that takes requests from the public, creating the group Intake Team first. Objects: Submission (topic, description, contact email, status, owner, resolution) and Topic (name, default owner). Make the Submission form public so anyone can submit without signing in, and turn the change log on. Only the Intake Team may read or edit submissions. Add a workflow that emails the Intake Team on submit and a second that emails the submitter when a request is resolved, a grid of new submissions newest first, and generate the triage screens. Preview the diff before committing.

Name the topics you already triage by. The agent creates them as rows in ntk_topics, and the form’s topic field looks them up.

Screens (placeholders)

Screenshots pending [PLACEHOLDER: screenshots of the built app — public intake form, triage queue, submission detail with change log]

Extend it

  • Add a PDF receipt generated on submit and emailed to the submitter.
  • Add an ExternalService step that posts each submission to your help desk, Zapier, Make or n8n.
  • Add a rulepack that requires a contact email only when the topic is one you follow up on.
Invite only · early access

Bring us something you want built.

CodeMonster is invite only while we work directly with early adopters. Request an invite and we will meet, scope what you want to build, and get you productive. You bring the AI subscription you already pay for.

Request an invite See how it works