Refresh participant context from Feathery when Linear changes
When a participant issue changes, have Notis retrieve the relevant Feathery user data so follow-up can start with current context.
Trigger
Public Team Issue Properties Updated
Fires when properties on a *public-team* Linear issue change (status, assignee, priority, labels, etc.). For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_PROPERTIES_UPDATED`.
Action
Get All User Data
Tool to retrieve all stored data fields for a user. Use when you need to fetch all field entries associated with a specific user.
Why this helps
Owners may act on old notes when the latest form information sits in a separate user record.
- Bring current user fields into a changing support issue.
- Reduce repeated record lookups.
- Make follow-up more grounded in the participant's latest information.
Setup
Build it in a few focused steps.
- 1Connect Linear and Feathery to Notis once through the portal.
- 2Create a portal automation or describe the context refresh to Notis.
- 3Write one plain-language instruction asking Feathery for all stored data for the user in a relevant updated issue.
- 4Choose the Linear Issue Properties Updated trigger and a run-report channel.
- 5Test with one participant issue and verify the returned user's identity.
Questions about this workflow
What does the action return?
It retrieves all stored data fields associated with a specified Feathery user.
How can I avoid unrelated lookups?
State which participant issues should trigger the lookup in the instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Feathery. A trigger fires from one place; an action lands in another.
Linear triggers
Feathery actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Edit Feathery Account
Tool to edit an existing account’s role and permissions. Use when modifying account settings after confirming identity.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Account Info
Tool to get your Feathery team name and list of accounts. Use when you need to fetch your team's account info.
Comment Received Trigger
Triggered when a comment is received.
Fill or sign document template
Tool to fill or sign a Feathery document template. Use when you need to generate a completed or signed document file after mapping template fields.
Issue Created Trigger
Triggered when a new issue is created.
List Document Envelopes
Tool to list generated document envelopes by document or user ID. Use when you need to retrieve envelope records for auditing or tracking.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Create hidden field
Tool to create a new hidden field in a form. Use when you need to add a non-visible field after confirming you have a unique field_id.
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).
Delete Form
Tool to delete an existing form. Use when you need to permanently remove a form after confirmation.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Get form schema
Tool to retrieve the schema of a specific form. Use after confirming the form ID.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
List Forms
Tool to list all forms in your Feathery account. Use when you need to view or filter available forms.
Connect any two apps with Notis in the middle.
Linear and Feathery, 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 Feathery.