Reconfigure BotStar when a Jira issue arrives
Start a widget configuration refresh when issue intake changes what the support flow needs.
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 boot
Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.
Why this helps
Issue-driven support changes can leave a widget running with outdated configuration until someone remembers to refresh it.
- Prompt a supported widget reinitialization when an issue arrives.
- Keep configuration details in the automation instruction.
- Reduce missed widget setup follow-ups.
Setup
Build it in a few focused steps.
- 1Connect Jira and BotStar once in the Notis portal.
- 2Create a named automation in Notis.
- 3In one instruction, tell Notis when to reinitialize the BotStar widget and provide the needed configuration data.
- 4Pick the Jira New Issue trigger and choose where run reports should go.
- 5Test with one real issue and verify the widget configuration.
Questions about this workflow
Does the issue automatically provide all boot data?
No. The action uses provided data. Include the required configuration in the instruction or context.
Can this simply update user details?
No. Widget boot reinitializes widget configuration. Updating details in the current session is a separate action.
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.