Bring new Jira issue context into a BotStar conversation
Give your support team useful issue context in the live chat session they are already handling.
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
Livechat update
Tool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.
Why this helps
People end up switching between Jira and BotStar to keep a customer conversation current after an issue is filed.
- Keep active conversations aligned with newly filed issues.
- Reduce manual copying between ticket tracking and chat.
- Let Notis interpret available issue details for the current session.
Setup
Build it in a few focused steps.
- 1Connect Jira and BotStar once in the Notis portal.
- 2Create an automation in Notis and give it a clear name.
- 3In one instruction, tell Notis to use new Jira issue details to update the current BotStar live chat user profile when appropriate.
- 4Pick the Jira New Issue trigger and choose where run reports should go.
- 5Test with one real issue and confirm the BotStar session details are useful.
Questions about this workflow
Does this start a new BotStar chat?
No. It uses the Livechat update action to modify user details on the current live chat session.
Will it run for issues in every Jira project?
No. The New Issue trigger only fires for the Jira project configured for that trigger.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Botstar. A trigger fires from one place; an action lands in another.
Jira triggers
Botstar actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
BotStar LiveChat onClose Callback
Tool to register a callback when the chat window is closed. use after the widget is initialized. example prompt: "register an onclose handler that logs 'goodbye!' to the console."
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get BotStar Application IDs
Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Livechat boot
Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.
New Project
Triggered when a new project is added in Jira
Close BotStar Livechat Widget
Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.
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.
Livechat on open
Tool to register a callback when the chat window is opened. use after widget initialization.
Livechat open
Tool to show the live chat window. use after the widget has been bootstrapped with botstarapi('boot') to programmatically open the chat window (mode must be 'livechat' or 'popup').
Livechat update
Tool to update user details on the current live chat session. use when you need to modify user profile attributes during an active conversation.
Get BotStar Webview Parameter
Tool to retrieve a parameter value passed from the botstar chatbot to the webview. use inside onchatbotready after your page loads in modal mode with bs:input meta tags.
Connect any two apps with Notis in the middle.
Jira and Botstar, 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 Botstar.