Start a document automation for each new project
When a Linear project is created, set up a Docsautomator automation for its recurring project documents, such as status briefs or handoff packets.
When something happens in Linear, Notis takes the next step in Docsautomator. 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
Creates an automation in test mode, where documents are watermarked and free.
When a Linear project is created, set up a Docsautomator automation for its recurring project documents, such as status briefs or handoff packets.
When a Linear project changes, have Notis update the relevant Docsautomator automation settings to reflect the new project requirements described in the change.
When a Linear project update is posted, retrieve the Docsautomator automation list so the run can report the relevant document workflow context alongside the update.
When a Linear issue is created to request document automation work, list Docsautomator automations so the team can identify an existing workflow before starting another.
When a Linear issue is updated, retrieve details for the related Docsautomator automation so the requester can compare its current setup with the changed requirement.
When a Linear comment clearly requests a Docsautomator automation change, have Notis update the named automation settings from the instruction.
When a Linear project update is posted, retrieve details for its related Docsautomator automation so the project lead can check that the document process still fits.
Have Notis retrieve Docsautomator queue statistics on a recurring schedule and report whether pending document work needs attention.
On a recurring schedule, retrieve the Docsautomator automation list and share a concise inventory for planning or housekeeping.
Notis builds workflows that link Linear to Docsautomator. 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.
Creates an automation in test mode, where documents are watermarked and free.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Permanently deletes an automation and all associated data; this cannot be undone.
Triggers when a new comment is received.
Duplicates an automation in test mode, where documents are watermarked and free.
Triggers when a new issue is created.
Retrieves details about an automation, including its configuration and template.
Triggers when an issue is updated, such as when its labels or status change.
Retrieves current document generation queue statistics for the workspace.
Triggers when a comment is posted on an issue in a private team.
Lists automations in the workspace with their basic details.
Triggers when an issue appears in a private team.
Lists signing sessions.
Triggers when an issue's properties change in a private team.
Sends a test email with a sample PDF attachment to check email delivery.
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,500+ 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 Docsautomator, or any other combination from 1,500+ 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 Docsautomator.