Keep Campaigns in Sync with Issue Priorities
Priorities shift. Your outreach follows.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
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
An issue's priority changes several times as the situation evolves. But your campaign stays on its original timeline. You're sending the wrong message at the wrong moment.
- Automatically verify campaign alignment with issue priorities
- Reduce manual intervention in priority shifts
- Stay responsive to changing customer needs
- Maintain message relevance throughout the customer journey
Setup
Build it in a few focused steps.
- 1Connect Linear and Amcards to Notis.
- 2Ask Notis: 'Whenever a Linear issue priority changes, check what campaigns are running to that customer in Amcards.' Set up via chat or portal.
- 3Set the trigger to 'Issue Properties Updated' and specify priority changes.
- 4Route alerts to your team channel so campaign and priority info reaches the right people.
- 5Test by changing an issue's priority in Linear and confirm campaign details arrive in your notification.
Questions about this workflow
Will this change my campaigns automatically?
No, it alerts you to the priority change and shows active campaigns. You decide whether to pause, adjust, or continue them.
How often can priorities change before it's overwhelming?
Notis batches alerts intelligently. You'll never be flooded -- each alert includes the most recent priority shift.
Can I set priority-based campaign rules?
Yes. Ask Notis to create rules like 'auto-pause all campaigns if priority is critical' or similar logic.
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.