# Plecto integrations: registrations

> Create registrations, create a data source and create a dashboard in Plecto. Connect Plecto to the rest of your data and analytics stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/plecto-integrations/
**Categories:** Data and analytics
**Connects through:** HTTP Connector

## Overview

Plecto is a performance dashboard tool that pulls sales and team data into real-time KPI dashboards, leaderboards, and contests shown on office screens. Tray.ai connects to Plecto through the HTTP Connector, so your workflows can call the Plecto API alongside the rest of your stack.

## Use cases

### Registrations

Read, create, and delete registrations in Plecto from any Tray.ai workflow. The Plecto API covers calls such as create registrations and list registrations.

- Create registrations
- List registrations
- Delete a registration

### Data sources

Read and create data sources in Plecto from any Tray.ai workflow. The Plecto API covers calls such as list data sources and create a data source.

- List data sources
- Create a data source

### Members

Read and create members in Plecto from any Tray.ai workflow. The Plecto API covers calls such as list members and create a member.

- List members
- Create a member

### Teams

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

- List teams
- Create a team

### Dashboards

Read and create dashboards in Plecto from any Tray.ai workflow. The Plecto API covers calls such as list dashboards and create a dashboard.

- List dashboards
- Create a dashboard

## Challenges Tray.ai solves

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

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

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

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

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