Include New Stakeholders When Project Scope Grows
Scope grows. Your stakeholder list grows with it.
Trigger
Project Properties Updated
Fires when properties on a Linear project change (status, lead, target date, priority, etc.). Covers projects in both public and private teams — polls with the connected user's token.
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
A project's scope expands mid-stream, but you don't realize a new department or partner should be involved. Weeks later, they're upset they weren't included.
- Identify new stakeholders when scope changes
- Reduce missed stakeholder inclusion
- Speed up stakeholder onboarding
- Keep all relevant people in the loop automatically
Setup
Build it in a few focused steps.
- 1Connect Linear and Amcards to Notis.
- 2Ask Notis: 'When a project scope or key properties change in Linear, get the updated stakeholder list from Amcards.' Set up in Automations.
- 3Set the trigger to 'Project Properties Updated' and filter for scope-related fields.
- 4Get notified with new stakeholders so you can include them in ongoing communications.
- 5Test by expanding a project scope in Linear and verify new stakeholders are identified and returned.
Questions about this workflow
How does Notis identify new stakeholders for expanded scope?
Notis matches the expanded scope details to stakeholder profiles in Amcards (by department, expertise, or tags you specify).
What if a stakeholder is missing?
You can manually add them or refine Notis' matching criteria to find similar people next time.
Can I auto-add new stakeholders to a campaign?
Yes. Ask Notis to automatically enroll new stakeholders in a welcome or update campaign.
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.