A connection is an HTTP endpoint your organization registers so Vibe OnCall can call it: an address and a method, request headers whose secret values are stored encrypted, a timeout, and — optionally — the endpoint's own documentation. What stands behind the address is your choice: one of your own internal services, or a third party's API. The connection is the registration, not the system behind it.

Where to find it: Settings → Shared Resources → Connections

Who calls a connection

One registration, two callers. Each decides for itself what to send and what to do with the answer.

Caller What it does
An automation The Invoke REST connection action sends alert or incident data to the endpoint when an automation fires. On the Alert is created trigger it can also read values out of the response and write them onto the alert.
Vibe OnCall, in conversation Asked something it cannot answer from its own records, Vibe OnCall can send a request to a registered endpoint and read the reply. It composes that request from the endpoint's Documentation.

Vibe OnCall can list your registered endpoints, read one together with its document, and send a request — always on behalf of a person who asked, never on its own. It cannot create, change, or delete a connection; that stays in Settings. Header values are attached to the request on the server and are never shown to it, and a response is treated as data to read, not as instructions to follow.

Create a connection

Screenshot 2026-08-31 at 2.56.59 PM.png

  1. Go to Settings → Shared Resources → Connections and select Create connection.
  2. Name the connection. The name must be unique in your organization. The optional description is a one-line note for whoever picks it from a list later.
  3. Under Endpoint, choose the HTTP method and enter the base URL. Add a path if the endpoint always needs one. Leave query strings out of it — a stored path containing ? cannot have a path appended to it later, which rules the connection out of both automation path templates and requests Vibe OnCall composes. Put query parameters on the caller instead.
  4. Under Headers, add whatever the endpoint requires: Authorization, Content-Type, an API key. Turn on Secret for any value that is a credential.
  5. Under Documentation, paste the endpoint's own API documentation. See below for what this changes.
  6. Set Timeout (ms) — how long to wait for a response before the request is treated as failed.
  7. Leave Connection enabled on and select Create.

Field reference

Field What it controls
Method GET, POST, PUT, PATCH, or DELETE. Fixed on the connection; callers cannot change it.
Base URL The address. Must be https:// — an http:// address saves but fails on every request.
Path Optional, appended to the base URL. It cannot contain a query string or fragment if anything will append a path to it — an automation's path template or a request Vibe OnCall composes both fail against a stored path holding ?. Query parameters belong on the caller.
Headers Sent with every request. A value marked Secret is encrypted at rest and never returned — when you edit the connection later, leave it blank to keep the stored value.
Documentation The endpoint's own manual. Optional, and the difference between an endpoint that can be asked new questions and one that cannot.
Timeout (ms) How long to wait before the request fails. Between 100 and 10,000.
Connection enabled When off, the connection is paused and sends no requests. Callers fail immediately rather than waiting.