Embed public forms that create CRM records
Build embeddable forms in Setup, map inputs to object fields, and publish a snippet for your site. Visitors submit from your landing page or embed; each successful submission creates a record on the target object without manual data entry.
Embed
Public forms
Hosted link or snippet on your site
1
Object per form
Contacts, Deals, or custom types
0
Manual re-entry
Submissions write directly to CRM
Website traffic becomes records
Embed a form on your site; submissions map to your schema.
Lead capture should not depend on someone copying form replies into the CRM at end of day. Web forms connect your marketing site directly to the workspace model you already use in Operations and Live Views.
Each form targets one object type — Contacts for inbound leads, custom objects for event registrations, or any schema you define. Field order in the builder controls layout in the embed.
Public embed URLs
Published forms get a hosted link and embed snippet. Copy the snippet to landing pages, WordPress, or static sites.
Field mapping to your schema
Map each input to an object field. Help text guides respondents; reorder fields to control the public layout.
Submission log
Review what was received and when. Submissions create records; deleting a form does not remove records already created.
Publish
From form builder to live embed
Create, map fields, customize copy, publish — then paste the snippet on your site.
- Name forms for internal reference in Setup → Web forms
- Select target object before adding inputs
- Publish when mapping and copy are ready
Capture
Lead capture without spreadsheet handoffs
Inbound interest lands as structured records your team can work immediately.
- Contacts, Companies, Deals, or custom objects as targets
- No parallel tracker when submissions write to the CRM
- Live Views and Operations read the same new records
Permissions
Permissions and create access
Forms create records on behalf of the workspace — ensure profiles allow create on the target object.
- Review permission profiles for the objects you expose
- Field-level permissions still apply to created records
- Admins configure forms; members work submissions in Operations
Audit
Submissions and audit trail
The submissions log shows what the public form received and when records were created.
- Open a form to edit fields or review submissions
- Unpublish or update mapping without losing past records
- Trace inbound leads back to the form that captured them
Schema
Fits your schema evolution
Add fields in Setup → Fields and remap forms when your capture needs grow.
- Field order in Setup affects Operations cards and embed layout
- Custom objects work the same as standard CRM objects
- Pair with webhooks when external systems also need the payload
Questions
Short answers before you request access.
- Where do visitors submit the form?
- Published forms have a hosted page and embed option. Paste the snippet on your own site so submissions create records in the same workspace.
- Which objects can a form target?
- Any object in your workspace schema — standard objects like Contacts or custom objects you define in Setup. Each form targets one object type per submission.
- What happens when someone submits?
- A new record is created on the target object with mapped field values. The submission appears in the form’s submissions log with a timestamp.
- Do I need API keys for basic lead capture?
- No. Web forms are configured in Setup → Web forms. Use webhooks or the REST API only when external systems need programmatic access beyond the public form.