# Survicate integrations: surveys and responses

> Start a Tray.ai workflow when Survicate sends “Question answered”. Connect Survicate to the rest of your customer service stack with Tray.ai.

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

## Overview

Survicate is a customer feedback tool for running surveys on websites, in products, by email and through links, then collecting and analysing the responses. Tray.ai connects to Survicate through the HTTP Connector, so your workflows can call the Survicate API alongside the rest of your stack.

## Use cases

### Surveys

Read surveys in Survicate from any Tray.ai workflow. The Survicate API covers calls such as list surveys and get a survey.

- List surveys
- Get a survey
- List survey questions

### Responses

Read responses in Survicate from any Tray.ai workflow. The Survicate API covers calls such as list survey responses and get a response.

- List survey responses
- Get a response

### Respondents

Read respondents in Survicate from any Tray.ai workflow. The Survicate API covers calls such as get respondent attributes and list respondent responses.

- Get respondent attributes
- List respondent responses

### Personal data

Read and delete personal data in Survicate from any Tray.ai workflow. The Survicate API covers calls such as retrieve a person's data and delete a person's data.

- Retrieve a person's data
- Delete a person's data

### Survicate events

Start a Tray.ai workflow the moment something happens in Survicate. Survicate sends events such as question answered and survey completed to a Tray.ai webhook trigger.

- Question answered
- Survey completed

## Challenges Tray.ai solves

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

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

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

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

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