Skip to content
Notis

Make Billsby cancellations visible for review

Give cancellation notices a consistent review path, so the team can spot cases that need a response or product follow-up.

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

Cancellation information can disappear into billing records before anyone has time to identify a useful next step.

  • Create a review task when a cancellation request reaches the webhook.
  • Preserve the cancellation reason when it is present in the request.
  • Help the team notice recurring themes without assuming a reason that was not provided.

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 and describe the cancellation review outcome you want.
  • 3In one instruction, tell Notis to create a Linear issue from the cancellation details supplied, noting any missing reason.
  • 4Pick the Notis webhook trigger and choose where run reports should go.
  • 5Test with one real cancellation example sent to the webhook.

Questions about this workflow

Does this determine why a customer cancelled?

No. It can carry forward a reason when the incoming request includes one, but it cannot infer an unstated reason.

Can I use this without a Billsby trigger event?

Yes, the trigger is Notis's webhook. A Billsby-originated request needs to be sent to that webhook for the automation to start.

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.

TriggerScheduled

Create linear attachment

Creates a new attachment and associates it with a specific, existing linear issue.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create a comment

Creates a new comment on a specified linear issue.

ActionInstant

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.

ActionInstant

Get create issue default params

Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.

ActionInstant

Create a label

Creates a new label in linear for a specified team, used to categorize and organize issues.

ActionInstant

Delete issue

Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.

ActionInstant

Get all teams

Retrieves all teams from the linear workspace without requiring any parameters.

ActionInstant

Download issue attachments

Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.

ActionInstant

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.