Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Blackbaud

Blackbaud integration for Flows360 workflows.

CategoryOther
AuthenticationOAuth 2.0
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Blackbaud with Flows360

Blackbaud integration for Flows360 workflows.

Use the Blackbaud connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 5 actions and no declared triggers.

Available actions

  • Search Contacts After Date
  • Upsert Contact on Email
  • Get Gift subtypes
  • Get Fundraising List
  • Create gift

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Blackbaud
  • Package: @activepieces/piece-blackbaud@0.3.0
  • Exact artifact digest: sha256:cc98145ff1dd14e08ee99912a649e542c14b1c23d4d418ebaa0af4ece01f11d3
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Search Contacts After Date (search_contacts_after_date), Search contacts Classification: read.
  • Upsert Contact on Email (upssert_contact_if_not_exists), Upsert Contact based on Email Classification: read.
  • Get Gift subtypes (get_gift_subtypes), Returns a list of gift subtypes. Classification: read.
  • Get Fundraising List (get_fundraising_list), Get Fundraising List Classification: read.
  • Create gift (create_gift), Create gift Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects5
Supported actions5
TriggersNone published

Authentication

Authentication method: OAuth 2.0

Authentication profiles

connection · oauth2

Supported objects

ObjectReadWriteNotes
Search Contacts After Date Yes No Search contacts
Upsert Contact on Email Yes No Upsert Contact based on Email
Get Gift subtypes Yes No Returns a list of gift subtypes.
Get Fundraising List Yes No Get Fundraising List
Create gift Yes No Create gift

Supported actions

Search Contacts After Date · Read

Search contacts

search_contacts_after_date · Risk: low · Retry: safe

Inputs

  • subscription_key · string · Required
  • last_modified_date · string · Required, The date to search for contacts modified after
Upsert Contact on Email · Read

Upsert Contact based on Email

upssert_contact_if_not_exists · Risk: low · Retry: safe

Inputs

  • subscription_key · string · Required
  • contact_json · object · Required, The Contact JSON
Get Gift subtypes · Read

Returns a list of gift subtypes.

get_gift_subtypes · Risk: low · Retry: safe

Inputs

  • subscription_key · string · Required
Get Fundraising List · Read

Get Fundraising List

get_fundraising_list · Risk: low · Retry: safe

Inputs

  • subscription_key · string · Required
  • fundraiser_list · string · Required, Select the List
  • last_modified_date · string · Optional, The date to search for appeal modified after | 2021-01-01T00:00:00.000Z
  • date_added · string · Optional, The date to search for contacts modified after | 2021-01-01T00:00:00.000Z
  • sort_token · string · Optional, Represents a token filter to provide the next stable-sorted list of appeals
  • include_inactive · boolean · Required, Include inactive appeals in the response
  • limit · number · Optional, Represents the number of records to return. The default is 500. The maximum is 5000
Create gift · Read

Create gift

create_gift · Risk: low · Retry: safe

Inputs

  • subscription_key · string · Required
  • gift_json · object · Required, The Gift JSON

Setup

Setup

  1. Add the Blackbaud connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-blackbaud@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 5 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Blackbaud connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-blackbaud@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com