SupportAsk360 connectors
Connect approved Lead360 and provider resources that Ask360 bots and playbooks can use inside one sub-account.
How this fits into Lead360Explore Ask360See how Pieces, memory, channels, playbooks, learning, and kits work together.- 01
How Lead360 helps
- 02
Before you begin
- 03
Complete the workflow
- 04
Understand the key controls
How Lead360 helps
Connectors give Ask360 controlled access to supported product or provider resources without placing credentials in prompts, memory files, or bot instructions. Each connection remains bound to the current tenant and can be granted only to the bots or workflows that need it.
When to use this workflow
Use Connectors when a bot or playbook needs a supported data source or action target that is not already available through its built-in Lead360 capabilities.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Verify provider ownership and the intended sub-account.
- Review permissions, data categories, and expected read or write effects.
- Identify every bot, Piece, playbook, or automation that will depend on the connection.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open Ask360 Tools and select Connectors.
- Choose the supported connector and start its authorization or setup flow.
- Authenticate with the correct provider account and review requested permissions.
- Select or map only the required provider resources.
- Test the connection with controlled data, then assign it to the intended consumer.
Understand the key controls
Credential handling
Provider secrets are handled by the connection flow and should never be copied into Ask360 chat, Memory Brain, templates, or client-side code.
Resource mapping
A valid provider login is not enough. The connection must point to the correct calendar, workspace, site, account, or other provider resource.
Revocation
Disconnecting or expiring a connector can stop dependent bots and playbooks. Review dependencies before removal.
Confirm the result
Do not rely on a success message alone. Confirm the saved state and any live effect in the product area that owns the final record.
- Use the connector test where available.
- Confirm a controlled read returns the intended resource.
- For writes, verify the provider record and Lead360 audit evidence.
Troubleshooting
Authorization succeeds but data is missing
Check provider resource selection, account access, tenant mapping, and whether the connector scope includes the requested data.
A connector repeatedly expires
Review provider token policy, revoked consent, account security changes, and whether the integration needs reauthorization.
Frequently asked questions
Can one connector be shared across every sub-account?
Connector access is tenant-scoped. A provider connection and its resource mapping must be approved for the exact sub-account and consumers that use it.
Should API keys be stored in bot memory?
No. Credentials belong in the supported connector or integration secret flow, never in prompts, Memory Brain files, playbooks, or exported kits.
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.