End Every Sprint With Team Celebration
Sprints end and teams jump immediately to the next one. No pause for celebration, no acknowledgment of effort. Notis marks sprint ends with cat-based celebration content - giving your team permission to recover and feel the work they did.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Get Portals
Tool to list all portals. use when you need to browse portal metadata with pagination after authentication.
Why this helps
Sprints close invisibly. No ritual completion means no recovery time. Teams run in continuous depleted mode.
- Create a ceremonial sprint closure
- Build team recovery time into the sprint rhythm
- Acknowledge collective effort and achievement
Setup
Build it in a few focused steps.
- 1Connect Linear and Cats to your Notis account.
- 2Create a 'Scheduled (Cron)' automation for your sprint end day at 5:00 PM (typically Friday).
- 3Enter the instruction: 'Every sprint end, fetch celebratory cat content and post it to our team channel to mark the sprint closure and celebrate our work.'
- 4Route to your team channel (#engineering, #product, #all-hands) for maximum visibility.
- 5Test by running it manually before the actual sprint end to ensure the celebration message lands properly.
Questions about this workflow
Can I customize this for different teams?
Yes. Create multiple automations - one for engineering, one for design, etc., each posting to their respective channels.
What if our sprints don't end on Fridays?
Set the cron schedule to whatever day your sprints actually end - Monday, Wednesday, whatever works for your team.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Cats. A trigger fires from one place; an action lands in another.
Linear triggers
Cats actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Portals
Tool to list all portals. use when you need to browse portal metadata with pagination after authentication.
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 Cats, 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 Cats.