Integrations Sweep

The integrations sweep is a quick walkthrough of the full GHL integrations page after the major connections (GBP, social, calendar, ads) are complete. The purpose is to catch any additional integrations the client might need: Stripe for payments, Quickbooks for accounting, Mailgun for email delivery, or any other third-party tool that connects to GHL. It also serves as a verification pass to confirm that everything connected earlier is still active and properly configured.

Why This Matters

The major connections get individual attention earlier in the call, but the integrations page has dozens of options. Some are relevant to the client’s business and would be missed without a deliberate sweep. A roofing company that uses Quickbooks needs that connection for invoice syncing. A med spa that uses Stripe needs payment processing linked. A real estate agent who uses Zillow might need a lead source integration. If you do not walk through the page, these connections get discovered weeks later during the build phase, requiring another call with the client to authenticate.

The sweep also catches connection failures. OAuth tokens can expire between the moment you connect an account and the end of the call. A social connection might show as “connected” but have a warning about insufficient permissions. A Google Calendar sync might have defaulted to the wrong calendar. Five minutes of verification now prevents hours of troubleshooting later.

Finally, the sweep demonstrates thoroughness. The client sees you methodically checking every integration option, confirming what is connected and noting what is not. This builds confidence that nothing is being overlooked. In an industry where many agencies wing it, a structured approach stands out.

How to Think About It

The integrations sweep is a checklist, not an exploration. You are not demonstrating every integration or explaining what each one does. You are scrolling through the integrations page and asking two questions for each relevant option: “Do you use this?” and “Should we connect it?”

Organize your sweep by category. Start with the connections you already made: Google (GBP, Calendar, Ads), Meta (Facebook, Instagram), and phone system. Verify each shows a green status or active indicator. Then move through the remaining categories: payment processors (Stripe, PayPal, Square), accounting (Quickbooks, Xero), email (Mailgun, custom SMTP), and any industry-specific integrations.

For each integration the client says they use, make a decision: connect now or flag for the build phase. Simple OAuth connections that take 30 seconds can be done on the call. More complex integrations that require API keys, configuration, or testing should be noted for the build team. The goal is to capture everything, not to connect everything.

Common Mistakes

Skipping the sweep because the call is running long. This is the most common reason the sweep gets cut. The call is already at 40 minutes and you still need to cover notification settings and the onboarding form. Five minutes for the sweep is still worth it. The alternative is discovering missing integrations during the build, which is far more disruptive.

Trying to connect everything on the spot. Some integrations require configuration beyond just clicking “connect.” Stripe needs webhook setup. Quickbooks needs account mapping. Custom SMTP needs DNS records. Note these for the build phase rather than trying to configure them live.

Not verifying existing connections. You connected GBP, social, and calendar earlier in the call. Things can change. OAuth can fail silently. Double-check each one during the sweep. It takes seconds and catches issues before they become problems.

Ignoring integrations outside the client’s current stack. The client might not use Stripe today, but if your package includes online booking with payment, they will need it. Flag integrations that are relevant to the deliverables in their package, even if the client does not currently use the tool.

Overwhelming the client with too many options. The integrations page can be intimidating. Do not read every option aloud. Focus on the categories relevant to the client’s business and package. Skip integrations that clearly do not apply (a plumber does not need a Shopify integration).

Tools Involved

The integrations page is centralized under Integrations in the GHL sub-account settings. Individual connections that were set up earlier in the call include GBP, Social Connections, Google Calendar, and Ads Accounts. Payment integrations connect to the Payments module. Email integrations affect deliverability for all email workflows. For agencies using GHL MCP, some integration configurations can be scripted and deployed programmatically during the build phase.

Where This Fits

The integrations sweep sits at sequence position 14, near the end of the quick start call. It depends on the major connections being attempted first: GBP, Social Connections, and Google Calendar. It runs alongside Notification Settings and Onboarding Form Preview, which are the other closing items on the call. Any integrations flagged during the sweep that were not connected on the call become build phase tasks.

Common Questions

How long should the integrations sweep take? Five minutes, maximum. You are scanning the page, asking quick questions, and noting items. If a specific integration sparks a long conversation, park it. “Let’s note that for the build and discuss it in detail then.”

What if the client uses a tool that does not have a native GHL integration? GHL supports Zapier and Make (Integromat) connections, which can bridge to thousands of third-party tools. Note the tool the client uses and flag it for your build team to evaluate whether a Zapier/Make integration or the GHL API can handle the connection.

Should I connect Stripe or payment processors during the quick start call? If the client has a Stripe account and the connection is straightforward (OAuth click), yes. If they need to create a Stripe account or configure complex payment settings, note it for the build phase. Payment processing setup often requires attention to detail around currencies, tax settings, and webhook configurations that do not belong on a quick start call.