Integrations & the Marketplace¶
The Marketplace is where you connect DXDT to your stack — monitoring, cloud providers, incident tooling, code hosting, security. Every integration you install becomes a capability the DXDT agent can use in chat investigations, Pulse scans, and triage enrichment.
How it works¶
Each integration runs as a stateless connector service. Your credentials are stored per tenant and injected into each request; the connector itself keeps no database and no credential store. When credentials are added or changed, the audit trail records which configuration keys changed — never their values.
Once an integration is installed and active, the agent gains a tool for it that accepts commands and returns the integration's responses. What the agent can see — and therefore what Pulse findings and infrastructure graph coverage you get — is defined by which integrations you connect.
Using it¶
Open Marketplace from the console. The page has two views — Marketplace (the full catalog) and Installed — plus free-text search. Selecting an integration opens a detail pane with three tabs:
| Tab | Contents |
|---|---|
| Overview | What the integration is and its current install status |
| Setup Guide | Step-by-step install guide for that integration: where to create credentials, required permissions, field mapping |
| Configuration | The integration's credential and endpoint fields (secrets are masked) |
Installing¶
- Open the integration and read its Setup Guide tab.
- Fill in the Configuration tab and click Install.
- The integration provisions itself — status shows
installing, thenready, at which point it is active and available to the agent. - If provisioning fails, the status shows the error and the integration stays inactive; correct the configuration and install again.
Uninstalling runs the integration's cleanup hook, clears your stored configuration, and deactivates the tool for the agent.
Custom plugins¶
You can register your own tool — a name, description, and either an endpoint URL or an MCP server — and it becomes available to the agent like any catalog integration. Custom plugins you create can also be deleted by you.
| Tier | Custom plugins |
|---|---|
| Starter | Not available |
| Growth | 3 |
| Enterprise | Unlimited |
Configuration¶
| Task | Where |
|---|---|
| Browse and install integrations | Marketplace |
| Read an install guide | Integration detail → Setup Guide |
| Update credentials | Integration detail → Configuration |
| Uninstall | Installed view → integration detail |
| Create a custom plugin | Marketplace |
Troubleshooting¶
| Symptom | Cause |
|---|---|
| Status stuck on "Setting up…" | Provisioning did not complete — run Install again |
Status shows error |
Provisioning failed; the message contains the reason. Fix credentials and reinstall |
Custom plugin creation rejected (402) |
Custom plugin limit for your tier reached |
| An expected integration is missing from the catalog | Catalog visibility can vary per tenant — contact support |