Keep Private Issues Contextualized and Organized
Sensitive topics stay private. Context stays clear.
Trigger
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Action
Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
Why this helps
Sensitive customer or internal issues land in a private Linear team, but you lose the contact context because you're siloing the data. Context and privacy become opposing forces.
- Maintain full context within private teams
- Keep sensitive issues organized without losing details
- Ensure privacy and information access align
- Reduce silos between private and standard workflows
Setup
Build it in a few focused steps.
- 1Connect Linear (with private team access) and Amcards to Notis.
- 2Tell Notis: 'When a new issue is created in my private Linear team, get the contact info from Amcards and keep it private.' Set up in Automations.
- 3Select 'Private Team Issue Created' as your trigger.
- 4Route notifications only to authorized team members via a private channel (secure Slack, direct message, or email).
- 5Test by creating a sample issue in a private team and verify only authorized users receive the contact details.
Questions about this workflow
How does Notis keep this private?
Notifications go only to channels you specify, and data is passed securely between Linear and Amcards via Notis' encrypted connection.
Can I restrict which contacts are visible?
Yes. Set up role-based rules so only authorized team members see certain contact details.
Does this work across multiple private teams?
Yes. Set it up once, and Notis will apply the rule to all private teams you're part of.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Amcards. A trigger fires from one place; an action lands in another.
Linear triggers
Amcards actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Cards
This tool retrieves a list of all cards associated with the authenticated account. the action is completely independent and doesn't require any external resource ids or parameters beyond authentication. it allows users to monitor, track, and manage their cards.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Contacts
This tool retrieves a list of contacts from amcards. it is used for managing contacts by providing details like limit, skip, and filters (e.g., last name, first name, email). the tool returns an array of contact objects containing fields such as id, first name, last name, email, created at, and updated at.
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 Amcards, 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 Amcards.