Connect Linear to Klipfolio
When something happens in Linear, Notis takes the next step in Klipfolio. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Linear to Klipfolio
Log new Linear issues for dashboard tracking
Append a concise row for each new Linear issue to an existing Klipfolio intake data source, keeping incoming work visible without manual copying.
Update a Klipfolio snapshot when issue priority changes
When a Linear issue changes, have Notis update the existing Klipfolio snapshot with the latest priority context so reporting stays aligned with the work.
Add Linear comment decisions to a Klipfolio log
Append a concise record of new Linear comments to an existing Klipfolio decision log, making discussion outcomes easier to review later.
Record Linear project changes in a Klipfolio tracker
Append project property changes to an existing Klipfolio tracker so shifts in status, lead, or target date are easier to follow.
Keep project update posts in a Klipfolio history
Add a concise entry for each Linear project update post to an existing Klipfolio history source for easier periodic review.
Log public issue property changes for workload reviews
Append changes to public-team Linear issue properties to a Klipfolio workload log, helping make changing priorities and ownership more visible.
Add public-team issue intake to a Klipfolio queue
Append newly created public-team Linear issues to an existing Klipfolio queue so incoming requests are visible in a shared intake view.
Capture private-team comment follow-ups
Append a concise record of new private-team Linear comments to a Klipfolio follow-up log, keeping sensitive team discussions visible to authorized reporting users.
Track private-team issue intake in Klipfolio
Append newly created private-team Linear issues to an existing Klipfolio intake source for teams that need an authorized high-level view of incoming work.
Supported Triggers and Actions
Notis builds workflows that link Linear to Klipfolio. A trigger fires from one place; an action lands in another.
Linear triggers
Klipfolio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Append Data to Data Source
This tool appends plain-text or csv data to an existing data source in klipfolio. it requires two parameters: 'data' which contains the data in plain-text or csv format, and 'data source id' which specifies the target data source.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Data Source
This tool creates a new data source in klipfolio. it uses the post /datasources endpoint to add a data source with required parameters (name, format, connector, endpointurl) and optional parameters (description, refreshinterval, method, additionalproperties).
Comment Received Trigger
Triggered when a comment is received.
Create Tab (Dashboard)
This tool creates a new tab (dashboard) in klipfolio. a tab serves as a container for organizing and displaying klips (data visualizations) in a meaningful way. the tool allows users to set up a new dashboard with specific properties and configurations.
Issue Created Trigger
Triggered when a new issue is created.
Delete Data Source
This tool permanently removes a specified data source from the klipfolio account. this operation is destructive and cannot be undone. the data source must not be currently in use, and proper permissions are required.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Get Dashboard Details
This tool retrieves detailed information about a specific dashboard (formerly known as tab) in klipfolio. it allows users to obtain comprehensive information including properties, settings, and metadata of the dashboard.
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).
Get Data Source Instance Details
This tool retrieves detailed information about a specific data source instance in klipfolio. it can return data in either json or csv format depending on the data source type.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get Klips
This tool retrieves a list of all klips accessible to the authenticated user. klips are visualization components in klipfolio that display data in various formats like charts, tables, or metrics.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Get User Profile
This tool is used to retrieve the authenticated user's profile information and test the authentication status. it verifies api connectivity and access permissions by returning profile details such as user id, username, email, company information, role and permissions, and account status.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything 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.
More ways to connect Linear and Klipfolio
Connect any two apps with Notis in the middle.
Linear and Klipfolio, 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 Klipfolio.