--- title: "Connect Better Stack and OpenAI - APIANT.ai" description: "When \"New Monitor Status Change\" fires in Better Stack, your agent runs \"Create message\" in OpenAI." canonical: "https://apiant.ai/connect/better-stack-to-openai" --- # Connect Better Stack and OpenAI When **New Monitor Status Change** fires in [Better Stack](https://apiant.ai/connections/better-stack), your agent runs **Create message** in [OpenAI](https://apiant.ai/connections/openai), or **New batch** in OpenAI to **Add Incident Comment** in Better Stack. Describe the whole flow and it is built, tested on every scenario and kept running. Better Stack **3** triggers Better Stack **13** actions OpenAI **5** triggers OpenAI **69** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Better Stack and OpenAI to do together? Give your AI client this address. `https://mcp.apiant.ai` One connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What Better Stack and OpenAI can do together ### From Better Stack to OpenAI - When **New Monitor Status Change** in Better Stack then **Create message** in OpenAI - When **New or Updated Incident** in Better Stack then **Create assistant** in OpenAI ### From OpenAI to Better Stack - When **New batch** in OpenAI then **Add Incident Comment** in Better Stack - When **New file** in OpenAI then **Add Heartbeat** in Better Stack Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with Better Stack and OpenAI ## Triggers and actions 8 triggers · 82 actions - Trigger **New Monitor Status Change** Fires when a monitor's status changes (up/down). - Trigger **New or Updated Incident** Triggers when new incidents are created, or when existing incidents are updated. - Trigger **On-Call Contact Changed** Triggers when an on-call contact changes. - Action **Acknowledge Incident** Acknowledges an incident. - Action **Add Heartbeat** Create a new heartbeat check. - Action **Add Incident Comment** Adds a comment to an incident. - Action **Add Monitor** Create a new uptime monitor. - Action **Create Incident** Creates an incident that notifies the team. - Action **Delete Heartbeat** Remove a heartbeat check by id. - Action **Delete Monitor** Delete an uptime monitor by id. - Action **Find Incident** Finds an Incident. - Action **Find On-Call Contact** Finds On-Call Contact. Supports time lookup. - Action **Get Monitor** Retrieve a single monitor by id. - Action **List Monitors** List all uptime monitors. - Action **Resolve Incident** Resolves an incident. - Action **Update Monitor** Update an existing monitor's settings. - Trigger **New batch** List your organization's batches. - Trigger **New file** Returns a list of files. - Trigger **New model** Lists the currently available models. - Trigger **New vector store** Returns a list of vector stores. - Trigger **New video** List recently generated videos for the current project. - Action **Cancel batch** Cancels an in-progress batch. - Action **Cancel run** Cancels a run that is in_progress. - Action **Cancel vector store file batch** Cancel a vector store file batch. - Action **Content moderation** Classifies text for hate, harassment, self-harm, sexual, and violence categories using the Moderations API. - Action **Count input tokens** Returns input token counts of the request. - Action **Create assistant** Create an assistant with a model and instructions. - Action **Create chat completion** Sends a list of chat messages to a model via the Chat Completions API and returns the assistant's reply. - Action **Create completion** Creates a completion for the provided prompt and parameters. - Action **Create embedding** Generates a vector embedding for input text using an embeddings model (e.g. text-embedding-3-small). - Action **Create message** Create a message. - Action **Create run** Create a run. - Action **Creates and executes a batch from an uploaded file of requests** Creates and executes a batch from an uploaded file of requests - Action **Create thread** Create a thread. - Action **Create thread and run** Create a thread and run it in one request. - Action **Create vector store** Create a vector store. - Action **Create vector store file** Create a vector store file by attaching a File to a vector store. - Action **Create vector store file batch** Create a vector store file batch. - Action **Create video edit job** Create a new video generation job by editing a source or existing generated video. - Action **Create video extension** Create an extension of a completed video. - Action **Create video generation job** Create a new video generation job from a prompt and optional reference assets. - Action **Create video remix** Create a remix of a completed video using a refreshed prompt. - Action **Delete assistant** Delete an assistant. - Action **Delete eval run** Delete an eval run. - Action **Delete file** Delete a file and remove it from all vector stores. - Action **Delete message** Deletes a message. - Action **Delete thread** Delete a thread. - Action **Delete vector store** Delete a vector store. - Action **Delete vector store file** Delete a vector store file (removes from store, file itself not deleted). - Action **Delete video** Permanently delete a completed or failed video and its stored assets. - Action **Download video content** Download the generated video bytes or a derived preview asset. - Action **Edit image** Creates an edited or extended image given one or more source images and a prompt. - Action **Generate image** Generates an image from a text prompt using gpt-image-1 / DALL-E and returns the image URL or base64 data. - Action **Generate speech** Converts text into spoken audio using a TTS model and the selected voice. Returns audio bytes. - Action **Get assistant** Retrieves an assistant. - Action **Get batch** Retrieves a batch. - Action **Get file** Returns information about a specific file. - Action **Get file content** Returns the contents of the specified file. - Action **Get message** Retrieve a message. - Action **Get model** Retrieves a model instance. - Action **Get run** Retrieves a run. - Action **Get run step** Retrieves a run step. - Action **Get thread** Retrieves a thread. - Action **Get vector store** Retrieves a vector store. - Action **Get vector store file** Retrieves a vector store file. - Action **Get vector store file batch** Retrieves a vector store file batch. - Action **Get vector store file content** Retrieve the parsed contents of a vector store file. - Action **Get video** Fetch the latest metadata for a generated video. - Action **List conversation items** List all items for a conversation with the given ID. - Action **List files** Lists files that have been uploaded to your OpenAI account. - Action **List messages** Returns a list of messages for a given thread. - Action **List models** Lists the models currently available to your account. - Action **List runs** Returns a list of runs belonging to a thread. - Action **List run steps** Returns a list of run steps belonging to a run. - Action **List vector store file batch files** Returns a list of vector store files in a batch. - Action **List vector store files** Returns a list of vector store files. - Action **OpenAI agent message** Runs one AI agent turn on OpenAI and returns the model's reply. The turn is billed to the OpenAI account connected on this step, and the agent can call the account's AI tool automations. - Action **Retrieve response** Retrieves a previously created model response by its Response ID. - Action **Search vector store** Search a vector store for relevant chunks based on a query and filter. - Action **Send model a message** Sends a message to an OpenAI model via the Responses API and emits its response. Returns a Response ID usable as previous_response_id for multi-turn conversations. - Action **Submit tool outputs to run** Submit tool outputs when a run requires action. - Action **Transcribe audio** Transcribes audio into the input language. - Action **Translate audio** Translates audio into English. - Action **Update assistant** Modifies an assistant. - Action **Update message** Modifies a message. - Action **Update run** Modifies a run. - Action **Update thread** Modifies a thread. - Action **Update vector store** Modifies a vector store. - Action **Update vector store file attributes** Update attributes on a vector store file. - Action **Upload file** Upload a file that can be used across various endpoints. ## Each app on its own - [ **Better Stack** Better Stack is a tool to provide reliable monitoring with voice calls and beautiful on-call scheduling.](https://apiant.ai/connections/better-stack) - [ **OpenAI** OpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...](https://apiant.ai/connections/openai) Reviews ## What our customers say ## More from Better Stack - [ **Better Stack to PagerDuty** PagerDuty is an incident management and on-call alerting platform.](https://apiant.ai/connect/better-stack-to-pagerduty) - [ **Better Stack to Mailsoftly** Mailsoftly is a free email marketing tool designed to send personalized emails and newsletters.](https://apiant.ai/connect/better-stack-to-mailsoftly) - [ **Better Stack to Telegram** Telegram is a cloud-based instant messaging and voice over IP service developed by Telegram Messenger LLP.](https://apiant.ai/connect/better-stack-to-telegram) - [ **Better Stack to Vdocipher** Video hosting platform with DRM encryption, watermarking, and APIs to prevent piracy of streamed video...](https://apiant.ai/connect/better-stack-to-vdocipher) - [ **Better Stack to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/better-stack-to-hubspot) - [ **Better Stack to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/better-stack-to-slack) ## More into OpenAI - [ **Mailchimp to OpenAI** Mailchimp marketing automation and email platform.](https://apiant.ai/connect/mailchimp-to-openai) - [ **ActiveCampaign to OpenAI** ActiveCampaign is a marketing automation, email marketing, and CRM platform.](https://apiant.ai/connect/activecampaign-to-openai) - [ **Asana to OpenAI** Asana is a collaborative information manager for workspace.](https://apiant.ai/connect/asana-to-openai) - [ **JIRA to OpenAI** Atlassian JIRA Cloud — issue tracking and project management.](https://apiant.ai/connect/jira-to-openai) - [ **Twilio to OpenAI** Cloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...](https://apiant.ai/connect/twilio-to-openai) - [ **Intercom to OpenAI** Intercom is a customer communications platform for support, engagement, and marketing.](https://apiant.ai/connect/intercom-to-openai) Questions ## Better Stack and OpenAI, answered ### ### What can start an automation from Better Stack? Any of Better Stack's 3 triggers in the catalog, including New Monitor Status Change, New or Updated Incident and On-Call Contact Changed. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in OpenAI when something happens in Better Stack? Any of OpenAI's 69 actions, including Create assistant, Create chat completion, Create completion and Create embedding. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from OpenAI to Better Stack? Yes. When something happens in OpenAI, your agent can act in Better Stack too. This page covers both directions: OpenAI's triggers and Better Stack's actions are listed here as well. ### ### Do I have to build a connector for Better Stack or OpenAI? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### Can my AI client use Better Stack and OpenAI without building an automation? Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.