Auto-pull Customer Context When Support Issues Arrive
See the full customer picture instantly -- no tab-switching required.
Trigger
Issue Created Trigger
Triggered when a new issue is created.
Action
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.
Why this helps
You jump between Linear and Amcards every time a new issue arrives, hunting for customer context. Each handoff drains focus and slows your response time.
- No tab-switching between tools
- Respond faster with complete customer history
- Reduce time spent searching for contact details
- Never miss a customer detail again
Setup
Build it in a few focused steps.
- 1Connect your Linear and Amcards accounts to Notis via the portal -- this is a one-time step.
- 2Ask Notis: 'When a new Linear issue is created, get the customer contact info from Amcards.' Or create it in the portal under Automations > New Automation.
- 3Set the trigger to 'Issue Created.' Notis will automatically match the issue to the right contact in Amcards.
- 4Choose where to receive notifications (Telegram, Slack, or email) so you're alerted with the contact details.
- 5Test it by creating a sample issue in Linear and verifying the contact info arrives in your chosen channel.
Questions about this workflow
How does Notis know which contact to pull?
Notis reads the issue details (customer name, email, or company) and matches it to contacts in your Amcards database.
What if the customer isn't in Amcards yet?
Notis will notify you that no match was found. You can add them manually or ask Notis to create a new contact record in Amcards.
Can I customize which fields I see?
Yes. Ask Notis to prioritize specific fields like email, phone, or company info so you get the most relevant details instantly.
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.