Keep Private Issues Safe from Campaign Conflicts
Sensitive discussions stay protected.
Trigger
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Action
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.
Why this helps
Your team is handling a sensitive customer issue in a private Linear team, but you don't know if a campaign is running to that customer. Confidentiality feels compromised.
- Protect sensitive issues from campaign conflicts
- Maintain confidentiality across tools
- Ensure no public messaging reaches confidential contacts
- Reduce risk of accidental disclosure
Setup
Build it in a few focused steps.
- 1Connect Linear (with private team access) and Amcards to Notis.
- 2Tell Notis: 'When an issue updates in my private Linear team, check what campaigns are active to that contact in Amcards.' Set up in Automations.
- 3Set the trigger to 'Private Team Issue Properties Updated.'
- 4Route alerts to a private channel or direct message so only authorized people see campaign details.
- 5Test by updating a private team issue and verify campaign details are delivered securely to authorized members only.
Questions about this workflow
Will this expose private information?
No. Notifications go only to authorized team members in private channels, maintaining confidentiality.
Can I auto-pause campaigns when private issues are flagged?
Yes. Ask Notis to create a rule that automatically pauses or adjusts campaigns based on private issue activity.
What if the contact has no active campaigns?
Notis will confirm that no campaigns are running, giving you confidence the discussion is truly private.
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.