# CrowdPower integrations: customers and charges

> Create a charge and create a tag in CrowdPower. Connect CrowdPower to the rest of your marketing stack with Tray.ai.

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

## Overview

CrowdPower is a customer engagement tool for SaaS companies that tracks user activity and sends automated and broadcast email campaigns to onboard and retain customers. Tray.ai connects to CrowdPower through the HTTP Connector, so your workflows can call the CrowdPower API alongside the rest of your stack.

## Use cases

### Customers

Read and delete customers in CrowdPower from any Tray.ai workflow. The CrowdPower API covers calls such as identify a customer and list customers.

- Identify a customer
- List customers
- Get a customer

### Events

Read, create, and delete events in CrowdPower from any Tray.ai workflow. The CrowdPower API covers calls such as create an event and list customer events.

- Create an event
- List customer events
- Delete an event

### Charges

Read, create, and delete charges in CrowdPower from any Tray.ai workflow. The CrowdPower API covers calls such as create a charge and list customer charges.

- Create a charge
- List customer charges
- Delete a customer charge

### Tags

Create and delete tags in CrowdPower from any Tray.ai workflow. The CrowdPower API covers calls such as create a tag and add a tag to a customer.

- Create a tag
- Add a tag to a customer
- Remove a tag from a customer

### Automations

Read and delete automations in CrowdPower from any Tray.ai workflow. The CrowdPower API covers calls such as list automations and get an automation.

- List automations
- Get an automation
- Delete an automation

### Segments

Read and delete segments in CrowdPower from any Tray.ai workflow. The CrowdPower API covers calls such as list segments and get a segment.

- List segments
- Get a segment
- Delete a segment

## Challenges Tray.ai solves

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

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

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

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

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