Align Campaigns with Issue Labels and Classifications
Labels change. Campaigns stay relevant.
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 gets labeled as a beta feature or known issue, but you're still sending regular campaign messages. Your outreach feels tone-deaf to the actual situation.
- Automatically verify campaigns when issue labels change
- Keep outreach relevant to issue status
- Reduce tone-deaf messaging based on stale labels
- Build responsive customer communication
Setup
Build it in a few focused steps.
- 1Connect Linear and Amcards to Notis.
- 2Tell Notis: 'When a Linear issue label changes, check what campaigns are active to that contact in Amcards.' Set up in Automations.
- 3Set the trigger to 'Issue Properties Updated' and filter for label changes.
- 4Get notified with the new label and active campaigns so you can decide if adjustments are needed.
- 5Test by adding a label to an issue in Linear and verify campaign status is retrieved.
Questions about this workflow
Which labels should trigger this?
You decide. Set up triggers for specific labels (beta, known-issue, high-priority, etc.) or all label changes.
Can I auto-adjust campaigns based on labels?
Yes. Ask Notis to create rules like 'pause campaigns if label = beta' or 'prioritize if label = critical'.
What if multiple labels change at once?
Notis will alert you with all label changes and active campaigns so you have the full picture.
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.