Subscription Cycles Align with Linear Sprints
When a subscription starts, Notis aligns it with your Linear cycle (sprint), so your product and support teams can plan support, features, and escalation response around the customer's billing period.
Trigger
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Action
Get cycles by team ID
Retrieves all cycles for a specified linear team id; cycles are time-boxed work periods (like sprints) and the team id must correspond to an existing team.
Why this helps
Subscriptions and sprints don't align. You don't know which subscribers are in which sprints, so you miss the chance to plan support and features alongside subscription onboarding.
- Plan support and feature work aligned with subscription billing cycles
- Your team sees which subscriptions matter in the current sprint
- Reduce surprises—anticipate support load based on subscription cohorts
- Better sprint planning with subscription context
Setup
Build it in a few focused steps.
- 1Connect Stripe and Linear to Notis.
- 2Create an automation: 'Subscription Cycle Sync'.
- 3Prompt: 'When a subscription is added in Stripe, retrieve the related team's Linear cycles and find the one that matches the subscription start date. Add a note to the subscription issue with the cycle name and end date so planning is coordinated.'
- 4Set the trigger to 'Subscription Added Trigger'.
- 5Test by creating a subscription and verifying cycle info appears.
Questions about this workflow
How does Notis know which team to check cycles for?
Tell it in your prompt (e.g., 'check the Support team's cycles' or 'match by customer region'). You define the logic.
What if the subscription doesn't match any cycle?
Ask Notis to create a note saying no matching cycle was found, or assign it to the next upcoming cycle.
Can I automatically add subscriptions to the cycle?
Yes—ask Notis to create a sub-task or label on the cycle issue for tracking.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Linear. A trigger fires from one place; an action lands in another.
Stripe triggers
Linear actions
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create linear attachment
Creates a new attachment and associates it with a specific, existing linear issue.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Create a comment
Creates a new comment on a specified linear issue.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Create linear issue
Creates a new issue in a specified linear project and team, requiring a title and description, and allowing for optional properties like assignee, state, priority, cycle, and due date.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Get create issue default params
Fetches a linear team's default issue estimate and state, useful for pre-filling new issue forms.
Product Created Trigger
Triggered when a product is created in Stripe
Create a label
Creates a new label in linear for a specified team, used to categorize and organize issues.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Delete issue
Archives an existing linear issue by its id, which is linear's standard way of deleting issues; the operation is idempotent.
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Get all teams
Retrieves all teams from the linear workspace without requiring any parameters.
Download issue attachments
Downloads a specific attachment from a linear issue; the `file name` must include the correct file extension.
Connect any two apps with Notis in the middle.
Not just Stripe and Linear. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Linear.