Skip to content
Notis

Connect Linear to IBM X-Force Exchange

When something happens in Linear, Notis takes the next step in IBM X-Force Exchange. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Triggers when a new comment is received.

Do this · Action

Retrieves the latest public collections.

Examples

Ways Notis can move work from Linear to IBM X-Force Exchange

Start new security issues with current threat context

When a Linear issue is created, retrieve the latest public X-Force Exchange collections to give the team a current threat-intelligence starting point.

Keep IP reputation categories close to issue updates

When a Linear issue changes, retrieve X-Force Exchange's IP reputation category list so the team can interpret IP-related investigation notes consistently.

Surface URL category guidance from issue comments

When someone comments on a Linear issue, retrieve X-Force Exchange's URL category list to support consistent interpretation of URL-related discussion.

Refresh public threat context when a project changes

When Linear project properties change, retrieve the latest public X-Force collections to help the team revisit its threat context as project scope or priority shifts.

Review the full public collection catalog after project updates

When a Linear project update is posted, retrieve public X-Force collections with pagination support for a broader intelligence review.

Refresh IP category reference when issue properties change

When public-team issue properties change, retrieve X-Force Exchange's IP reputation category list to support triage when ownership, priority, or labels shift.

Add URL classification context to public issue discussions

When a comment is posted on a public-team Linear issue, retrieve X-Force Exchange's URL categories for discussion of URL-related threats.

Give private security issues a broad public collection scan

When a private-team issue is created, retrieve public X-Force collections through pagination to support a wider initial threat review.

Keep IP reputation definitions with private issue changes

When a private-team issue's properties change, retrieve the X-Force IP reputation category list to make IP triage terminology easier to carry across handoffs.

Supported Triggers and Actions

Notis builds workflows that link Linear to IBM X-Force Exchange. A trigger fires from one place; an action lands in another.

Linear triggers

IBM X-Force Exchange actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Latest Public Collections

Retrieves the latest public collections.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Public Collections Paginated

Retrieves public collections across pages of results.

ActionInstant

Comment Received Trigger

Triggers when a new comment is received.

TriggerInstant

Get IPR Category List

Retrieves the available IP reputation categories.

ActionInstant

Issue Created Trigger

Triggers when a new issue is created.

TriggerInstant

Get URL Category List

Retrieves URL classification categories from IBM X-Force Exchange.

ActionInstant

Issue Updated Trigger

Triggers when an issue is updated, such as when its labels or status change.

TriggerInstant

Get User Profile Information

Retrieves the authenticated user’s profile information.

ActionInstant

Private Team Comment Created

Fires when a comment is posted on an issue in a private Linear team.

TriggerPolling

Get Current API Version

Retrieves information about the current API version.

ActionInstant

Private Team Issue Created

Fires when an issue is created in a private Linear team.

TriggerPolling

Generate API Key and Password

Generates a new API key and password for authentication.

ActionInstant

Private Team Issue Properties Updated

Fires when an issue’s properties change in a private Linear team.

TriggerPolling
Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit
Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

Notis

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect Linear and IBM X-Force Exchange

Connect any two apps with Notis in the middle.

Linear and IBM X-Force Exchange, or any other combination from 1,600+ 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 IBM X-Force Exchange.