Trigger incident response documentation via webhook
When incidents occur, critical response documentation doesn't exist; teams scramble to create templates during high-stress situations. This webhook creates them instantly.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create a page
Create a new page in a doc. note that creating a page requires you to be a doc maker in the applicable workspace.
Why this helps
When incidents occur, critical response documentation doesn't exist; teams scramble to create templates during high-stress situations.
- Automatically creates incident response documentation when triggered
- Provides structure during crisis situations
- Creates an audit trail of incident management
Setup
Build it in a few focused steps.
- 1Create an incident response template in Coda with sections for impact, timeline, root cause, and resolution.
- 2Connect your Coda workspace to Notis.
- 3Ask Notis: 'Create a webhook that creates an incident response page in Coda whenever I send a request with incident details'.
- 4Notis will generate a webhook URL for your incident response system.
- 5Test by triggering the webhook and verifying an incident response page is created.
Questions about this workflow
Can I send incident details via the webhook?
Yes. You can send incident severity, affected systems, and other details, and Notis will populate them in the response document.
Can this escalate notifications to the team?
Yes. You can ask Notis to notify your team in Slack or another channel when an incident response is created.
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.