Generate a Feathery document from a Linear issue
When a Linear issue captures a document request, use Feathery to fill the relevant document template and create a completed file.
Connect Linear to Feathery
When something happens in Linear, Notis takes the next step in Feathery. 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
Edit an account’s role and permissions.
Examples
Ways Notis can move work from Linear to Feathery
Check document envelopes when a Linear issue changes
When a Linear issue is updated, have Feathery list relevant document envelopes so the team can check document progress without hunting through tools.
Fetch the Feathery form schema for a new Linear request
When a Linear issue requests work on a Feathery form, retrieve its schema to give the request owner concrete structure to review.
Retrieve Feathery user data after a Linear comment
When a Linear comment asks for a Feathery user-data check, retrieve the user's stored fields so the discussion can move forward with context.
Check Feathery session progress when an issue changes
When an issue about a form participant is updated, retrieve the relevant Feathery session progress to keep follow-up grounded in current completion state.
List Feathery forms for a new Linear form task
When a form task is created in Linear, retrieve the available Feathery forms to help the requester identify the right starting point.
Check Feathery connector errors after a Linear issue update
When an integration-related Linear issue changes, retrieve recent Feathery API connector errors for the named form to speed up troubleshooting.
Check Feathery email issues from a Linear comment
When a Linear comment reports a form email delivery problem, retrieve Feathery bounce and complaint events to guide the next investigation step.
Find Feathery users for a private Linear request
When a private-team issue changes to request a user lookup, search Feathery users using the request context to help resolve the case.
Supported Triggers and Actions
Notis builds workflows that link Linear to Feathery. A trigger fires from one place; an action lands in another.
Linear triggers
Feathery actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
TriggerScheduled
Edit Feathery Account
Edit an account’s role and permissions.
ActionInstant
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
TriggerInstant
Get Account Info
Retrieve the team name and account list.
ActionInstant
Comment Received Trigger
Triggers when a new comment is received.
TriggerInstant
Fill or sign document template
Fills a Feathery document template and can route it to an email address for signature.
ActionInstant
Issue Created Trigger
Triggers when a new issue is created.
TriggerInstant
List Document Envelopes
List generated document envelopes for auditing or tracking.
ActionInstant
Issue Updated Trigger
Triggers when an issue is updated, such as when its labels or status change.
TriggerInstant
Create hidden field
Creates a hidden field in Feathery using a deprecated endpoint.
ActionInstant
Private Team Comment Created
Triggers when a comment is posted on an issue in a private team.
TriggerPolling
Delete Form
Permanently delete a form; this action is irreversible.
ActionInstant
Private Team Issue Created
Triggers when an issue appears in a private team.
TriggerPolling
Get form schema
Retrieves a Feathery form’s schema, including its steps, fields, rules, integrations, and translations.
ActionInstant
Private Team Issue Properties Updated
Triggers when an issue's properties change in a private team.
TriggerPolling
List Forms
List all forms in the account.
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,500+ 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.
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 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.
Related pairs
More ways to connect Linear and Feathery
Connect any two apps with Notis in the middle.
Linear and Feathery, or any other combination from 1,500+ 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 Feathery.