Preserve Campaign Context When Issues Close
Nothing disappears. Everything documents itself.
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 closes and you lose track of what campaigns were running during that customer interaction. Months later, you can't remember what you sent them when.
- Automatically archive campaign context when issues close
- Build a searchable record of customer interactions
- Reduce manual documentation work
- Support audits and compliance reporting with complete history
Setup
Build it in a few focused steps.
- 1Connect Linear and Amcards to Notis.
- 2Tell Notis: 'When a Linear issue is closed, get the campaign history from Amcards and archive it with the issue.' Set up in Automations.
- 3Set the trigger to 'Issue Updated' and filter for closed or resolved status.
- 4Notis can add a comment to the closed issue with campaign details or archive to a backup channel.
- 5Test by closing a sample issue in Linear and verify campaign context is captured and archived.
Questions about this workflow
Where is the archive stored?
Notis can add it as a comment to the closed issue in Linear or save it to a dedicated archive channel in Slack or email.
Can I search archived campaigns later?
Yes. If archived in Linear, you can search issue comments. If archived elsewhere, check your preferred channel.
Does this affect closed issues in Linear?
No. Notis only reads data and adds optional comments. Closed issues remain unchanged.
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.