Find the right Docmosis template for a new request
When a Linear issue asks for a generated document, retrieve Docmosis templates so the team can quickly identify a suitable starting point.
When something happens in Linear, Notis takes the next step in Docmosis. 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
Delete one or more stored images.
When a Linear issue asks for a generated document, retrieve Docmosis templates so the team can quickly identify a suitable starting point.
For a new Linear issue about a Docmosis document, retrieve the template's parsed structure to make its fields, repeats, and conditions easier to review.
When a Linear issue update signals a template upload or revision, retrieve Docmosis template details to check its stored metadata and error status.
When a Linear issue is updated with a Docmosis batch upload in progress, retrieve the batch upload status to help the owner know whether to follow up.
When a Linear project status update is posted, retrieve Docmosis render tag statistics to give document-heavy project updates relevant activity context.
When a Linear project property changes during document-heavy work, retrieve Docmosis render queue utilization so the team can see current capacity.
When a Linear project is created for document generation work, check whether the Docmosis environment is ready and within quota.
When a Linear project property changes, retrieve the Docmosis environment summary to keep service status, plan, and quota context close to planning updates.
When a new Linear issue asks for Docmosis template testing, generate sample data from the template structure to give the task owner test input.
Notis builds workflows that link Linear to Docmosis. 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.
Delete one or more stored images.
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete one or more templates from the environment.
Triggers when a new comment is received.
Checks whether a Docmosis environment is ready to handle document requests.
Triggers when a new issue is created.
Retrieve the environment’s status, plan, and quota summary.
Triggers when an issue is updated, such as when its labels or status change.
Retrieves the Docmosis API access key from connection metadata.
Fires when a comment is posted on an issue in a private Linear team.
Check the progress or completion status of a template batch upload.
Fires when an issue is created in a private Linear team.
Downloads up to 100 stored Docmosis images per request.
Fires when an issue’s properties change in a private Linear team.
Retrieve the current render queue status and usage.
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 Docmosis, 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 Docmosis.