Connect your stack

The Troubleshooting Agent is only as good as what it can see. Each system you connect gives it another place to find evidence.

You need the Admin role. In the Troubleshooting Agent, open Integrations.

Connect an app#

1. Under Discovery, find the app. Popular apps are grouped by category, and Search across 3000+ integrations finds the rest.
2. Select Connect.
3. In the window that opens, sign in to the app or enter its API key or credentials.

The app then appears under Connected Apps. The first time you connect an app, your workspace gets 500 free credits.

The table lists the popular apps only. Any app in the catalog connects the same way, including session recording tools such as FullStory or LogRocket. If you cannot find a tool, use the Send us a message link under the search results.

Do you lack the access to connect a tool? Select Invite a colleague to bring in someone who has it.

Choose your GitHub repositories#

Right after you connect GitHub, Pluno asks which repositories it may inspect.

1. In Select repositories, tick the repositories.
2. Select Save.

To change the selection later, select the pencil icon on the GitHub card. During an investigation, Pluno works with a copy of the repository inside that investigation's temporary workspace.

If you want Pluno to be able to open pull requests, the GitHub connection needs write access. See Pull requests.

Connect a database#

PostgreSQL, MySQL, MongoDB and Snowflake connect like any other app.

• Use a database user that can only read. Pluno is instructed to run read-only queries, and a read-only user guarantees it.
• Make sure the database is reachable from the internet. Queries do not run from inside your network. Allow only encrypted connections.

Set your PostHog region#

After connecting PostHog, select the pencil icon on its card and choose United States or European Union. The default is United States.

Add a custom API#

Use a custom API for an internal system that is not in the catalog, such as an admin API or a metrics service.

1. Under Custom APIs, select Add custom API.

2. Enter a Display name and the Base URL.

3. Choose the Auth type:

   Auth type	What Pluno sends
   None	No authorization header
   Bearer token header	Your token, with the header name and prefix you set
   API key header	Your key in the header you name, by default X-API-Key
   Custom header	Any header name and value

4. Select Add tool for each request Pluno may make, and fill it in:

   Field	What to enter
   Tool name	A short name, such as "Get account"
   Description	What Pluno should use the tool for. Pluno decides when to call a tool from this text
   Path template	The path, with placeholders, such as /incidents/{incident_id}
   Request params	Each parameter's name, where it goes, its type and whether it is required
   Timeout seconds	How long Pluno waits. The default is 20

5. Save, then open Test, choose a tool and select Run test.

Things to know:

• Tools make GET requests. Point them at endpoints that only read data.
• The API must be reachable on the public internet.
• Secrets are stored encrypted and are never shown again.
• Pluno reads the first 12,000 characters of a response, so point tools at endpoints that return focused results.

Self-hosted connectors#

On Enterprise plans, access to your code and databases can run through connectors you host yourself. Contact the Pluno team to set this up.

Connections you get automatically#

If your Pluno workspace has a help desk connected, the Troubleshooting Agent can also use these without any setup:

Disconnect an app#

Select the trash icon on the app's card and confirm with Disconnect. Pluno can no longer use the app.

Disconnecting removes the connection from Pluno. To withdraw the access itself, also revoke it in the app, for example by deleting the API key or removing the authorized application.

What Pluno stores#

• Your systems' data is read live during an investigation. Pluno does not copy or index your apps or repositories in advance.
• Each investigation is kept in your chat history, including the steps Pluno took and what they returned.
• Credentials for catalog apps are held by Pluno's integration partner. Custom API secrets are stored encrypted by Pluno.