Better Stack and Vercel Integration
Demonstration of how apps are integrated in WEXTL workflow builder[4]
Build developer tools workflows between Better Stack and Vercel on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Better Stack and Vercel
Detailed info you need to know about Better Stack and Vercel integrations in WEXTL. Explore which modules apps support and how you connect them.
Better Stack

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

Frontend cloud for deploying and hosting web projects.[6]
How to connect Better Stack to Vercel
Set up your Better Stack and Vercel integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect Better Stack and Vercel
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 Vercel 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 Vercel. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between Better Stack and Vercel work in WEXTL?
WEXTL exposes actions and triggers for Better Stack and Vercel 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 triggersVercel 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.
Vercel modules
- Add a Domain Adds a domain to your Vercel account from its Domain Name. Use Method to add one you own or move one in from elsewhere, Create DNS Zone to create its zone as well, and Enable CDN to switch on the Vercel CDN.
- Add a Firewall Bypass Rule Adds a rule that lets traffic from a Source IP, an address or CIDR range, skip the project firewall. Use Domain to limit it to one domain and Duration for the minutes it lasts.
- Add a Project Domain Connects a hostname to a Vercel project. Use Git Branch to serve it from a branch instead of production, Custom Environment for a custom environment, and Redirect To to forward it to another domain or URL.
- Add a Project Member Grants a person one of the roles Admin, Developer or Viewer on a project via Project Role. Use Team Member for someone on the team, or Email when no team member is picked.
- Approve a Rolling Release Stage Advances a rolling release to a later stage for its Canary Deployment, and reports the Active Stage and Current Canary Percentage.
- Assign an Alias to a Deployment Makes a deployment answer on a hostname such as staging.example.com. Use Redirect To to send the Alias to another hostname instead. You receive the Alias and the Old Deployment ID.
- Cancel a Deployment Halts a deployment while it is building or queued. You receive the deployment with its Ready State and URL.
- Complete a Rolling Release Finishes a rolling release by sending all traffic to the Canary Deployment. You receive the Active Stage and Current Deployment.
- Create a Custom Environment Builds a custom environment for a project under a Slug of up to 32 characters. Use Branch Match to send matching branches to it, and Copy Variables From or Copy From Custom Environment to start from existing variables.
- Create a Deployment Starts a deployment of a project from a connected Git repository or from uploaded files, set through Source. Leave Target blank for a preview, and turn on Force New Deployment to build again even when nothing changed.
- Create a DNS Record Adds a DNS record of a chosen Type to a domain. Use Name for a subdomain such as www, or leave it blank for the domain itself. Use TTL for a lifetime in seconds, at least 60.
- Create a Project Sets up a Vercel project. Leave Framework blank to let Vercel detect it, use Git Provider to connect a repository so pushes deploy, and Root Directory for the folder of the project inside the repository.
- Create a Project Environment Variable Defines a variable on a project with a Name, Value and Type of Encrypted, Plain Text or Sensitive. Choose Targets for the environments it covers, and turn on Replace If It Exists to overwrite a variable with the same name and target instead of failing.
- Create a Team Creates a Vercel team from a Slug of up to 48 characters, with an optional Name. You receive the team ID and Slug.
- Create an Access Group Creates an access group with a Name of up to 50 characters. Use Project Roles to give the group a role on specific projects and Members To Add to put team members in it. You receive the Access Group ID.
- Create an Edge Config Makes an Edge Config from a Slug of lowercase letters, digits, hyphens and underscores. Use Items to start it with values, which stay masked in run logs.
- Create Shared Environment Variables Sets up to 50 shared Variables in one call, each stored with a Type of Encrypted or Sensitive for the chosen Targets. Link them to projects through Projects.
- Delete a Certificate Deletes a certificate. This cannot be undone, so turn on Confirm to proceed.
- Delete a Custom Environment Removes a custom environment. Turn on Also Delete Unassigned Variables to delete variables that belong to no other environment.
- Delete a Deployment Removes a deployment. Switch on Confirm to go ahead, since there is no undo.
- Delete a DNS Record Deletes a DNS record on a domain. Turn on Confirm to proceed, since deletion cannot be undone.
- Delete a Domain Deletes a domain. Turn on Confirm to proceed, as there is no undo.
- Delete a Drain Removes a log drain once Confirm is switched on. Deletion cannot be undone.
- Delete a Feature Flag Deletes a feature flag from its project. Switch on Confirm to continue, as undoing is not possible.
- Delete a Project Removes a project from Vercel. Turn on Confirm to proceed, because this cannot be undone.
- Delete a Project Check Deletes a check defined on a project. Turn on Confirm to proceed.
- Delete a Project Environment Variable Removes a project variable, either everywhere or only from one custom environment through Custom Environment. Turn on Confirm to proceed.
- Delete a Team Deletes a team, which cannot be undone once Confirm is on. Set New Default Team to the team that should become your default afterwards.
- Delete a Webhook Deletes a webhook. If a workflow trigger relies on it, turn that trigger off instead. Turn on Confirm to proceed.
- Delete an Access Group Deletes an access group from the team. Turn on Confirm to go ahead, as this cannot be undone.
- Delete an Access Token Revokes an access token. Turn on Confirm to proceed, and note that deleting the token this credential uses breaks the credential.
- Delete an Alias Removes a hostname alias pointing at a deployment. Turn on Confirm to proceed.
- Delete an Edge Config Turn on Confirm to delete an Edge Config. There is no way to undo it.
- Delete an Edge Config Item Removes the item stored under a Key inside a config store.
- Delete Multiple Project Environment Variables Deletes up to 1000 variables of one project in a single call, reporting the Deleted count and the Ids. Turn on Confirm to proceed.
- Delete Shared Environment Variables Removes up to 50 shared variables at once, reporting any Failed deletions. Turn on Confirm first.
- Get a Certificate Shows a certificate with its Cns, Auto Renew setting and Expires At date.
- Get a Custom Environment Returns a custom environment with its Slug, Branch Matcher and Domains.
- Get a Deployment Retrieves a deployment with its Ready State, URL, Target and Inspector URL. Turn on Include Git Info to add the Git repository details.
- Get a Domain Gets a domain on your account with its Verified flag, Nameservers, Intended Nameservers and Expires At date.
- Get a Domain Configuration Reviews how a domain is set up in DNS, flagging a Misconfigured domain and showing Configured By. Add Project to look at one project.
- Get a Domain Price Looks up the Purchase Price, Renewal Price and Transfer Price of a Domain Name. Use Years to price a longer term, or leave it blank for the shortest term the domain allows.
- Get a Drain Reads a log drain with its Name, Project Ids and Disabled Reason. Turn on Include Delivery Stats to add its delivery health.
- Get a Feature Flag Fetches a feature flag with its Kind, State, Environments and Maintainer Ids.
- Get a Project Retrieves a project with its Framework, Node Version, Build Command and Root Directory.
- Get a Project Check Reads a project check with its Name, Source, Requires and whether it Is Rerequestable.
- Get a Project Domain Looks up a domain attached to a project, showing its Verified flag, Redirect and Git Branch.
- Get a Project Environment Variable Reads a project variable with its Key, Type, Target and Value. The real Value enters the run history, and sensitive variables return no value.
- Get a Rolling Release Reads rolling release progress on a project, with its Active Stage, Current Canary Percentage and Stages. Use State to filter by whether it is Active, Complete or Aborted.
- Get a Rolling Release Configuration Returns how rolling releases are set up for a project: the Target, the Gate, the Stages and the Canary Response Header.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with Better Stack and Vercel 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 Vercel.
References
List of sources used to gather information about the Better Stack and Vercel integration.
- Better Stack and Vercel integration source code, module specs and credentials implementation.
- Our Better Stack and Vercel integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Better Stack and Vercel, 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
- Vercel integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted Better Stack and Vercel integration page documentation. Used sources, the role of AI, and how the team validates the result.