Skip to content
Notis

Connect Linear to Leadoku

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

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Linear to Leadoku

View example

Keep new lead follow-up visible

When a Linear issue flags a new prospect or inbound inquiry, retrieve recent Leadoku connections so the owner can spot a warm contact and follow up while context is fresh.

View example

Check connections when a prospect qualifies

When a Linear issue changes to a qualified prospect state, retrieve Leadoku's new connections to help the owner decide whether a fresh connection merits a next step.

View example

Add connection context to inbound prospect issues

When an inbound prospect issue is created in Linear, fetch Leadoku's new connections and report relevant results so the team can start from shared context.

View example

Check connections when a prospect gets a comment

When a Linear comment adds context to a prospect issue, retrieve recent Leadoku connections so the follow-up owner can act with the updated discussion in mind.

View example

Review connections when work becomes sales-ready

When a Linear issue is updated to signal sales readiness, retrieve Leadoku's recent connections and give the owner a concise review cue.

View example

Check connections for partnership prospects

When a Linear issue records a partnership prospect, retrieve Leadoku's new connections to surface possible warm context before the next outreach decision.

View example

Give stalled prospect work a fresh connection cue

When a Linear prospect issue is updated to resume or reopen work, check Leadoku's new connections for context that may help the owner restart follow-up.

View example

Give a new prospect owner connection context

When ownership changes on a Linear prospect issue, retrieve Leadoku's new connections so the incoming owner has a useful follow-up starting point.

View example

Check connections when prospect priority rises

When a Linear prospect issue's priority is raised, retrieve Leadoku's new connections so the team can spend its attention with current relationship context.

Supported Triggers and Actions

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

Linear triggers

Leadoku actions

Recurring trigger

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

TriggerScheduled

Get New Connections

Retrieves a list of new connections from growth-x (formerly leadoku). the 'tsfield' for this action is 'connection date' (mapped from 'creation date' in the api response).

ActionInstant

Webhook trigger

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

TriggerInstant

Comment Received Trigger

Triggered when a comment is received.

TriggerInstant

Issue Created Trigger

Triggered when a new issue is created.

TriggerInstant

Issue Updated Trigger

Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.

TriggerInstant

Private Team Comment Created

Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).

TriggerPolling

Private Team Issue Created

Fires when a new issue appears in a private Linear team (polled with the connected user's token).

TriggerPolling

Private Team Issue Properties Updated

Fires when properties on an issue change in a private Linear team (polled with the connected user's token).

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 recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ 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

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only
Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match
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 Leadoku

Connect any two apps with Notis in the middle.

Linear and Leadoku, 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 Leadoku.