Venom Forms
Build forms in Venom Cloud with a Tally-style builder, conditional logic and a live preview. Publish a link, and let agents build, change and publish them too.
Venom Forms is the form builder inside Venom Cloud, at /forms. You build a form out of blocks, add logic so people
only see what matters, publish it, and share the link. It is an add-on like Venom Flags: an owner or a billing member
adds it on the billing page. g o opens it from any app, and ⌘K finds forms by title (type forms: to search only
forms).
This page covers building. Agents do the same work over the MCP server; see logic and outlines for the rules and the outline format they and the "New form" dialog share.
The forms list
The list shows each form's status (draft, published, closed), questions, responses and completion rate. Press c for a
new form, / to search. A new form starts from:
- a template: feedback (a rating, and a follow-up only when it is low), bug report, sign-up, NPS survey, job application, or blank;
- a pasted outline: one question per line, as described in logic and outlines;
- Draft with AI: describe the form in a sentence. Your organisation's own gear drafts the questions and logic, under the organisation's daily AI limit (the one the AI actions in Notes use). You edit the result; nothing is published.
The builder
A form opens at /forms/{id}; ?tab=share, ?tab=responses, ?tab=connect and ?tab=settings open its other tabs.
Blocks are on the left, a live preview is in the middle, and the selected block's settings, logic and design are on the right. On a phone the three are tabs.
- Blocks. Short and long text, email, phone, website, number, multiple choice, checkboxes, dropdown, yes/no,
ranking, rating, opinion scale, net promoter score, date, file upload, statement and hidden field. Press
/, type to filter, press Enter. Drag a block to move it, or use the keyboard. - Edit in place. Click a question in the preview and type: the title, description and each choice are fields.
- Block settings. Type, required, placeholder, and the validation that fits the type: length, a pattern, a number range, how many choices, rating steps, file types and size.
- Logic. Rules read as sentences: When "How was it?" is at most 2, then show "What went wrong?". See logic and outlines.
- Design. The accent colour, one question at a time or a classic page, the progress bar and the button text. No web fonts are loaded. The preview has its own switch between the two layouts.
- Share. The form's link (live once published), inline, popup and slider embeds, an iframe and a QR code drawn in your browser. See sharing.
- Responses. A table, filters, CSV export, a summary and drop-off by question. See responses.
- Connect. Send each response to a Notes database, Tasks triage, webhooks or Slack. See destinations.
- Settings. Appearance with a logo, close date, response limit, the thank-you screen or a redirect, the minimum time before a submit is accepted, how long responses are kept, the change history and deleting the form.
Keyboard
| Key | Does |
|---|---|
/ |
add a block after the selected one |
j k or ↓ ↑ |
select the next or previous block |
⌘↑ ⌘↓ |
move the block up or down (works while typing) |
⌘D |
duplicate the block |
Delete |
delete the block (a toast offers Undo) |
b l |
open the block's settings or its logic |
p |
switch the preview between one at a time and a page |
⌘Enter |
publish |
Esc |
leave a field; again, back to the list |
Saving, publishing and agents
Every edit is a small instruction (add this block after that one, change this title) sent under the version the page last saw. If a person or an agent changed the form meanwhile, the page says so and reloads it instead of overwriting. Publish snapshots the form: the public link serves that version until you publish again, so you can keep editing a live form. Responses record the version they answered. Close form stops taking responses.
Settings → History lists every change, by people and by agents ("via agent …"), each with a Revert that puts the form back as it was before that change.