Stay Accountable: Weekly Blocker Roundup
Blockers need accountability. Notis runs a weekly summary of what's stuck so your team can unblock and move forward.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get BotStar Application IDs
Tool to retrieve the botstar application id (`appid`). use when initializing or reinitializing the live chat widget.
Why this helps
Blockers slip through cracks; no weekly accountability; leadership unaware of what's actually stuck.
- Automatic weekly blocker visibility
- Build accountability without manual meetings
- Make unblocking a priority
Setup
Build it in a few focused steps.
- 1Connect Linear and Botstar to Notis.
- 2Tell Notis: 'Every Monday morning, find all issues with Blocked status and summarize them in a report'.
- 3Select 'Notis Cron - Weekly' and choose your day and time.
- 4Notis retrieves bot analytics and issues to create a comprehensive roundup.
- 5Review the first report and adjust which statuses or labels count as blockers.
Questions about this workflow
Can I include blocked issues from multiple teams?
Yes. Say: 'Include blockers from all teams' or 'Only from the product and engineering teams' and Notis filters accordingly.
What does the report include?
Title, who it's blocking, how long it's been stuck, and why (reason label). Ask Notis to add what you need.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Botstar. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
Livechat boot
Tool to reinitialize the live chat widget with provided data. use after initial load to reset or update widget configuration.
Issue Created Trigger
Triggered when a new issue is created.
Close BotStar Livechat Widget
Tool to hide the live chat window. use when the chat widget is configured in livechat or popup mode.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Livechat on open
Tool to register a callback when the chat window is opened. use after widget initialization.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
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').
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
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.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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.
Linear 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.