Settings

Configure global settings, marketplace, integrations, mail, cache, captcha, storage, and security.

In LeadFlow AI, this area is part of the buyer's operational workflow: build a lead capture asset, publish it safely, collect qualified lead records, route those records to the correct owner, and review performance before changing traffic or sales processes. Treat every setting here as production-facing when the item is connected to a live form, funnel, survey, QR link, embedded page, automation, custom domain, file, or paid SaaS plan.

Main Features Overview

Connect LeadFlow AI to email marketing, CRM, webhook, analytics, captcha, storage, and payment providers.
Map form fields to external fields with validation and fallback handling.
Store provider credentials centrally and restrict access to trusted admins.
Review logs after every credential, field mapping, or endpoint change.

When to Use This Feature

Use Settings when the team needs a controlled way to manage this part of lead generation instead of handling it through spreadsheets, disconnected forms, or manual email threads. It is especially useful when agencies manage multiple customer workspaces, when SaaS customers need repeatable form and funnel setup, or when administrators must control which features are available by plan.

Do not use this area as a catch-all record store. Keep records tied to the correct workspace, client, form, funnel, campaign, or lead source so analytics, permissions, exports, and automation rules stay accurate.

Practical Examples

A workspace owner reviews this page before turning on a production lead capture workflow.
An agency operator uses this feature while onboarding a new client campaign.
A SaaS admin checks this area when a customer cannot see an expected button or report.
A buyer uses this workflow to confirm the product is ready for paid traffic and customer access.

Recommended Workflow

Open the admin workspace with a super admin or authorized staff account.
Review current records, enabled modules, plan permissions, and recent activity before changing settings.
Make one controlled change, save it, then clear application and documentation cache when required.
Test the affected user-facing flow with a normal workspace user account.
Document the change in release notes, support notes, or internal operations records.

Important Fields and Records

Provider name, endpoint, authentication method, secret key, active status, and retry settings.
Field mappings from LeadFlow AI fields to provider fields.
Last run status, response code, response body, and failure reason.
Workspace or tenant owner, because records must remain separated between buyers, teams, and clients.
Status and visibility, because draft, published, archived, internal, and active records behave differently.
Created and updated timestamps, because troubleshooting often depends on knowing when a campaign changed.
Owner or assignee, because lead response speed and accountability matter in a lead generation product.

Permissions and Plan Access

Access should be controlled by workspace role, team permissions, owner permissions, and SaaS plan features. A form builder role may create drafts but not publish. A lead operator may view responses and update lifecycle stage but should not change custom domains, billing, or tracking scripts. Admins should test visibility with a non-admin account after changing plans, marketplace addons, or sidebar permissions.

Confirm the user's workspace owns the form, funnel, lead, client, or report being opened.
Confirm the active plan allows publishing, AI generation, automation, reports, files, custom domains, QR tools, templates, surveys, or integrations where relevant.
Hide buttons and routes for addon features when the addon package is not installed.
Review team roles before allowing delete, export, billing, integration, or domain changes.

Best Practices

Name records with form, funnel, source, offer, and date context. Validate forms before driving paid traffic. Use hidden fields and UTM capture consistently. Keep lifecycle stages simple enough for operators to update. Review analytics weekly and make one controlled change at a time so conversion changes can be understood. For agency work, keep each customer's workspace, team members, files, domains, and reports separated.

For production SaaS use, configure plan limits before launch, test payment and email delivery, and keep a backup before importing, deleting, or bulk updating lead data. For agency use, create a standard onboarding checklist for each client: workspace, brand settings, lead fields, consent copy, funnel pages, integrations, notification recipients, test submissions, and reporting cadence.

Section Guide

This section contains related pages that should be read in sidebar order when setting up LeadFlow AI for the first time. The parent page explains how the section fits into the complete lead generation workflow; the child pages explain the specific setup screens and operating tasks.

Marketplace Admin: Install, update, rescan, configure, and uninstall marketplace packages.
API Integration: Manage provider credentials, callbacks, API settings, and integration toggles.
Cache and Crons: Clear cache and configure scheduler, queues, and background jobs.

Troubleshooting

The page or button is not visible
Check the user role, workspace ownership, active SaaS plan, addon installation status, and sidebar/menu permissions. Clear cache after changing permissions or package status.

Saved changes do not affect the public form or funnel
Confirm the draft was published, the correct domain or embed code is being used, and browser cache or CDN cache is not serving an older version.

Lead data looks incomplete
Review required fields, custom field keys, hidden tracking fields, consent settings, spam protection, and integration mappings. Submit a test lead from a private browser session.

Notifications or webhooks are not delivered
Check mail settings, queue workers, cron configuration, webhook endpoint availability, provider credentials, and recent failed job logs.

A user sees the wrong information
Review workspace ownership, team membership, route permission middleware, plan features, and whether the account is operating inside the correct active team.

FAQ

Can this feature be sold inside SaaS plans?
Yes, when your license and business model allow it. Use plan permissions and limits to decide which plans can access forms, responses, funnels, surveys, AI tools, QR tools, reports, files, custom domains, integrations, support, and automation.

Should agencies create one workspace per customer?
That is the cleanest operating model for most agencies because it separates branding, leads, forms, funnels, reports, files, domains, team members, and integrations.

Can admins edit customer records?
Admins can usually inspect and support customer records, but production teams should keep an audit trail and avoid changing customer data unless support or operations requires it.

What should be tested before launch?
Test installation, login, plan access, form publishing, funnel redirects, survey links, QR links, lead capture, email automation, webhooks, reports, files, custom domains, payments, and cache clearing.