Blackbaud offers cloud-based software for nonprofits, schools, and healthcare institutions, supporting fundraising, financial management, and donor engagement in mission-driven organizations
Blackbaud offers cloud-based software for nonprofits, schools, and healthcare institutions, supporting fundraising, financial management, and donor engagement in mission-driven organizations On Nagent, Blackbaud is exposed as a fully-configurable fundraising integration that any agent can call — 5 actions, and OAuth authentication. No code is required to wire Blackbaud into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Blackbaud to automate the kinds of tasks fundraising teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Blackbaud into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Blackbaud, with input parameters and output schema. Drop these into any step of an agent built in Helix.
BLACKBAUD_ADD_GIFTS_TO_BATCHAdd one or more gifts (donations) to an existing gift batch in Blackbaud Raiser's Edge NXT. Use this tool when you need to: - Append new gifts to an open batch for later processing - Batch multiple donations together before committing them - Add gifts with detailed information (payments, splits, custom fields) Prerequisites: - The batch must already exist (use a create batch action first if needed) - The batch must be in "open" status (not committed) - You need the batch_id (system record ID) and constituent_id (donor ID) for each gift Note: This action returns response details for all HTTP status codes (including errors). Check the status_code field in the response to determine success (200) vs errors (4xx/5xx).
Input parameters
List of one or more gift objects to add to the batch. Each gift represents a donation from a constituent.
The system record ID of the gift batch where gifts will be added. The batch must be open (not committed).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLACKBAUD_GET_GIFT_BY_IDRetrieves comprehensive gift details from Blackbaud Raiser's Edge NXT by gift ID. Use this tool when you need to fetch detailed information about a specific gift including: - Gift amount and currency - Donor/constituent information - Gift type and status - Important dates (gift date, post date) - Associated metadata and custom fields The gift_id is the unique system record ID (integer) that identifies the gift in Raiser's Edge NXT.
Input parameters
Unique system record ID of the gift to retrieve.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLACKBAUD_GET_MEMBERSHIP_DETAILSRetrieves comprehensive membership details from Blackbaud Raiser's Edge NXT by member junction ID. Fetches detailed information about a specific membership including program name, category/subcategory, membership status and standing (Active, Lapsed), start/expiration dates, dues information, and associated constituent ID. Requires a valid member_junction_id (GUID) that uniquely identifies a membership junction record linking a constituent to a membership program in Raiser's Edge NXT. Returns error information in the response object for graceful error handling in agent workflows.
Input parameters
The unique member junction ID (GUID format) that identifies a specific membership record in Raiser's Edge NXT. This ID links a constituent to a membership program and can be obtained from membership list endpoints or constituent membership records.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLACKBAUD_GET_PAYMENT_TRANSACTIONRetrieves payment transaction details from Blackbaud SKY Payments API. Use this to check transaction status, amounts, payment methods, and error details. Transaction IDs come from payment processing endpoints, checkout callbacks, batch operations, or webhook notifications. Requires: Payments API subscription key (Bb-Api-Subscription-Key) and OAuth Bearer token. This retrieves existing transactions; it does not process new payments.
Input parameters
The unique identifier of the payment transaction to retrieve. This ID is returned when a transaction is created through the Blackbaud Merchant Services (BBMS) Payments API or transaction processing endpoints.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
BLACKBAUD_ONE_ROSTER_O_AUTH2_BASE_APITool to interact with Blackbaud OneRoster OAuth2 base endpoints. Use to fetch OpenID configuration (/.well-known/openid-configuration), JWKS key set (publickeys), or obtain an access token via the client credentials grant. Ensure client credentials are configured before using the token operation.
Input parameters
Optional OAuth2 scope string. OneRoster generally does not require a scope; leave empty unless instructed by Blackbaud.
OneRoster OAuth2 client_id (key) provided by the institution.
Optional Authorization header value for HTTP Basic authentication, e.g., 'Basic base64(client_id:client_secret)'. If provided, it will be used.
OAuth2 grant type; must be 'client_credentials' for token operation.
Which OAuth2 resource to call: openid_configuration, jwks, or token
OneRoster OAuth2 client_secret provided by the institution.
Optional override for OAuth2 server base URL. Defaults to 'https://oauth2.sky.blackbaud.com'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 63 agents privately built on Nagent that already use Blackbaud.
Build on Nagent
Connect Blackbaud to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Blackbaud, and click "Connect Now." You'll authenticate with OAuth — Nagent handles credential storage and refresh automatically. Once connected, Blackbaud is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Blackbaud is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Blackbaud steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Blackbaud event fires, the agent kicks off automatically.
Every Blackbaud action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Blackbaud ships with 5 pre-built fundraising actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Blackbaud together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Blackbaud-based workflows tailored to your business.