Capture logged work from new Linear issues
When a new Linear issue explicitly records completed billable work and its duration, create a matching Harvest time entry so the hours are not lost in task notes.
When something happens in Linear, Notis takes the next step in Harvest. 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
Create a client record.
When a new Linear issue explicitly records completed billable work and its duration, create a matching Harvest time entry so the hours are not lost in task notes.
When a Linear issue changes, have Notis retrieve relevant Harvest time entries and report the recorded hours alongside the issue for a quick review.
When a Linear project is created, have Notis create a corresponding Harvest project after confirming the client match and project details.
When Linear project properties change, have Notis find the related Harvest project and report its details for a focused alignment check.
When a Linear project update is posted, have Notis retrieve time entries for the related Harvest project and report a concise hours summary.
When a Linear comment explicitly states completed work and a duration, have Notis create a Harvest time entry from that clear instruction.
When a Linear issue update indicates a newly named work category, have Notis create a matching Harvest task when the project match is clear.
When a new Linear issue documents a project expense with a clear amount and category, have Notis create a Harvest expense entry for review.
When a Linear issue changes, have Notis retrieve the related Harvest project details so the issue's tracking context is easy to review.
Notis builds workflows that link Linear to Harvest. A trigger fires from one place; an action lands in another.
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create a client record.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a contact to an existing client.
Triggers when a new comment is received.
Create an estimate for a client.
Triggers when a new issue is created.
Create a category for estimate items.
Triggers when an issue is updated, such as when its labels or status change.
Add a message to an estimate or trigger an estimate event.
Fires when a comment is posted on an issue in a private Linear team.
Record an expense against a project.
Fires when an issue is created in a private Linear team.
Create an invoice for a client.
Fires when an issue’s properties change in a private Linear team.
Create a category for invoice items.
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.
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ apps can start a workflow.
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
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.
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.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
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:
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.
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 monthWhatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
Every step can include an LLM call: summarise, classify, extract, rewrite.
Every run, every step, every input, all replay-able from Mission Control.
Pause for approval. Notis pings you in chat with one-tap approve.
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Linear and Harvest, or any other combination from 1,600+ integrations.
When this happens · Trigger
Do this · Action
7-day trial of any paid plan, with $20 of usage included.
No card. Works with personal or business Harvest.