Connect Linear to Folk

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

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Linear to Folk

View example

Create a Folk company from a Linear prospect issue

When a new Linear issue contains a prospective company and its details, create a Folk company after checking for a duplicate.

View example

Reflect Linear project changes on a Folk company

When a Linear project changes, find the corresponding Folk company and update only the company details supported by the project.

View example

Look up Folk contacts from Linear comments

When a Linear comment asks who to contact at a company, search Folk people and report matching contacts with their available details.

Supported Triggers and Actions

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

Linear triggers

Folk actions

Recurring trigger

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

TriggerScheduled

Create Company

Tool to create a new company in the workspace. use after gathering all required company details and ensuring the name is unique.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Company

Tool to delete a company from the workspace (irreversible). use after confirming this company should be removed.

ActionInstant

Comment Received Trigger

Triggered when a comment is received.

TriggerInstant

Delete Person

Tool to delete an existing person in the workspace (irreversible). use after confirming this person should be permanently removed.

ActionInstant

Issue Created Trigger

Triggered when a new issue is created.

TriggerInstant

List Companies

Tool to list companies in the workspace. use when you need a paginated overview of companies, optionally filtered.

ActionInstant

Issue Updated Trigger

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

TriggerInstant

Get Company

Tool to retrieve an existing company by its id. use after authentication has been verified.

ActionInstant

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

Get Current Workspace User

Tool to get details of the current authenticated workspace user. use after authentication to retrieve the user's profile information.

ActionInstant

Private Team Issue Created

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

TriggerPolling

Get Person

Tool to retrieve an existing person by their id. use when you need full profile details of a person by their unique identifier.

ActionInstant

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

List Group Custom Fields

Tool to list custom fields for a specific group and entity type. use after selecting a group and entity type to inspect available custom fields.

ActionInstant

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.

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.