Escalate Issues with Complete Campaign Context
Every escalation includes the full customer story.
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
An issue gets escalated to a manager or lead, but they don't know what campaigns that customer has received. Critical context is missing from the handoff.
- Escalations include full customer outreach history
- Reduce rework and redundant investigation
- Speed up escalation resolution with complete context
- Improve handoff quality across teams
Setup
Build it in a few focused steps.
- 1Connect Linear and Amcards integrations to Notis.
- 2Ask Notis: 'When a Linear issue is escalated, get the campaign history from Amcards and include it in the escalation.' Set up via chat or the portal.
- 3Set the trigger to 'Issue Updated' and specify that it should fire when an issue is marked for escalation.
- 4Route notifications to your escalation channel (Slack, email, or Telegram) so context is delivered alongside the issue.
- 5Test by escalating a sample issue in Linear and verify the campaign history arrives in your notification.
Questions about this workflow
What if there's no campaign history?
Notis will note that no prior campaigns were sent to this customer, giving context to the escalation team.
Can I add this context directly to the Linear issue?
Yes. Ask Notis to add a comment to the issue with the campaign history automatically.
Does this slow down escalations?
No. This happens in seconds and is delivered alongside the escalation, speeding up the overall process.
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.