# E-goi integrations: contacts, lists and campaigns

> Create a contact, create a list and create an email campaign in E-goi, and start a workflow when E-goi sends “Contact subscribed”.

**Canonical page:** https://tray.ai/connectors/e-goi-integrations/
**Categories:** Marketing
**Connects through:** HTTP Connector

## Overview

E-goi is a multichannel marketing automation platform for sending email, SMS, voice, push, and web push campaigns to contact lists, with automations and reports. Tray.ai connects to E-goi through the HTTP Connector, so your workflows can call the E-goi API alongside the rest of your stack.

## Use cases

### Contacts

Read, create, and update contacts in E-goi from any Tray.ai workflow. The E-goi API covers calls such as get all contacts and create a contact.

- Get all contacts
- Create a contact
- Update a contact

### Lists

Read, create, update, and delete lists in E-goi from any Tray.ai workflow. The E-goi API covers calls such as get all lists and create a list.

- Get all lists
- Create a list
- Update a list

### Campaigns

Read and create campaigns in E-goi from any Tray.ai workflow. The E-goi API covers calls such as get all campaigns and create an email campaign.

- Get all campaigns
- Create an email campaign
- Send an email campaign

### Segments and tags

Read and create segments and tags in E-goi from any Tray.ai workflow. The E-goi API covers calls such as get all segments and create a segment.

- Get all segments
- Create a segment
- Create a tag

### Automations

Read, create, and delete automations in E-goi from any Tray.ai workflow. The E-goi API covers calls such as get all automations and start an automation.

- Get all automations
- Start an automation
- Remove an automation

### Reports

Read reports in E-goi from any Tray.ai workflow. The E-goi API covers calls such as get an email report and get an SMS report.

- Get an email report
- Get an SMS report
- Generate an advanced report

## Challenges Tray.ai solves

### Keeping E-goi 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 E-goi 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 E-goi 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 E-goi 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 E-goi?

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

### How does Tray.ai authenticate with E-goi?

The E-goi API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated E-goi connector?

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