Give public location issues a shared spatial view
When a new public-team issue includes a real location, Notis can put it on the map for easier team follow-up.
Trigger
Public Team Issue Created
Fires when a new issue is created in a Linear *public* team. For private teams (lock icon in Linear's sidebar) use `LINEAR_PRIVATE_TEAM_ISSUE_CREATED`.
Action
Create or Update Elements
Tool to create new elements or update existing elements on a map via geojson featurecollection. use when you need to batch add or modify elements on a specified map after confirming the map id.
Why this helps
Geographic issues in a busy team queue can be hard to group by place and keep visible.
- See public-team location issues in geographic context.
- Make issue clusters easier to notice.
- Reduce manual map updates after issue creation.
Setup
Build it in a few focused steps.
- 1Connect Linear and Felt to Notis once in the portal.
- 2Create an automation with one plain-language instruction to add new location-based public-team issues to the right map.
- 3Select the Public Team Issue Created trigger.
- 4Choose a run-report channel and test with a public-team issue that has a usable location.
Questions about this workflow
Is this trigger for private teams?
No. It is for public-team issues; private-team issues have a separate trigger.
What if the issue has no usable location?
State in the prompt that Notis should add only issues with enough geographic information.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Felt. A trigger fires from one place; an action lands in another.
Linear triggers
Felt actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create or Update Elements
Tool to create new elements or update existing elements on a map via geojson featurecollection. use when you need to batch add or modify elements on a specified map after confirming the map id.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Project
Tool to create a new felt project. use when you need to initialize a project with a specific name, and optional description or organization context.
Comment Received Trigger
Triggered when a comment is received.
Delete Element
Tool to delete a specific element from a map. use when you have both map and element ids and need to remove the element permanently.
Issue Created Trigger
Triggered when a new issue is created.
Delete Layer
Tool to delete a specific layer from a map. use when you have the map's and layer's ids and need to remove it permanently.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Delete Map
Tool to delete a specific map. use when you have the map's id and want to permanently remove it. returns no content (http 204) on success.
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 Project
Tool to delete a project and all its contents. use when you need to permanently remove a project after confirmation.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Duplicate Map
Tool to duplicate an existing map in felt. use when you need a clone of a map as a starting point.
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Create Felt Project
Tool to create a new felt project. use when you need to initialize a project with a specific name and optional description or organization context.
Connect any two apps with Notis in the middle.
Linear and Felt, 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 Felt.