# Feedier integrations: feedback and reports

> Create feedback, create a report and create a segment in Feedier. Connect Feedier to the rest of your customer service stack with Tray.ai.

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

## Overview

Feedier is a customer feedback platform that collects survey and review responses, analyses them with AI and shares the findings in reports. Tray.ai connects to Feedier through the HTTP Connector, so your workflows can call the Feedier API alongside the rest of your stack.

## Use cases

### Feedback

Read, create, delete, and manage feedback in Feedier from any Tray.ai workflow. The Feedier API covers calls such as list feedback and get feedback.

- List feedback
- Get feedback
- Create feedback

### Reports

Read, create, update, and delete reports in Feedier from any Tray.ai workflow. The Feedier API covers calls such as list reports and get a report.

- List reports
- Get a report
- Create a report

### Segments

Read, create, update, and delete segments in Feedier from any Tray.ai workflow. The Feedier API covers calls such as list segments and create a segment.

- List segments
- Create a segment
- Update a segment

### Users

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

- List users
- Create a user
- Update a user

### Teams

Read, create, and update teams in Feedier from any Tray.ai workflow. The Feedier API covers calls such as list teams and get a team.

- List teams
- Get a team
- Create a team

### Imports

Read and create imports in Feedier from any Tray.ai workflow. The Feedier API covers calls such as import a CSV file and get an import.

- Import a CSV file
- Get an import

## Challenges Tray.ai solves

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

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

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

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

### Can I get a dedicated Feedier connector?

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