Fronty documentation
Connected services, code export, and ownership
Distinguish customer-configured connections from Fronty's internal infrastructure, export the site, and verify what remains functional elsewhere.
Last verified
Availability
LimitedDomains, business-email DNS, forms, maps/media components and code export exist. A general webhook, Zapier, Make or CRM integration catalog was not found.
- Plans
- Export is available on eligible paid plans; each connected service has its own terms and costs.
- Roles
- Owner or administrator for connections and export; some editor-level components may be configurable by editors.
- Before you start
- A website you own, authorization for each external account, and a safe place to test exported files.
On this page
Separate user connections from platform dependencies #
| Connection | What you configure | How to verify |
|---|---|---|
| Custom domain | Public DNS records at your registrar | DNS response, HTTPS and canonical hostname |
| Business email | Provider MX, SPF, DKIM and DMARC records | Public DNS plus send/receive tests |
| Forms | Fields, destination table/inbox and optional notifications | A published submission at the authoritative destination |
| Page components | Map, video, chart, calendar, checkout or other component-specific inputs | The public component loads and remains usable under the site's security policy |
| Code export | Download and move the generated files | Serve the archive independently and test the primary path |
Paddle, object storage, email delivery and internal AI providers are platform dependencies, not integrations a customer connects to their own account unless the dashboard explicitly presents such a connection flow.
Connect and disconnect safely #
- Record the owner, purpose and data shared with the external service.
- Use the smallest permission available and never paste credentials into page content.
- Complete the connection, then verify its public result and failure state.
- Document how to rotate or revoke access and what visitors see during an outage.
- Before disconnecting, identify pages, forms or data flows that depend on it.
No general customer-facing webhooks, Zapier, Make or CRM connection path was found in the current product code. Do not promise those integrations until a user can connect, authorize, test and disconnect them from the product.
Configure Visitor AI as a bounded site assistant #
Visitor AI can be configured around support, sales, lead collection, bookings, frequently asked questions or onboarding. Give it only approved knowledge, a clear contact destination and an explicit handoff path for requests it should not answer.
Conversation history is retained for 90 days and the product does not retain raw visitor IP addresses in those transcripts. Availability still depends on the configured AI provider, rate and budget controls. Content configuration may also rely on Fronty's managed object storage, so verify the assistant after any storage, account or hosting change.
Export and test the site #
Export produces page HTML plus the Fronty component assets required by the generated pages. Treat claims about live data and forms separately from the visual archive: those features can still call Fronty public services and are not the same as moving the underlying database or submission system to your new host.
The current export is limited to 200 non-deleted pages, writes English as the document language, and can retain CDN dependencies for component CSS, JavaScript and icons. It does not include a private token for reading dynamic database data. Treat it as a portable generated-site archive with documented dependencies, not as a guaranteed offline or fully self-contained application bundle.
- Export from the website controls available to an eligible plan and role.
- Unpack the archive into an empty directory and serve it over HTTP; do not
judge it only by opening
index.htmlfrom the filesystem. - Check every page, asset path, navigation link, responsive breakpoint and CSP-sensitive component.
- Submit any form and load dynamic content. Record which requests still use Fronty endpoints and whether the destination remains under your account.
- Move DNS only after the independently hosted copy passes the same release checklist.
Know what you own and what remains connected #
You can take the generated website files. Private account credentials, write tokens and platform secrets must never be included. A static export is not an automatic export of account users, billing, database administration, submission history or managed domain infrastructure.