# Envoy integrations: entries and invites

> Create an entry, create an invite and create a work schedule in Envoy, and start a workflow when Envoy sends “Visitor signed in”.

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

## Overview

Envoy is a workplace platform for signing in visitors, pre-registering guests, scheduling employee office days, booking desks, and logging package deliveries. Tray.ai connects to Envoy through the HTTP Connector, so your workflows can call the Envoy API alongside the rest of your stack.

## Use cases

### Entries

Read, create, and update entries in Envoy from any Tray.ai workflow. The Envoy API covers calls such as list entries and get an entry.

- List entries
- Get an entry
- Create an entry

### Invites

Read, create, update, and delete invites in Envoy from any Tray.ai workflow. The Envoy API covers calls such as list invites and create an invite.

- List invites
- Create an invite
- Update an invite

### Work schedules

Read and create work schedules in Envoy from any Tray.ai workflow. The Envoy API covers calls such as list work schedules and create a work schedule.

- List work schedules
- Create a work schedule
- Check in

### Employees

Read and create employees in Envoy from any Tray.ai workflow. The Envoy API covers calls such as list employees and get an employee.

- List employees
- Get an employee
- Import employees

### Deliveries

Read, create, and delete deliveries in Envoy from any Tray.ai workflow. The Envoy API covers calls such as list deliveries and create a delivery.

- List deliveries
- Create a delivery
- Delete a delivery

### Blocklists

Read, create, and delete blocklists in Envoy from any Tray.ai workflow. The Envoy API covers calls such as list blocklist entries and create a blocklist entry.

- List blocklist entries
- Create a blocklist entry
- Delete a blocklist entry

## Challenges Tray.ai solves

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

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

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

The Envoy 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 Envoy connector?

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