Track Billsby payment failures in Linear
Give each payment failure a clear place to land, with the customer and invoice context included when the webhook provides it.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Payment failures can get buried in billing activity, leaving nobody sure who should investigate or follow up.
- Create a visible investigation task from each incoming failure notice.
- Keep customer, invoice, and error details together when present in the payload.
- Reduce manual copying between billing activity and your team backlog.
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 by naming it and describing the payment-failure follow-up you want.
- 3In one instruction, tell Notis to create a Linear issue with the available customer, invoice, and failure details.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real payment-failure example sent to the webhook.
Questions about this workflow
Does Billsby provide a built-in trigger for this automation?
No Billsby trigger event is listed here. The automation starts when a request reaches its Notis webhook, so a Billsby-originated request must be sent to that webhook for this workflow to run.
What if the webhook payload has no customer or invoice details?
Notis can only include details present in the request. Tell it to note missing information in the issue rather than inventing it.
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.