# Raiser's Edge NXT integrations: constituents

> Create a constituent, create a gift and create an opportunity in Raiser's Edge NXT, and start a workflow when Raiser's Edge NXT sends “Constituent added”.

**Canonical page:** https://tray.ai/connectors/raisers-edge-nxt-integrations/
**Categories:** Sales
**Connects through:** HTTP Connector

## Overview

Raiser's Edge NXT is Blackbaud's fundraising and donor management system for nonprofits, tracking constituents, gifts, and major giving opportunities. Tray.ai connects to Raiser's Edge NXT through the HTTP Connector, so your workflows can call the Raiser's Edge NXT API alongside the rest of your stack.

## Use cases

### Constituents

Read, create, and update constituents in Raiser's Edge NXT from any Tray.ai workflow. The Raiser's Edge NXT API covers calls such as list constituents and get a constituent.

- List constituents
- Get a constituent
- Create a constituent

### Gifts

Read and create gifts in Raiser's Edge NXT from any Tray.ai workflow. The Raiser's Edge NXT API covers calls such as list gifts and get a gift.

- List gifts
- Get a gift
- Create a gift

### Opportunities

Read, create, and update opportunities in Raiser's Edge NXT from any Tray.ai workflow. The Raiser's Edge NXT API covers calls such as list opportunities and create an opportunity.

- List opportunities
- Create an opportunity
- Update an opportunity

### Raiser's Edge NXT events

Start a Tray.ai workflow the moment something happens in Raiser's Edge NXT. Raiser's Edge NXT sends events such as constituent added and constituent changed to a Tray.ai webhook trigger.

- Constituent added
- Constituent changed
- Constituent deleted

## Challenges Tray.ai solves

### Keeping Raiser's Edge NXT 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 Raiser's Edge NXT 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 Raiser's Edge NXT 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 Raiser's Edge NXT 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 Raiser's Edge NXT?

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

### How does Tray.ai authenticate with Raiser's Edge NXT?

The Raiser's Edge NXT API uses OAuth 2.0 and an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Raiser's Edge NXT connector?

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