Prevent Campaign Conflicts During High-Priority Issues
Stop sending promo messages to customers in crisis.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
You mark an issue urgent, but there's already a campaign running to that customer. You don't know until they complain about conflicting messages or bad timing.
- Prevent tone-deaf outreach during customer issues
- Automatically flag active campaigns for pausing
- Reduce customer frustration from mixed signals
- Maintain message consistency during crises
Setup
Build it in a few focused steps.
- 1Ensure Linear and Amcards are connected to Notis in your portal.
- 2Tell Notis: 'When a Linear issue priority changes to urgent or high, check what campaigns are active to that contact in Amcards.' Set this up conversationally or in the portal.
- 3Select 'Issue Updated' as the trigger and specify that you want it to fire on priority changes.
- 4Get notified via your preferred channel (Telegram, Slack, email) with the list of active campaigns so you can pause if needed.
- 5Test by changing an issue to urgent in Linear and confirm the active campaigns are returned.
Questions about this workflow
Will this pause campaigns automatically?
No, Notis checks and alerts you. You can then manually pause campaigns or ask Notis to pause them based on a rule you set.
Does this work for all priority levels?
Yes. You can customize it to trigger on any priority change (urgent, high, etc.) or only the ones that matter most to you.
What if there are no active campaigns?
Notis will notify you that no campaigns are running, so you know it's safe to respond without conflicts.
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.