Know Your Active Campaigns Before Each Response
Don't accidentally message twice.
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
A customer comments on an issue. You respond thoughtfully. Meanwhile, an automated campaign sent them a similar message yesterday. You don't realize you're repeating yourself.
- See all active campaigns before responding to comments
- Avoid accidental duplicate messaging
- Tailor your response based on what they've already received
- Build genuine customer relationships with clear communication
Setup
Build it in a few focused steps.
- 1Connect Linear and Amcards to Notis in the portal.
- 2Ask Notis: 'When someone comments on a Linear issue, show me the active campaigns to that contact in Amcards.' Set it up in plain language or via the portal.
- 3Set the trigger to 'Comment Received.' Notis will pull the contact's active cards each time.
- 4Choose your notification channel (Telegram, Slack, email) to get instant alerts with campaign details.
- 5Test it by having a team member comment on an issue and verify you receive the active campaign list.
Questions about this workflow
Will this work for internal team comments only?
You can customize it. Filter for customer comments only or include all comments -- tell Notis your preference.
What counts as an active campaign?
Notis pulls all cards/campaigns currently in flight to that contact. You can refine this to include only certain campaign types if needed.
Can I use this to auto-suggest responses?
Notis can show you the campaign context. From there, you can ask Notis to draft a response that acknowledges what they've already received.
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.