Keep subscription changes beside the related Linear work
When a subscription update affects a known issue, add the change details where the team is already coordinating.
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
Subscription updates can arrive separately from the issue they affect, forcing teammates to search across tools for context.
- Keep billing changes visible in the related issue discussion.
- Include the subscription and customer details available in the request.
- Avoid creating a duplicate task when an existing issue is the right place for context.
Setup
Build it in a few focused steps.
- 1Connect Billsby and Linear once in the Notis portal, if the Billsby connection is available for your account.
- 2Create an automation in Notis with a name and a prompt for adding subscription-change context to a Linear issue.
- 3In one instruction, tell Notis which issue to comment on and what available change details to include; provide a reliable issue identifier in the request or prompt.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real subscription-change example and a specified Linear issue.
Questions about this workflow
Can this find the right Linear issue automatically?
Only if the request or your instruction provides enough information to identify the issue. The workflow should not guess an issue from incomplete details.
Which subscription details will appear in the comment?
Only details included in the incoming request or otherwise supplied to Notis. The listed Billsby capabilities do not specify the exact webhook payload fields.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Billsby to Linear. A trigger fires from one place; an action lands in another.
Billsby 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.
Billsby 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.