Route location events into a map automatically
When another system sends Notis a location event, the workflow can put its useful geographic context on the right map.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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
Location events from other systems can require manual copying before anyone can see them in context.
- Bring external location events into a spatial view.
- Reduce copy-and-paste between systems.
- Make new geographic information easier to share with the team.
Setup
Build it in a few focused steps.
- 1Connect Felt to Notis once in the portal.
- 2Create an automation with one plain-language instruction to add or update relevant map elements from incoming location events.
- 3Select the incoming webhook trigger and use the webhook endpoint from Notis in the sending system.
- 4Choose a channel for run reports and test with one safe sample event.
Questions about this workflow
Does Linear start this workflow?
No. It starts when an external tool or custom backend sends a request to the Notis webhook.
What does the Felt action need?
It updates elements on a specified map using geographic features supplied or interpreted from the event context.
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.