SupportIntegrations
Authorize external services for this sub-account and control exactly what Lead360 may read or change.
How this fits into Lead360Explore the agency and client platformConnect administration, providers, users, billing, and developer access.- 01
How Lead360 helps
- 02
Connect safely
- 03
Before enabling writes
- 04
Maintain the connection
How Lead360 helps
Lead360 Integrations connects a sub-account with supported external providers and services. Tenant-scoped connection state, permissions, mappings, and test results help teams use outside capabilities without sharing credentials in ordinary content or crossing account boundaries.
When to use this area
Use Integrations to connect, review, reauthorize, test, or disconnect a supported provider used by Lead360 workflows.
Before you begin
- Confirm provider ownership and the exact sub-account.
- Review requested permissions and grant only what the workflow needs.
- Identify automations, calendars, payments, channels, or sites that depend on the connection.
Connect safely
- Choose the provider and confirm the account belongs to this sub-account.
- Review the requested scopes and grant only what the workflow needs.
- Complete authorization without sharing credentials with staff or Ask360.
- Run the provided connection test and confirm the expected account or resource is listed.
Before enabling writes
- Verify read access first.
- Confirm which records, calendars, ad accounts, channels, or stores will be affected.
- Use a controlled test record or action.
- Require human approval for live changes performed through Ask360 or automation.
Maintain the connection
Monitor failed syncs and expired authorization. Reconnect, rotate, or disconnect access when ownership changes, then verify dependent automations and reports.
Use Ask360 here
Ask360 can explain provider requirements, current authorized connection metadata, scopes, dependencies, and a controlled test plan. Authentication and consent stay with the signed-in user; this Help flow never asks for credentials, grants scopes, disconnects a provider, or performs an external write.
Confirm the result
A completed Integrations workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.
- Use the product test action where available.
- Confirm read and write behavior with controlled data.
- Review provider logs and Lead360 records for the same operation.
Troubleshooting
A connection shows expired or unauthorized
Reauthorize with the correct provider account and scopes, then retest dependent workflows.
Data maps to the wrong place
Review tenant binding, resource selection, field mapping, and duplicate provider connections before syncing again.
Frequently asked questions
What should I confirm before using Integrations?
Confirm provider ownership and the exact sub-account. Review requested permissions and grant only what the workflow needs. Identify automations, calendars, payments, channels, or sites that depend on the connection. Start with a small, reviewable change whenever the workflow can affect customers, money, published content, or shared records.
How does Lead360 help with Integrations?
Lead360 Integrations connects a sub-account with supported external providers and services. Tenant-scoped connection state, permissions, mappings, and test results help teams use outside capabilities without sharing credentials in ordinary content or crossing account boundaries.
Continue with Lead360
Use this workflow in Lead360
Put this guide into practice with a 14-day free trial of Lead360 Pro early access, or continue learning through the related collection.