Carry Botpress escalation context into Linear
When a conversation needs a human or product follow-up, keep its key details close to the related issue with a concise Linear comment.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a comment
Creates a new comment on a specified linear issue.
Why this helps
An escalation can lose its useful details when someone reports only that a conversation needs attention, without carrying along what happened.
- Keep the escalation reason and relevant conversation context together.
- Give the issue owner a clearer starting point for follow-up.
- Avoid switching back to chat history to recover the initial report.
Setup
Build it in a few focused steps.
- 1Connect Botpress and Linear once in the Notis portal.
- 2Create an automation in Notis and name it.
- 3Tell Notis to summarize the escalation and relevant Botpress context, then comment on the related Linear issue.
- 4Choose the webhook trigger and where run reports should go.
- 5Test by sending one real escalation example to the webhook.
Questions about this workflow
How does the workflow know an escalation occurred?
Botpress has no listed trigger events here. An HTTP request to the Notis webhook starts the automation, so the escalation process must send that request.
What if the Linear issue is not identified in the incoming context?
The comment action requires a specific issue. Make the relevant issue reference available in the request or automation instruction.
Can Notis include information that was not sent?
Notis can summarize available conversation content. Any missing escalation reason or issue reference must be supplied or available from the connected context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Botpress to Linear. A trigger fires from one place; an action lands in another.
Botpress triggers
Linear actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create a comment
Creates a new comment on a specified linear issue.
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Botpress and Linear, 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 Linear.