Respond to Urgent Feedback with Complete Context
Every urgent response includes the full story.
Trigger
Comment Received Trigger
Triggered when a comment is received.
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 urgent comment comes in from a frustrated customer. You respond quickly, but you don't know they've already received three similar messages this month. Your response ignores the real problem.
- Understand the full context before responding to urgent comments
- Avoid tone-deaf responses when customers are frustrated
- Reduce response cycles by addressing root causes
- Build trust through contextually aware support
Setup
Build it in a few focused steps.
- 1Connect Linear and Amcards to Notis.
- 2Tell Notis: 'When an urgent comment is received on a Linear issue, show me the campaign history from Amcards.' Set up in Automations.
- 3Filter for urgent comments (use keywords like 'urgent', 'ASAP', or escalation markers).
- 4Get notified immediately via Slack or email with the customer's campaign history so you can craft a smart response.
- 5Test by adding an urgent comment to a Linear issue and verify the campaign history arrives instantly.
Questions about this workflow
How does Notis identify urgent comments?
You can set keywords (urgent, ASAP, crisis) or markers. Notis will alert you when these appear in comments.
What if there's no campaign history?
Notis will note that this is a fresh contact, giving you important context for your response.
Can this trigger auto-pausing of campaigns?
Yes. Ask Notis to auto-pause all campaigns to urgent contacts while you investigate and respond.
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.