# Blink integrations: feed events and chats

> Send a feed event, create a chat and send a message in Blink. Connect Blink to the rest of your human resources stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/blink-integrations/
**Categories:** Human resources
**Connects through:** HTTP Connector

## Overview

Blink is an employee app for frontline teams, giving staff a company news feed, chat, forms and a hub for their work tools on their phone. Tray.ai connects to Blink through the HTTP Connector, so your workflows can call the Blink API alongside the rest of your stack.

## Use cases

### Feed events

Create, update, and delete feed events in Blink from any Tray.ai workflow. The Blink API covers calls such as send a feed event and update a feed event.

- Send a feed event
- Update a feed event
- Archive a feed event

### Users

Read, create, and update users in Blink from any Tray.ai workflow. The Blink API covers calls such as list users and create a user.

- List users
- Create a user
- Update a user

### Groups

Read, create, and update groups in Blink from any Tray.ai workflow. The Blink API covers calls such as list groups and create a group.

- List groups
- Create a group
- Update a group

### Chats

Read, create, update, and delete chats in Blink from any Tray.ai workflow. The Blink API covers calls such as create a chat and get a chat.

- Create a chat
- Get a chat
- Update a chat

### Messages

Read, create, update, and delete messages in Blink from any Tray.ai workflow. The Blink API covers calls such as list chat messages and send a message.

- List chat messages
- Send a message
- Edit a message

### Forms

Read forms in Blink from any Tray.ai workflow. The Blink API covers calls such as list forms and list form submissions.

- List forms
- List form submissions

## Challenges Tray.ai solves

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

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

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

The Blink API uses 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 Blink connector?

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