Auto-generate sprint planning document on schedule
Sprint planning requires manual setup every cycle; teams forget to prepare and planning becomes chaotic. This automation generates the template on schedule.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Copy Document
Creates a copy of an existing coda document. this action allows you to duplicate a document while optionally specifying a new title and location for the copied document.
Why this helps
Sprint planning documents require manual setup every cycle; teams forget to prepare and planning becomes chaotic or gets skipped.
- Automatically generates a sprint planning document on a fixed schedule
- Removes friction from planning cycle startup
- Standardizes sprint structure across your organization
Setup
Build it in a few focused steps.
- 1Create a sprint planning template in Coda with sections for goals, capacity, risks, and deliverables.
- 2Connect your Coda workspace to Notis.
- 3Tell Notis: 'Every two weeks on Monday morning, copy my sprint planning template in Coda for the upcoming sprint'.
- 4Select a bi-weekly trigger on your preferred day and time.
- 5Test by having Notis generate a test sprint planning document.
Questions about this workflow
Can I change the sprint schedule?
Absolutely. You can ask Notis to run on any schedule - weekly, every two weeks, monthly, or even bi-weekly on different days.
Can the template include links to the backlog?
Yes. Your sprint planning template can include references to your backlog, capacity calculations, or any other resources your team needs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Coda. A trigger fires from one place; an action lands in another.
Linear triggers
Coda actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a category for pack
Add a publishing category for a given pack.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add a maker for pack
Set a maker for a given pack. used to display makers for a pack in the corresponding packs page.
Comment Received Trigger
Triggered when a comment is received.
Add a permission for pack
Create or modify user, workspace, or global permissions for a given pack.
Issue Created Trigger
Triggered when a new issue is created.
Add custom domain
Add a custom domain to a published doc.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Add permission
Adds a new permission to the doc.
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).
Begin content export
Initiate an export of content for the given page.
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Content export status
Check the status of a page content export
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Copy Document
Creates a copy of an existing coda document. this action allows you to duplicate a document while optionally specifying a new title and location for the copied document.
Connect any two apps with Notis in the middle.
Linear and Coda, 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 Coda.