Update a Docsbot bot from an Asana review task
When bot maintenance reaches review, carry the requested changes forward without retyping the task details into Docsbot.
Trigger
Task Moved to Section
Triggers when a task is moved to a section in a project.
Action
Update Bot
Tool to update specific fields for a bot (e.g., name, description, settings). use after confirming valid team and bot ids.
Why this helps
Bot updates are easy to postpone when the request lives in Asana but the change has to be repeated in another tool.
- Run a requested bot update at a clear project milestone.
- Use task-provided instructions as the source of the requested changes.
- Keep the update tied to the task that tracks the work.
Setup
Build it in a few focused steps.
- 1Connect Asana and Docsbot ai once in the Notis portal.
- 2Create an automation and name it for the bot maintenance milestone.
- 3In one instruction, tell Notis to update only the specified bot fields using the task's explicit values, and to stop if the team or bot identifiers are missing.
- 4Pick Asana's Task Moved to Section trigger and choose where run reports should go.
- 5Test by moving one real task with valid identifiers and explicit requested values into the review section.
Questions about this workflow
Will Notis infer new bot settings?
The instruction should use explicit values in the task and avoid guessing any missing settings.
What identifiers are needed?
The update action requires valid team and bot identifiers.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Asana to Docsbot ai. A trigger fires from one place; an action lands in another.
Asana triggers
Docsbot ai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Bot
Tool to create a new bot within a team. use when you have a valid team id and want to provision a new bot.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Bot
Tool to delete a specific bot by its id. use after confirming the bot id is correct to permanently remove a bot from the system.
Attachment Added to Task
Triggers when an attachment is added to a task.
Generate Conversation Ticket
Tool to generate a structured support ticket from a chat agent conversation. use when you need to convert an existing conversation into a ready-to-submit helpdesk ticket.
New Comment on Task
Triggers when a comment is added to a task in a project.
Get Bot Details
Tool to fetch details of a specific bot by id within a team. use after confirming valid team and bot ids.
New Task Created
Triggers when a new task is created in a project.
Get Team Details
Tool to fetch details of a specific team by its id. use when you need full team info including members and settings after confirming the team id.
Task Moved to Section
Triggers when a task is moved to a section in a project.
List Team Bots
Tool to list all bots for a given team. use after confirming the team id to retrieve all associated bots for that team.
Tag Added to Task
Triggers when a tag is added to a task. Note: Asana's event structure is inverted for tag events — the resource is the task and the parent is the tag. So parent.gid gives the tag GID.
List Questions
Tool to list all questions asked of a specific bot. use after confirming the bot's identifier. example: "list questions for bot abc123 with status 'unanswered'."
Task Updated
Triggers when a task is updated in a project.
List Bot Sources
Tool to list all sources for a specific bot. use when you need to retrieve paginated source lists after confirming the bot's identifier.
Connect any two apps with Notis in the middle.
Asana and Docsbot ai, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Docsbot ai.