# Appcues integrations

> Call the Appcues API from any Tray.ai workflow with the HTTP Connector.

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

## Overview

Appcues is a product adoption platform for building in-app flows, checklists, banners, and NPS surveys, then tracking how users respond to them. Tray.ai connects to Appcues through the HTTP Connector, so your workflows can call the Appcues API alongside the rest of your stack.

## Use cases

### Flows

Read flows in Appcues from any Tray.ai workflow. The Appcues API covers calls such as list flows and get a flow.

- List flows
- Get a flow
- Publish a flow

### Segments

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

- Create a segment
- Update a segment
- Delete a segment

### End users

Read and update end users in Appcues from any Tray.ai workflow. The Appcues API covers calls such as get a user profile and update a user profile.

- Get a user profile
- Update a user profile
- Track a user event

### Groups

Read and update groups in Appcues from any Tray.ai workflow. The Appcues API covers calls such as get a group profile and update a group profile.

- Get a group profile
- Update a group profile

### Bulk data

Create bulk data in Appcues from any Tray.ai workflow. The Appcues API covers calls such as start a bulk import and start an event export.

- Start a bulk import
- Start an event export
- Check job status

### Appcues events

Start a Tray.ai workflow the moment something happens in Appcues. Appcues sends events such as web flow started and web flow completed to a Tray.ai webhook trigger.

- Web flow started
- Web flow completed
- Web flow skipped

## Challenges Tray.ai solves

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

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

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

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

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