Skip to content
Notis

Connect Linear to Docmosis

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.

Examples

Ways Notis can move work from Linear to Docmosis

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.

Check template structure for a document issue

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.

Verify a template after a task update

When a Linear issue update signals a template upload or revision, retrieve Docmosis template details to check its stored metadata and error status.

Check batch upload progress from Linear

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.

Add render activity context to a project update

When a Linear project status update is posted, retrieve Docmosis render tag statistics to give document-heavy project updates relevant activity context.

Check render queue when a project changes

When a Linear project property changes during document-heavy work, retrieve Docmosis render queue utilization so the team can see current capacity.

Check Docmosis readiness for a new project

When a Linear project is created for document generation work, check whether the Docmosis environment is ready and within quota.

Review Docmosis environment context on project change

When a Linear project property changes, retrieve the Docmosis environment summary to keep service status, plan, and quota context close to planning updates.

Get sample data for a new template task

When a new Linear issue asks for Docmosis template testing, generate sample data from the template structure to give the task owner test input.

Supported Triggers and Actions

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

Linear triggers

Docmosis actions

Recurring trigger

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

TriggerScheduled

Docmosis: Delete Image(s)

Delete one or more stored images.

ActionInstant

Webhook trigger

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

TriggerInstant

Docmosis: Delete Template(s)

Delete one or more templates from the environment.

ActionInstant

Comment Received Trigger

Triggers when a new comment is received.

TriggerInstant

Docmosis Environment Ready

Checks whether a Docmosis environment is ready to handle document requests.

ActionInstant

Issue Created Trigger

Triggers when a new issue is created.

TriggerInstant

Docmosis Environment Summary

Retrieve the environment’s status, plan, and quota summary.

ActionInstant

Issue Updated Trigger

Triggers when an issue is updated, such as when its labels or status change.

TriggerInstant

Docmosis: Get API Key

Retrieves the Docmosis API access key from connection metadata.

ActionInstant

Private Team Comment Created

Fires when a comment is posted on an issue in a private Linear team.

TriggerPolling

Get Batch Upload Status

Check the progress or completion status of a template batch upload.

ActionInstant

Private Team Issue Created

Fires when an issue is created in a private Linear team.

TriggerPolling

Download Docmosis Images

Downloads up to 100 stored Docmosis images per request.

ActionInstant

Private Team Issue Properties Updated

Fires when an issue’s properties change in a private Linear team.

TriggerPolling

Get Docmosis Render Queue

Retrieve the current render queue status and usage.

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,600+ 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

Scheduled triggers

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.

Daily · 8:00Weekdays onlyOnce · Dec 13
Beta

Database triggers

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.

Row addedProperty editedValue > limit
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.

Notis

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.

  • 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

All12Manager5Telegram1Messages0WhatsApp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything 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.

Related pairs

More ways to connect Linear and Docmosis

Connect any two apps with Notis in the middle.

Linear and Docmosis, or any other combination from 1,600+ 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 Docmosis.