Better Stack and Granola AI Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Connect Better Stack to Granola AI on visual integration builder following simple steps below. When developer tools event fired from Better Stack, it will run actions inside Granola AI app - exactly how you set them in your ai automation. No coding skills required.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Better Stack and Granola AI
Detailed info you need to know about Better Stack and Granola AI integrations in WEXTL. Explore which modules apps support and how you connect them.
Better Stack

Uptime monitoring, incident management and status pages.[5]
Granola AI

AI meeting notepad to list notes and transcripts, watch note.generated and note.edited, and pull folders and audit events.[6]
How to connect Better Stack to Granola AI
Set up your Better Stack and Granola AI integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Better Stack and Granola AI
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected Better Stack and Granola AI nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Better Stack and Granola AI. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Better Stack and Granola AI work in WEXTL?
WEXTL exposes actions and triggers for Better Stack and Granola AI that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
Better Stack triggersGranola AI actions
Better Stack modules
- Change the Incident Status Moves an incident to a new state: Action offers Acknowledge, Resolve and Reopen. Use By to record who made the change. The updated incident is returned.
- Change the Role of a Team Member Gives an existing team member a different Role, taken from your list of roles. Use Member to say whose role changes.
- Create a Catalog Attribute Gives a catalog relation another attribute under a Name. Turn on Primary to match it against the incident metadata key of the same name, and give a Position to order it, lowest first.
- Create a Catalog Record Stores one record in a catalog relation. Fill Attributes with one row per attribute, each row holding its values.
- Create a Catalog Relation Defines a catalog relation under a Name, with an optional Description. Set Match Rule to apply a record when any primary value or every primary value matches the incident metadata.
- Create a Heartbeat Sets up a heartbeat that expects a ping every Expected Every seconds and counts one as missed after the Grace Period. Choose an Escalation Policy to decide who is alerted, or alert the on-call person with the e-mail, SMS or Call switches.
- Create a Heartbeat Group Starts a group for heartbeats under a Name. Sort it among the other groups with Position, or begin with every heartbeat inside it paused by using Paused.
- Create a Monitor Starts a monitor that checks a chosen Monitor Type against a URL or Host. Use Check Frequency and Regions to set how often and where it runs, and Escalation Policy to decide who is alerted.
- Create a Monitor Group Sets up a home for monitors under a Name. Turn on Paused to pause every monitor in that group.
- Create a Severity Defines a severity level that decides how people are notified when an incident of that level opens. Pick channels with Send SMS, Call, Send E-mail, Send Push Notification and Send Critical Alert, and file it under a Severity Group.
- Create a Severity Group Adds a named group for severities, shown in the dashboard. Use Position to order it in the list, lowest first.
- Create a Status Page Creates a status page for your company from a Company Name, Time Zone and Subdomain, which must be unique across Better Stack. Add a Custom Domain, a Design, History Days or a Password to shape who sees what.
- Create a Status Page Group Creates a named group for status pages, shown in the dashboard. Use Position to place it in the list.
- Create a Status Page Report Publishes a report with a Title and the first status update Message. Choose a Report Type, either a manual incident or planned maintenance, and turn on Notify Subscribers to e-mail them.
- Create a Status Page Resource Adds an item to a status page based on its Resource Type, shown there under the Public Name. Use Mark as Down When and Mark as Degraded When to define how an incident affects it.
- Create a Status Page Section Sets up a section for grouping the items of a status page. Leave Name blank to hide its header, and use Position with Fixed Position to place it exactly.
- Create a Status Page Subscriber Subscribes an E-mail address to the updates of a status page.
- Create a Status Update Posts a follow-up on a status page report with the text from Message. Use Affected Resources for a manual report and leave it out for maintenance. Turn on Notify Subscribers to send an e-mail.
- Create an Escalation Policy Group Makes a group for escalation policies, shown in the dashboard under its Name. Use Position to place it in the list, lowest first.
- Create an Incident Opens an incident on behalf of a Requester E-mail, described by its Summary. Add a Name, a longer Description and an Escalation Policy, or alert the on-call person with Send E-mail, Send SMS or Call.
- Create an Incident Comment Posts a Comment on an incident, with Markdown supported. Set Tag Member to notify a colleague about it. The new comment is returned.
- Create an Incoming Webhook Creates a webhook endpoint that raises incidents from outside requests. Give it a Name and an Escalation Policy, and set Recovery Period for how long to wait after a resolving request. Start, Acknowledge and Resolve rules decide when each happens.
- Create an On-Call Event Puts people on call for a stretch of time on a schedule, between Starts At and Ends At. Everyone chosen as On-Call Users must belong to the schedule team. Turn on Override so the event beats regular scheduled ones.
- Create an On-Call Rotation Rotates On-Call Users through a schedule, each person on call for the Rotation Length counted in the chosen Interval. Rotations run from Start At to End At. Use Working Hours to restrict when anyone is paged.
- Create an On-Call Schedule Creates a new on-call schedule under a Name, which can then hold events and rotations.
- Delete a Catalog Attribute Deletes an attribute that belongs to a catalog relation.
- Delete a Catalog Record Removes a record that belongs to one catalog relation.
- Delete a Catalog Relation Deletes a catalog relation, the set of attributes and records matched against incident metadata.
- Delete a Heartbeat Removes a heartbeat that expects regular pings.
- Delete a Heartbeat Group Deletes a group that can pause and organise heartbeats together.
- Delete a Monitor Deletes a monitor that checks a website, server or port.
- Delete a Monitor Group Removes a group that holds monitors and can pause them together.
- Delete a Severity Removes a severity level used to decide how people are notified of new incidents.
- Delete a Severity Group Deletes a dashboard group that holds severity levels.
- Delete a Status Page Removes the status page on which visitors check the health of your services. Check first, it is final.
- Delete a Status Page Group Deletes a dashboard group that collects status pages.
- Delete a Status Page Report Removes a report, either an incident or planned maintenance, from a status page.
- Delete a Status Page Resource Deletes an item from a status page, found by Status Page and Resource.
- Delete a Status Page Section Removes a section that groups the items of a status page.
- Delete a Status Page Subscriber Unsubscribes an e-mail address from the updates of a status page.
- Delete a Status Update Deletes one update that was posted under a status page report.
- Delete an Escalation Policy Removes an escalation policy, the setting that decides who gets alerted.
- Delete an Escalation Policy Group Deletes a dashboard group used to organise escalation policies.
- Delete an Incident Removes an incident from your Better Stack account. Plan on it being final.
- Delete an Incident Comment Deletes a note that was posted in the thread of an incident.
- Delete an Incoming Webhook Removes an incoming webhook that raises incidents from outside requests.
- Delete an On-Call Event Deletes a single on-call shift that was added to a schedule.
- Delete an On-Call Rotation Removes the rotation configured on an on-call schedule.
- Delete an On-Call Schedule Deletes an on-call schedule that people can be placed on through events and rotations.
- Get a Catalog Attribute Reads an attribute of a catalog relation, including whether it is primary and where it is positioned.
Granola AI modules
- Get a Note Reads one Granola note with its Title, Owner, Attendees, Folder Membership and Summary Text. Set Include to Transcript to add the Transcript to the same result.
- Get a Transcript Fetches the transcript of one note as separate segments, each with its Speaker, Text, Start Time and End Time. Use Limit to stop after a set number of segments.
- List Audit Events Reads the audit log of your Granola workspace, one item per event with its Action, Actor and Occurred At. Use Action to look at a single kind of event, or Occurred After and Occurred Before to cover a time window.
- List Folders Gathers the folders in Granola as separate items, each with its Name and Parent Folder ID. Set Limit for a fixed maximum of folders.
- List Notes Pulls notes as separate items with their Title, Owner and Updated At. Use Folder to read one folder only, and Created After, Created Before or Updated After to limit by date.
- List Webhook Endpoints Shows the webhook endpoints set up in Granola, each with its URL, the Events it receives, its Scopes and whether it is Enabled.
- Make an API Call Runs a free-form request against the Granola AI REST API using your saved credential.
- Update a Webhook Endpoint Changes an existing endpoint: its Endpoint URL, Scopes, Events or Folder IDs. Turn Enabled off to pause deliveries or on to resume them. The updated endpoint is returned.
- Watch Events Starts a workflow when Granola sends a note event. Output includes the Event Type, the Note ID and when it Occurred At.
- Watch Notes Checks on a schedule for notes that were created or updated and runs once per note. Use Folder to watch one folder, and Max Pages to cap how far each check reads.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Better Stack and Granola AI integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Better Stack and Granola AI.
References
List of sources used to gather information about the Better Stack and Granola AI integration.
- Better Stack and Granola AI integration source code, module specs and credentials implementation.
- Our Better Stack and Granola AI integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Better Stack and Granola AI, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Better Stack integration information
- Granola AI integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Better Stack and Granola AI integration page documentation. Used sources, the role of AI, and how the team validates the result.