Connect deliberately
In Lightning Leads, open Profile → AI Coach & Personal AI → Connect Personal AI, choose a supported provider, and follow the secure setup shown there.
Personal AI Connectors
Ask a supported personal AI for Lightning Leads help, field-sales context, and approved account actions. Lightning Leads remains the system of record and verifies every completed change.
Public directory listings are subject to each AI provider's availability and review. A platform is not listed as public here until that listing is live.
In Lightning Leads, open Profile → AI Coach & Personal AI → Connect Personal AI, choose a supported provider, and follow the secure setup shown there.
Ask your AI to explain a feature, review onboarding progress, prepare field context, or help with a specific Lightning Leads workflow.
Actions such as adding a lead note or marking a lead for follow-up require your confirmation and must be verified by Lightning Leads before the AI reports success.
Current availability
Support varies by provider, plan, region, and product surface. Lightning Leads uses a shared secure tool service, but each provider controls how custom connections and public listings work.
A marketplace package is being prepared for provider review. Public discovery is not promised until an approved listing is actually available.
Private or custom setup is limited to ChatGPT or Codex surfaces that support the required connector connection.
Lightning Leads can be added as a remote MCP connection where a Claude product and plan support remote MCP servers.
Setup and directory availability are controlled by Anthropic and may differ across Claude products.
The Lightning Leads public-help tools have been tested through a Grok custom MCP connector. Account-specific access requires a secure private connection.
A public Grok catalog listing is not advertised here unless and until that listing becomes available.
Billing stays with Lightning Leads. The connector does not sell, upgrade, or manage a Lightning Leads subscription inside an AI conversation. Manage your plan in the Lightning Leads app or on the Lightning Leads website. Access to an AI provider may require a separate provider account or subscription.
Explain Lightning Leads features, onboarding steps, territories, routes, lead statuses, appointments, and follow-up workflows.
Read account-scoped briefing, performance, territory, route-planning, and appointment-preparation context when you request it.
Request supported actions such as adding a lead note or marking a lead for follow-up. Important writes require explicit confirmation.
Designed for control
Your AI can request information or an action, but the Lightning Leads service checks the connection, account scope, permissions, required confirmation, and result.
Private data requires a connection. Public product help does not grant access to your Lightning Leads account.
Credentials stay out of tool results. Connector tokens and provider credentials are not returned to the AI as action results.
Writes require confirmation. The AI must not claim a change succeeded unless Lightning Leads confirms and verifies it.
You can disconnect. Revoke or replace a connection from Lightning Leads and remove it in your AI provider's settings.
No. Enter a credential only in the provider's designated secure connection or authorization field. If a credential was pasted into a chat or otherwise exposed, revoke or replace it before reconnecting.
No. A connected provider receives only the information returned by the specific tool you ask it to use, subject to your Lightning Leads account scope and permissions. Review the provider's privacy terms because the provider separately controls its processing of chat and tool data.
Revoke or replace the Personal AI connection in Lightning Leads and remove the connection from the AI provider's settings. Revocation blocks new Lightning Leads requests through that credential.
Use the public support page for setup, troubleshooting, privacy, or revocation help. Never include passwords, API keys, or connector credentials in a support message.