Skip to content
Notis

Keep Linear issues current with Backendless service status

Reflect a service status change in the Linear issue your team is already tracking.

Trigger

Webhook received

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

Action

Update issue

Updates an existing linear issue using its `issue id`; requires at least one other attribute for modification, and all provided entity ids (for state, assignee, labels, etc.) must be valid.

Why this helps

A status recorded in one system can leave the related Linear issue stale and misleading.

  • Update an existing issue when Backendless sends a status change.
  • Keep investigation notes aligned with the latest supplied service details.
  • Reduce stale issue information and manual follow-up.

Setup

Build it in a few focused steps.

  • 1Connect Backendless and Linear once in the Notis portal.
  • 2Create an automation in Notis and name it.
  • 3Tell Notis to update the existing Linear issue identified in each request with the supplied service status and relevant investigation details.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real status change and check the updated issue.

Questions about this workflow

Does this workflow update any issue automatically?

It should update the issue identified by the incoming request. Include the correct issue identifier and the details to apply.

What kind of status can it use?

It can use status information supplied by Backendless. The workflow does not assume a particular Backendless status field or invent one.

What happens if the issue identifier is missing?

Notis cannot reliably choose the intended issue without enough identifying information in the request.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Backendless to Linear. A trigger fires from one place; an action lands in another.

Backendless 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.

Backendless 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.