Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Bloomerang

Bloomerang integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.1
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Bloomerang with Flows360

Bloomerang integration for Flows360 workflows.

Use the Bloomerang 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

  • Upsert Contact (Duplicates)
  • Upsert Contact (Search)
  • Create a transaction (Advanced)
  • Get contacts
  • Get Transaction Stuff (Advanced)

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: Bloomerang
  • Package: @activepieces/piece-bloomerang@0.1.1
  • Exact artifact digest: sha256:47922ad77dcf251c85e88e33cd6949a4fc6a601e69b56603e407b19b34ebd270
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

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

Action contracts

  • Upsert Contact (Duplicates) (upsert_contact_duplicates), Update or create bloomerang contact using duplicates Classification: read.
  • Upsert Contact (Search) (upsert_contact_search), Update or create bloomerang contact using the search Classification: read.
  • Create a transaction (Advanced) (create_transaction), Create a transaction Classification: read.
  • Get contacts (get_contacts), Get all contacts after date Classification: read.
  • Get Transaction Stuff (Advanced) (get_transaction_stuff), Get Transaction Stuff 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

Authenticationcustom
Supported objects5
Supported actions5
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Upsert Contact (Duplicates) Yes No Update or create bloomerang contact using duplicates
Upsert Contact (Search) Yes No Update or create bloomerang contact using the search
Create a transaction (Advanced) Yes No Create a transaction
Get contacts Yes No Get all contacts after date
Get Transaction Stuff (Advanced) Yes No Get Transaction Stuff

Supported actions

Upsert Contact (Duplicates) · Read

Update or create bloomerang contact using duplicates

upsert_contact_duplicates · Risk: low · Retry: safe

Inputs

  • first_name · string · Optional, First name
  • last_name · string · Optional, Last name
  • organization_name · string · Optional, Organization name
  • street · string · Optional, Street
  • phone_number · string · Optional, Phone number
  • email_address · string · Optional, Email
  • type · string · Optional, Type
  • contact_json · object · Required, The Contact JSON
Upsert Contact (Search) · Read

Update or create bloomerang contact using the search

upsert_contact_search · Risk: low · Retry: safe

Inputs

  • search · string · Required, The text to search
  • skip · number · Optional, The number of items to skip before starting to collect the result set.
  • take · number · Optional, The number of items to include in the result set.
  • contact_type · string · Optional, Select the object
  • contact_json · object · Required, The Contact JSON
Create a transaction (Advanced) · Read

Create a transaction

create_transaction · Risk: low · Retry: safe

Inputs

  • transaction · object · Required, The Transaction JSON
Get contacts · Read

Get all contacts after date

get_contacts · Risk: low · Retry: safe

Inputs

  • last_modified_date · string · Required, The date to search for contacts modified after
  • skip · number · Optional, The number of items to skip before starting to collect the result set.
  • take · number · Optional, The number of items to include in the result set.
  • is_favorite · boolean · Optional, Filters constituents to only constituents the user has favorited.
  • type · string · Optional, Select the object
  • order_by · string · Optional, Available values : Id, CreatedDate, LastModifiedDate
  • order_direction · string · Optional, Available values : Asc, Desc
  • id · array · Optional, Filters results based on the ID for the constituent.
Get Transaction Stuff (Advanced) · Read

Get Transaction Stuff

get_transaction_stuff · Risk: low · Retry: safe

Inputs

  • transaction_stuff · string · Required, Select the object
  • skip · number · Optional, The number of items to skip before starting to collect the result set.
  • take · number · Optional, The number of items to include in the result set.
  • id · array · Optional, Filters to object with the IDs in the list (pipe-separated)
  • include_inactive · boolean · Optional, Filters to either active or inactive funds
  • has_goal · boolean · Optional, Filters to campaigns that have either non-zero-dollar or zero-dollar goals
  • limit · string · Optional, Filters to funds with names that match any part of the search string

Setup

Setup

  1. Add the Bloomerang 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-bloomerang@0.1.1; 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 Bloomerang 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-bloomerang@0.1.1 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