Public forms & Email In

Let the outside world file records: shareable forms with conditional questions, and email addresses that turn messages into records. Create a form Open a table's field editor and press Forms. A new form starts with every fillable field included — untick what you don't want, drag ⠿ to reorder, mark answers required, and override labels or add help text per field. The share link (/f/…) works for anyone, no account needed; submissions become records instantly. Ask only what's relevant Any field can be conditional: only ask this when an earlier Select, Multi-select, or Yes/No answer matches — "which browser?" only when Type is Bug. Conditions are enforced on the server too: a hidden question can't block submission and its answer is discarded if a clever visitor forces one in. Submissions are first-class records Auto number fields stamp themselves (instant ticket numbers), automations fire (email the team, set a status), and the record-name mapping decides what shows in the grid. Optionally email every submission somewhere with Email each submission to. Forms are protected by rate limiting and a bot trap; Relation fields are deliberately not offered — a public picker would expose your records' names. Email In: an address that files records for you Any table can have its own email address. On the table's Email In page, create a mailbox and RowFold hands you a ready-made address like t-…@in.rowfold.com — there is nothing to set up on your side: no DNS, no mail server, no forwarding rules required to make the address work. It receives mail the moment it exists. A new mailbox already works: the sender goes into your first Email field, the message into your first Long text field, and files into your first Attachment field. The subject always names the record. Auto numbers stamp themselves and automations fire exactly as if the record were typed in. The classic move: forward your real support address (support@yourcompany.com) at the RowFold address, and your support queue lives in a table — numbered, filterable, automated, with AI triage one question away. Choosing what lands where The mapping list is the heart of the page: each row is one source and one field, and you can add as many as you like. The sources are the parts of an email — Subject, Message (quoted reply chains, "On … wrote:" trails and signature blocks stripped so the record holds just what was said) or Message with quoted history, the sender's email, name or domain, Sent to, Cc, the received date, any named email header (for senders that put order ids and references there), and attached files. Two do more than copy text. A fixed value writes the same thing on every message — "Source = Email", "Priority = Normal" — so a mailbox can feed a queue that already has conventions. And Match sender to a record links the email to the contact, company or customer it belongs to: pick a Relation field, say which field on the other table holds their address, and RowFold links the matching record — creating it if they're new, so every email quietly builds your contact list. Some fields can't take a value from email, and the picker says so instead of letting you find out later: anything RowFold works out itself (Auto number, Formula, Lookup, Rollup), a Doc, which is written on its own page, and any field a lifecycle or approval policy governs — those decide their own value, and an email must not talk past them. A saved mapping is checked again every time mail arrives, so if a field is later retyped the mapping stops running and the page tells you why rather than writing something wrong. The panel at the bottom shows what the last email you received actually contained, so you can pick sources against real values rather than guessing. Find your table's address Admins find a table's address under Fields & setup in the table's header: the Email In row shows the address when the table has one, and opens the setup page when it doesn't. The empty state of a new table shows the address to everyone, so "how do records get in here?" answers itself. Admins reach the full editor from that row (the Forms page links across to it too): change the mapping, choose who is alerted when mail arrives, pause an address, or create several mailboxes for one table. Tips • The record-name mapping defaults to your first Text or Email field - set it explicitly for tidy grids. • Pause a form or mailbox any time; the link/address stops working but nothing is deleted. • Email In addresses are RowFold-provided and work instantly — you never touch DNS or mail settings. • Pair a mailbox with a RecordCreated automation (email, Slack, SMS) and every inbound message announces itself. • Map the sender to a Relation field with "create if new" and your contacts table fills itself in as people write to you. Good to know • A reply threads onto the ticket it came from — see Running support for what happens when a mail client strips the reply address. • The subject names the record, which normally means it lands in the table's first field. If that field is an Auto number (or anything else RowFold works out itself) the subject has nowhere to go — map Subject to a field of its own, and the Email In page will warn you. • Emailed files are always kept on the conversation. Mapping an Attachment field also puts them on the record itself. • A mapping stops running if its field is later retyped or adopted by a lifecycle. It stays listed and says why, rather than silently writing the wrong thing.