# Integrations

### Card States

| State            | Visual    | Meaning                              |
| ---------------- | --------- | ------------------------------------ |
| **Disconnected** | Default   | No connection is configured.         |
| **Connected**    | Green dot | The last test or delivery succeeded. |
| **Error**        | Red dot   | The last test or delivery failed.    |

Each card shows:

* Integration name and badge.
* Short description.
* Flow direction in plain English, such as "PromptVault -> trace metadata".
* Connect, Edit, Test, and Disconnect actions.

### Connecting

Click **Connect** on a card to open the configuration dialog. Each connector has its own field set:

* Langfuse&#x20;
* Helicone
* Braintrust
* Webhook
* PostHog
* GitHub

Secrets are not shown again after connection. Editing an integration with a masked secret requires re-entering that secret.

### Testing a Connection

The **Test** button checks whether the destination accepts the configured credentials. A failed test marks the card as **Error**, but it does not delete the connection.

### Disconnecting

Disconnecting removes the connection. To re-enable it later, reconnect with fresh credentials.

### How Events Flow

PromptVault sends events when prompts are created, published, rolled back, or deleted. Delivery is independent per integration: one failing destination does not block prompt saves or other integrations.

### Notes on Observability Stance

PromptVault keeps prompt source and version metadata. Connected tools handle traces, evals, external history, and audit workflows.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://aiso.gitbook.io/promptvault/documentation/dashboard/integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
