Forms That Become Work, Not Just Emails
Publish web forms that feed directly into your business database without custom backend plumbing.
Three kinds of form: collect new records, send one record out to be corrected, or send a document out to be signed. All without giving anyone a login.
Why this matters
Most form tools only do intake. The moment you need something back from a customer, a supplier, or a contractor, whether that is a corrected address or a signed contract, you leave the system and start emailing attachments around.
InfoLobby web forms are tied to your tables. A create form takes new submissions from the public. An edit form opens one existing record so someone outside your team can correct it. A signature form sends a document out to be signed. Everything that comes back is a record your team can review, route, and automate.
A form is a door, and it swings both ways.
Intake is the obvious half. The other half is sending a single record back out: asking a customer to confirm their own details, a supplier to fill in a price, a client to sign the quote. Same tables, same automations, no login for the person on the other end.
- Map submissions directly into your tables
- Send one record out with a private, revocable link
- Trigger follow-up as soon as something comes back
What changes for the team
- Forms connect straight to your tables
- Submissions can trigger workflows instantly
- Use forms for leads, requests, applications, or orders
- Send one record out for someone outside your team to correct
- Send a document out to be signed, and keep the signature on the record
- Keep customer input and internal processing in one system
Feature details
- Map public inputs into structured records
- Use the same data downstream for tasks, comments, and automations
- Embed on your website instead of sending users elsewhere
- Share a single record for editing, with per-field read-only control
- Collect a legally binding electronic signature on a document
- Password protect a form, and revoke a shared link at any time
- Give a table its own email address so messages become records too
- Track form-created changes in activity history
- Block bot spam with an optional CAPTCHA challenge
How teams usually start
- Create the target table first so every form field maps to useful business data.
- Publish a create form for lead capture, requests, applications, orders, or structured intake.
- Add an edit or signature form when you need something back on a record that already exists.
- Trigger notifications, routing, or follow-up tasks as soon as submissions become records.
FAQ
Do web form submissions go straight into the database?
Yes. Each submission creates records in the target table so your team can act on them right away.
Can form submissions trigger automations?
Yes. Once a submission lands as a record, it can trigger the same workflows as any other record event.
Can someone outside my team update an existing record?
Yes. An edit form opens one specific record through a private link, with each field set to editable or read-only. Send the link yourself or have an automation email it, and revoke it later if you need to.
Can I get a document signed through a form?
Yes. A signature form shows the document, collects a legally binding electronic signature, and records who signed, when, and exactly what the document said at that moment. See electronic signatures for the detail.
How do I stop bots from spamming my form?
Enable the optional CAPTCHA on the form. Submitters solve a quick image challenge that is verified on our servers, so automated submissions are rejected.
Do all three kinds count toward my plan limit?
Yes. Create, edit, and signature forms all draw on the same web form allowance, so a table with an intake form and a signing form is using two.
Can people create records by email instead of a form?
Yes. Each table can have its own email address, and messages sent to it become new records, with the sender, subject, body, and attachments mapped to fields you choose. If it ever attracts spam, reset the address to issue a fresh one.
Want this feature in a system your team can actually run?
Start with the workflow this feature supports, then add the records, views, tasks, comments, and automations around it.