Find Docsbot team ownership during Jira triage
Give issue reviewers a quick view of available Docsbot teams when support ownership is unclear.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
List Teams
Tool to list all teams. use when you need to retrieve every team associated with the authenticated user.
Why this helps
A new issue can bounce between people while everyone tries to work out which support team owns it.
- Make available Docsbot teams visible during triage.
- Reduce manual searching for support ownership.
- Give people returned team information to guide routing.
Setup
Build it in a few focused steps.
- 1Connect Jira and Docsbot AI once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name, prompt, report channel, and trigger.
- 3In one instruction, ask Notis to list the authenticated user's Docsbot teams when a Jira issue is created and summarize available team information for a human routing decision.
- 4Pick the Jira New Issue trigger and choose where run reports go.
- 5Test with one real issue and review the team directory.
Questions about this workflow
Does this assign the issue or route a customer automatically?
No. It lists teams to support a human ownership decision.
Does the Docsbot action need a team id?
List Teams retrieves all teams associated with the authenticated user.
Can it determine ownership from team names alone?
Only if the returned information is sufficient. Your team should supply or confirm any ownership rules.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Docsbot ai. A trigger fires from one place; an action lands in another.
Jira 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.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
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 Project
Triggered when a new project is added in Jira
Get Bot Details
Tool to fetch details of a specific bot by id within a team. use after confirming valid team and bot ids.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
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.
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.
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'."
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.
Jira 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.