SupportAssign automations to an Ask360 bot
Make selected Lead360 automations available to an Ask360 bot without granting unrelated workflows.
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
Automation assignment lets a bot discover or start only the workflows approved for its role. The automation keeps its own version, trigger, validation, execution log, permissions, and live effects, while the bot provides a controlled way to select inputs and request execution.
When to use this workflow
Use Bot Automations when a repeatable, tested workflow should be available through a specific Ask360 bot.
Before you begin
Start with the exact sub-account and the smallest set of permissions, records, and resources required for the task.
- Validate and publish the automation version.
- Document required inputs, target rules, effects, and idempotency.
- Confirm the bot capability and effect policy for starting the workflow.
Complete the workflow
Follow the steps in order and stop when a required resource, permission, review, or approval is missing.
- Open the bot profile and its Automations area.
- Select the exact published automation.
- Review required inputs, effects, and approval behavior.
- Assign the automation to the bot.
- Run a controlled request and inspect the complete Automation Run.
Understand the key controls
Assignment does not enable every automation
Only selected workflows are made available to the bot, which keeps unrelated tenant automations outside its role.
Run evidence
The bot response is not the execution record. Automation Runs remains the source for version, inputs, step states, and errors.
Removal
Removing an assignment stops future bot access but does not erase prior runs or reverse completed effects.
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 bot lists only intended automations.
- Compare test inputs with the run record.
- Verify every live result in its owning product or provider.
Troubleshooting
The automation does not appear
Check publication state, sub-account, bot assignment, user access, and whether the workflow is supported for bot invocation.
The bot starts the wrong version
Review the automation publication and assignment, then inspect the version identifier captured by the run.
Frequently asked questions
Does removing an automation from a bot undo past runs?
No. Removal affects future availability only. Prior run history and completed live effects remain.
Can a bot run any automation in the sub-account?
No. The automation must be explicitly assigned and all user, capability, input, effect, and confirmation controls still apply.
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.