# eGain integrations: cases and activities

> Update a case, create a task activity and create a customer in eGain. Connect eGain to the rest of your customer service stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/egain-integrations/
**Categories:** Customer service
**Connects through:** HTTP Connector

## Overview

eGain is a customer service platform built around a knowledge hub, with case management, customer records, live chat and AI answers for agents and self-service. Tray.ai connects to eGain through the HTTP Connector, so your workflows can call the eGain API alongside the rest of your stack.

## Use cases

### Cases

Read and update cases in eGain from any Tray.ai workflow. The eGain API covers calls such as search cases and get cases by ID.

- Search cases
- Get cases by ID
- Update a case

### Activities

Read and create activities in eGain from any Tray.ai workflow. The eGain API covers calls such as search activities and create a task activity.

- Search activities
- Create a task activity
- Send an email response

### Customers

Read, create, and update customers in eGain from any Tray.ai workflow. The eGain API covers calls such as search customers and create a customer.

- Search customers
- Create a customer
- Update a customer

### Notes

Read, create, and delete notes in eGain from any Tray.ai workflow. The eGain API covers calls such as create a case note and list case notes.

- Create a case note
- List case notes
- Delete case notes

### Knowledge articles

Read knowledge articles in eGain from any Tray.ai workflow. The eGain API covers calls such as list articles and get an article.

- List articles
- Get an article
- Rate an article

## Challenges Tray.ai solves

### Keeping eGain 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 eGain 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 eGain 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 eGain 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 eGain?

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

### How does Tray.ai authenticate with eGain?

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

### Can I get a dedicated eGain connector?

eGain runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated eGain connector from the eGain 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/