Decisions Documented, Not Lost
Technical decisions trigger your architecture partner to capture tradeoffs and reasoning, so future context-rebuilding never happens
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
Get Public Character By ID
Tool to retrieve a public character by its id. use when you need to fetch details of a single public character by providing its unique id.
Why this helps
Technical decisions live in comments; rationale gets lost when context resets or team changes
- Decision rationale persists even after people leave
- Future decisions reference past logic without rework
- Tradeoffs stay visible instead of forgotten
- Onboarding becomes reading, not reverse-engineering
Setup
Build it in a few focused steps.
- 1Connect Linear and Chatfai to Notis (one-time setup)
- 2Create new automation: 'Technical Decision Capture'
- 3Prompt: 'When an issue in Linear involves a technical decision, engage my architecture partner. Have them document the decision, capture tradeoffs considered, and note the rationale for this choice over alternatives.'
- 4Trigger: 'Issue Created' from Linear
- 5Test by creating an architecture issue and reviewing the documentation session
Questions about this workflow
How does the partner identify technical decisions?
Your prompt tells them to focus on architecture or technical-decision issues. Mentioning your typical decision topics helps Notis recognize them reliably.
Can the documentation go into a shared space?
Yes. Your prompt can direct your partner to format decisions for your documentation system, and Notis can push them to your wiki or docs site.
What if the decision changes later?
Documenting the original reasoning makes changes easier to justify and understand. Your partner can update documentation when decisions shift.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Chatfai. A trigger fires from one place; an action lands in another.
Linear triggers
Chatfai actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Public Character By ID
Tool to retrieve a public character by its id. use when you need to fetch details of a single public character by providing its unique id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Comment Received Trigger
Triggered when a comment is received.
Issue Created Trigger
Triggered when a new issue is created.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear and Chatfai, or any other combination from 1,000+ 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 Chatfai.