SupportManage Ask360 plugins and apps
Assign supported plugins, verified apps, and custom MCP connections to an Ask360 bot with explicit tenant and effect controls.
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
Plugins and apps extend an Ask360 bot with supported external capabilities while keeping authorization, tenant scope, resource mapping, and revocation separate from bot prompts and memory. The workspace distinguishes managed apps, verified OAuth connections, and custom MCP connections.
When to use this workflow
Use Plugins when a bot needs an approved external tool that is not provided by its built-in Lead360 capabilities or standard connectors.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Verify the provider and business owner.
- Review requested data access, actions, OAuth scopes, MCP tools, and risk.
- Choose the exact bot and sub-account that require the plugin.
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 Plugins.
- Choose Apps or MCP based on the supported connection type.
- Complete the provider authorization or custom MCP configuration.
- Inspect discovered tools and assign only the required plugin capability to the bot.
- Test reads first, then controlled writes with confirmation and audit review.
Understand the key controls
Verified apps and custom MCP
Verified apps use a managed authorization flow. Custom MCP is a beta connection path and requires careful server, authentication, and tool review.
Tool discovery
A connected server may expose multiple tools. Review names, input schemas, effects, and confirmation requirements before assignment.
Revocation and dependencies
Removing provider consent or a plugin assignment can stop bot and playbook workflows. Record ownership before disconnecting.
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.
- Confirm the plugin belongs to the intended provider account and tenant.
- Test allowed and disallowed operations.
- Inspect both Lead360 audit evidence and provider results.
Troubleshooting
OAuth completes but tools are unavailable
Check provider scopes, app status, resource access, tenant mapping, and whether the bot has the plugin assignment.
A custom MCP server changes its tools
Disable high-risk use, rediscover and review the tool catalog, then retest schemas and effects before restoring access.
Frequently asked questions
What is the difference between an app and MCP?
Apps use supported provider integration flows. MCP connects a compatible tool server and exposes its discovered tools. Both still require explicit authorization, bot assignment, and effect review.
Can credentials be pasted into Ask360?
No. Use the supported authorization or secret configuration. Do not place tokens in chat, memory, playbooks, templates, or 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.