Embed Public Forms
Embed Agiled forms on another website and control theme behavior.
Public forms can be shared as standalone links or embedded on another website. Embedded forms use a minimal layout so they fit inside the host page.
Use embeds when visitors should complete the form without leaving your website or landing page.
Use the direct public link when you need the simplest sharing path, such as an email, QR code, proposal, or support message. Use an embed when the website page itself should own the visitor experience.
Embed Options
Public form links support options for:
- Embedded display
- Theme mode
- Brand color
Use these options when the form needs to match a public website or landing page.
Keep the direct public form link available for testing and support. It helps separate Agiled form issues from website embed issues.
Decide whether the embedded form should inherit the website feel or use the workspace brand color. Consistent visual treatment helps visitors trust the form as part of the page instead of a disconnected iframe.
Coordinate With the Website Owner
Give the website owner the current embed code, direct fallback link, expected form height behavior, and the success or redirect behavior. This makes it easier to troubleshoot whether a problem is in Agiled or the host page.
Embed Behavior
Embedded forms can notify the parent page when the form is ready, resized, or submitted. This helps the host page adjust iframe height and respond after a submission.
The host website still controls surrounding layout, spacing, scripts, cookie banners, and page performance. If the form appears cramped or cut off, adjust the host page container and embed height handling.
If the host site uses a strict content security policy, cookie banner, script optimizer, or page builder, test the embed after publishing because those tools can alter iframe or script behavior.
Test the Embed
After embedding:
- Load the host page.
- Confirm the form height is correct.
- Submit a test response.
- Confirm the submission appears in Agiled.
- Confirm the host page handles the submitted state correctly.
Test on desktop and mobile. Then open the created submission or CRM record to confirm mappings, notifications, redirects, and workflows worked.
Test from the final published page, not only from the website builder preview. Some builders, cache layers, and script optimizers behave differently after the page is published.
If The Embed Fails
Test the direct public form link. If the direct link works, review the website embed code, cache, content security policy, script stripping, and theme/layout constraints.
If both the direct link and embed fail, check form active status, required fields, redirects, submission actions, and public-domain configuration before editing website code.
If the form submits but the host page does not resize or show the expected confirmation, review the parent page embed script and iframe container. The submission may have reached Agiled even if the website did not react cleanly.
Embed Launch Checklist
Before adding the form to a production page:
- confirm the form is active
- submit a test response from the embedded page
- test mobile width and long field labels
- check the success message or redirect
- confirm mapped CRM records and workflows run
- keep the direct link available for support
After launch, review the first real submission. Confirm the source page, contact mapping, notification recipients, and workflow output before sending traffic to the page at scale.