Link Your Performance to Your Environment
When you create a retrospective issue, Notis logs the current conditions. Over time, you'll see which environments led to great sprints and which ones held you back.
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
Get Devices
Tool to retrieve a list of user's ambient weather devices with their most recent data. use when you need to list your stations and view their latest readings.
Why this helps
Neurodivergent founders often can't explain why some sprints went well and others flopped. Environmental factors (seasonal changes, weather, light, temperature) play a huge role but are never tracked.
- Automatically capture environmental context at retro time
- Build a dataset linking environment to performance
- Make better sprint plans based on actual environmental data
Setup
Build it in a few focused steps.
- 1Connect both Ambient Weather and Linear integrations to Notis.
- 2Create an automation: When a retrospective or retro issue is created, fetch current ambient conditions and log them.
- 3Set up in Automations or ask Notis to create this automation.
- 4Use Issue Created as the trigger, filtering for retro or retrospective labels.
- 5Test by creating a retro issue and verifying conditions are logged.
Questions about this workflow
What conditions should I track for retros?
Temperature, humidity, light level, air quality, and season. Over many retros, you'll see if winter sprints are slower or summer sprints faster.
Can I track the whole sprint's weather, not just retro day?
Yes - set up an automation to log conditions daily during the sprint, then aggregate them in the retro.
How does this help future sprints?
If data shows you always perform well in fall, you can plan ambitious sprints for fall. If summer is consistently harder, you can adjust expectations.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Ambient weather. A trigger fires from one place; an action lands in another.
Linear triggers
Ambient weather actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Devices
Tool to retrieve a list of user's ambient weather devices with their most recent data. use when you need to list your stations and view their latest readings.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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 Ambient weather, 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 Ambient weather.