# Splunk AppDynamics integrations: applications

> Create a health rule in Splunk AppDynamics. Connect Splunk AppDynamics to the rest of your IT stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/appdynamics-integrations/
**Categories:** IT
**Connects through:** HTTP Connector

## Overview

Splunk AppDynamics is an application performance monitoring product that tracks business transactions, tiers and nodes, and raises alerts through health rules and policies. Tray.ai connects to Splunk AppDynamics through the HTTP Connector, so your workflows can call the Splunk AppDynamics API alongside the rest of your stack.

## Use cases

### Applications

Read applications in Splunk AppDynamics from any Tray.ai workflow. The Splunk AppDynamics API covers calls such as list business applications and list business transactions.

- List business applications
- List business transactions
- List tiers

### Health rules

Read, create, update, and delete health rules in Splunk AppDynamics from any Tray.ai workflow. The Splunk AppDynamics API covers calls such as list health rules and get a health rule.

- List health rules
- Get a health rule
- Create a health rule

### Events

Read and create events in Splunk AppDynamics from any Tray.ai workflow. The Splunk AppDynamics API covers calls such as retrieve event data and create a deployment event.

- Retrieve event data
- Create a deployment event
- Create a custom event

## Challenges Tray.ai solves

### Keeping Splunk AppDynamics credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Splunk AppDynamics credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Splunk AppDynamics API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Splunk AppDynamics API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Splunk AppDynamics?

Yes. Tray.ai connects to Splunk AppDynamics through the HTTP Connector, which calls the Splunk AppDynamics API directly. Any call the Splunk AppDynamics API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Splunk AppDynamics?

The Splunk AppDynamics API uses OAuth 2.0 and a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Splunk AppDynamics connector?

Splunk AppDynamics runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Splunk AppDynamics connector from the Splunk AppDynamics API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/