Summary
iPaaS.com Transaction records can be transferred to Blackbaud Raiser's Edge NXT as Gift records. Each Transaction Line a subscriber tags as a gift becomes one Raiser's Edge NXT gift, created through the Blackbaud SKY API (POST /gift/v1/gifts). Per-line tagging on a single Transaction-Line custom field decides which lines become gifts, so a single Transaction can contribute its gift line(s) to Raiser's Edge NXT while other lines are handled elsewhere. The gift is recorded against the correct constituent automatically — the integration links (and, if necessary, first transfers) the transaction's customer to a Raiser's Edge NXT constituent before writing the gift. Gift creation is the only supported action; gift update and delete are handled directly in Raiser's Edge NXT.
This documentation covers three mapping collections that work together as one transfer:
Add Raiser's Edge NXT Gift FROM iPaaS.com — the parent Transaction collection (dispatch, constituent resolution, external-id linkage).
Add Raiser's Edge NXT Gift Line FROM iPaaS.com — the per-line gift detail (one gift per line).
Add Raiser's Edge NXT Gift Payment FROM iPaaS.com — the transaction's payments, reduced to a single payment method per gift.
ID Format
Manual Sync ID Format
Enter the iPaaS.com Transaction ID — a numeric value identifying the Transaction record in iPaaS.com. The integration retrieves the full Transaction (with its lines and payments) and writes each Gift line to Raiser's Edge NXT.
External ID Format (saved after sync)
After a successful transfer, iPaaS.com records a parent external-id link on the Transaction in the form {TransactionNumber}|{TransactionType} (example: 10042|Gift), and records the Raiser's Edge NXT gift id on each Gift Transaction Line. Each created gift is paired back to its source line by SequenceNumber, because the gift filter includes only a subset of the transaction's lines. These links keep repeated transfers of the same transaction from creating duplicate gifts.
Deleted Record Support
Gift Delete and Update are not supported in the outbound direction. Only gift creation is written to Raiser's Edge NXT; changes to a gift after it is created are made directly in Raiser's Edge NXT.
Custom Field Support
Subscribers can set custom fields on the created Raiser's Edge NXT gift by mapping them on the Add Raiser's Edge NXT Gift Line FROM iPaaS.com collection. Each such mapping's destination is a Raiser's Edge NXT gift custom-field category and its source supplies the value; every mapped custom field is written to the gift after the gift record is created. The destination must match a Raiser's Edge NXT gift custom-field category name exactly — the integration resolves the category by name. If a mapped category does not exist on the tenant, the integration attempts to create it; some Blackbaud installations restrict category creation (typically HTTP 403), in which case the category must be created manually in Raiser's Edge NXT before values can be written to it (see System Caveats and Known Limitations).
Mapping Collection Status
Status: Enabled
Trigger Events: Transaction Created (subscribed in the iPaaS.com subscription configuration's Outbound Data Flows section — automatic transfers will not occur until enabled). Manual Sync is also available.
Prerequisite — Constituent Link
A gift in Raiser's Edge NXT must be attached to a constituent. The subscriber maps only the iPaaS.com CustomerId on the parent collection; the integration handles the constituent link end to end:
Before the gift is written, the integration checks whether the transaction's customer is already linked to a Raiser's Edge NXT constituent.
If not linked, it transfers the customer first (through the Customer FROM iPaaS.com flow) and waits for that transfer to complete, so the gift has a constituent to attach to. The Customer transfer's collision-handling configuration determines how an existing constituent is matched and linked.
It then records the gift against the resolved constituent. Subscribers do not map a constituent id.
Note: If the customer cannot be linked to a constituent (for example, the customer transfer fails), the gift transfer stops with a clear message and no gift is created.
Duplicate or Conflicting Mappings
Gifts are written one-way, from iPaaS.com to Raiser's Edge NXT — there is no inbound (TO iPaaS.com) gift collection, so there is no bidirectional-overwrite risk for gifts. Within the outbound direction, the Raisers Edge NXT LineType tagging convention keeps gift, membership, and retail lines from being processed by the wrong collection: each line type has its own filtered parent collection, and only lines tagged Gift are processed by this flow.
Supported Child Collections
Add Raiser's Edge NXT Gift Line FROM iPaaS.com — per-line gift detail (type, amount, date, fund, reference). Only lines tagged Gift are included. Each line becomes one gift.
Add Raiser's Edge NXT Gift Payment FROM iPaaS.com — the transaction's payments (no filter). Read to resolve the single payment method recorded on the gift.
System Caveats
Raiser's Edge NXT Caveats
Fund must exist: The fund referenced by FundId must exist in the subscriber's tenant. The BlackbaudFundGetIdByLookupId function resolves a fund by its lookup id; an unmatched lookup id causes the gift to be rejected.
Gift type must be valid: The Type value must be a gift type Raiser's Edge NXT recognizes (see the Gift Line mapping table). An unrecognized value causes the gift to be rejected.
Gift custom-field categories: A mapped gift custom-field category must exist on the tenant, or the integration attempts to create it. If the Blackbaud installation restricts category creation, the category must be created manually in Raiser's Edge NXT.
Single payment method per gift: Raiser's Edge NXT records one payment method per gift. With more than one payment on the transaction, the gift records Other; with a single payment, it records that payment's method.
Rate Limiting and Daily Quota: Blackbaud enforces a per-second rate limit and a daily call quota on the SKY API. When either is reached, the transfer is automatically rescheduled and resumes after the window resets — no subscriber action is required. Permission errors (for example, an inactive credential or a missing scope) are treated as permanent failures and appear in Dashboard / Integration Monitoring / Error Logs without being rescheduled.
iPaaS.com Caveats
Line tagging is required: Each Transaction Line must carry the Raisers Edge NXT LineType custom field with the appropriate value. A subscriber using a different scheme to identify gift lines must adjust the filters on the parent and Gift Line collections accordingly.
Field references in dynamic formulas use PascalCase (e.g.,
Payments,Parent.TransactionNumber,SequenceNumber) — required by the iPaaS.com mapping formula engine.
Setup Requirements
For full setup steps see the Installation Instructions and Connections and Settings articles. The integration-wide setup (Blackbaud Private Application registration, OAuth scope, subscription settings) is documented there and not repeated here. In addition, before enabling this flow:
Ensure each source Transaction Line carries the Raisers Edge NXT LineType custom field, populated with Gift for gift lines.
Ensure the funds referenced by the FundId mapping exist in your Raiser's Edge NXT tenant, and update the fund lookup id in the mapping to match your tenant.
Ensure the Customer FROM iPaaS.com flow is configured so the transaction's customer can be linked to a constituent.
Integration Flow
When a Transaction transfer is dispatched from iPaaS.com to this flow, the integration:
Resolves the constituent link. Checks whether the transaction's customer is linked to a Raiser's Edge NXT constituent; if not, transfers the customer first and waits for it to complete (see Prerequisite — Constituent Link).
Selects the gift lines. Includes only Transaction Lines whose Raisers Edge NXT LineType equals Gift.
Creates each gift. For each gift line, builds the gift from the mapped fields (type, amount, date, single-fund split, and one resolved payment method) and creates it via
POST /gift/v1/gifts.Writes gift custom fields. Writes any gift custom fields mapped on the Gift Line collection to the created gift.
Stamps the links. Records the Raiser's Edge NXT gift id back onto the source Transaction Line (paired by SequenceNumber), and, after all lines succeed, records the parent external-id link {TransactionNumber}|{TransactionType} on the Transaction.
Note: If any line fails, the parent external-id link is not recorded, so the transaction remains eligible for retry. Lines that already wrote successfully keep their gift-id links and are not re-created.
Mappings
Add Raiser's Edge NXT Gift FROM iPaaS.com
Description: Parent Transaction collection. Dispatches each Gift-tagged line to a Raiser's Edge NXT gift, resolves the constituent from the mapped customer, and records the composite external-id link on success.
Mapping Filter: Fires only for Transactions that contain at least one Gift-tagged line — the filter includes the Transaction when any line's Raisers Edge NXT LineType custom field equals Gift.
Field Mapping Table
Mapping Type | Source (iPaaS.com) | Destination Field | Description |
Static |
| TransactionType | Required. Routes the transaction's lines to Raiser's Edge NXT gift records. Fixed value Gift for this collection. If blank, the transfer stops with a clear message. |
Field | CustomerId | CustomerId | Required. The transaction's customer, used to resolve (and if necessary establish) the Raiser's Edge NXT constituent link. Subscribers do not map a constituent id. |
Field | TransactionNumber | TransactionNumber | Required. Identifies the source transaction and forms the left half of the parent external-id link. |
Dynamic Formula |
| GiftPaymentMethod | Recommended. Resolves the single payment method recorded on the gift: Other when the transaction has more than one payment, the single payment's method when it has one, empty otherwise. If unmapped, the integration applies the same logic automatically. The |
Add Raiser's Edge NXT Gift Line FROM iPaaS.com
Description: Child of the parent Gift collection. Carries the per-line gift detail; each Gift-tagged line becomes one gift.
Mapping Filter: Line-scoped — a line is included when its Raisers Edge NXT LineType custom field equals Gift.
Field Mapping Table
Mapping Type | Source (iPaaS.com) | Destination Field | Description |
Dynamic Formula |
| Reference | Required. Produces a unique per-line reference (example: |
Static |
| Type | Required. The Raiser's Edge NXT gift type — the classification of the gift, not how it was paid. Valid values include Donation, GiftInKind, Pledge, PledgePayment, RecurringGift, RecurringGiftPayment, PlannedGift, Stock, SoldStock, MatchingGiftPledge, MatchingGiftPayment, Other. An unrecognized value is rejected by Raiser's Edge NXT. |
Field | ExtendedPrice | Amount | Required. The gift amount; must be greater than zero. |
Dynamic Formula |
| Date | Recommended. Sets the gift date from the parent transaction's created date. Defaults to the current date and time if omitted. |
Dynamic Formula |
| FundId | Required. The fund the gift is recorded against; Raiser's Edge NXT requires a fund on every gift. BlackbaudFundGetIdByLookupId resolves a fund by its lookup id. Placeholder — replace during implementation: |
Field | SequenceNumber | SequenceNumber | Recommended. Maps the source line's sequence number so the created gift id can be linked back to the correct line. If unmapped, the gift is still created but the gift-id link is not recorded on the iPaaS.com line. |
Optional per-line overrides: PaymentReference and PaymentReferenceDate may be mapped on the line to set the payment reference recorded on the gift explicitly, instead of taking it from the transaction's payments.
Add Raiser's Edge NXT Gift Payment FROM iPaaS.com
Description: Child of the parent Gift collection. Carries the transaction's payments so the gift's single payment method can be resolved.
Mapping Filter: None — every payment on the transaction is included.
Field Mapping Table
Mapping Type | Source (iPaaS.com) | Destination Field | Description |
Dynamic Formula |
| PaymentMethod | Recommended. Carries each payment's method (for example Cash, CreditCard, PersonalCheck, DirectDebit) so the parent's GiftPaymentMethod formula can resolve the single method recorded on the gift. The |
Optional: Amount (informational — the gift amount comes from the Gift Line), Reference, and ReferenceDate may also be mapped; reference values are used on the resulting gift payment when a single payment is selected.
Error Handling
Errors from this flow appear in iPaaS.com Dashboard / Integration Monitoring / Error Logs. For the full catalog of error messages, descriptions, and resolution steps see the Error Messages article. Common gift-specific failures include a missing or unrecognized Type, an Amount that is zero or negative, a FundId whose lookup id does not resolve to a fund in the tenant, and a customer that cannot be linked to a constituent — each stops the transfer with a clear message and no gift is created.
Testing & Validation
Test Scenarios
Create an iPaaS.com Transaction with one Gift-tagged line (amount greater than zero, a valid gift type, and a fund that exists in the tenant) for a customer already linked to a constituent. Dispatch the transfer and verify one gift is created in Raiser's Edge NXT and both the parent and line external-id links are recorded.
Repeat scenario 1 for a customer not yet linked to a constituent. Verify the customer is transferred first, the constituent is linked, and the gift is then created against it.
Create a Transaction that mixes a Gift line with membership and/or retail lines. Verify only the Gift line is written as a gift and the non-gift lines are excluded.
Create a Transaction with no Gift line (membership and/or retail only). Verify the gift flow does not fire and no gift is created.
Re-dispatch an already-transferred Transaction. Verify no duplicate gift is created (the recorded gift-id link prevents re-creation).
Create a Transaction with a single payment and verify the gift records that payment's method; create one with multiple payments and verify the gift records Other.
Configure a Gift line whose FundId lookup id does not exist in the tenant. Verify the transfer fails with a clear message and no gift is created.
Manually sync a Transaction using its iPaaS.com Transaction ID from the Manual Sync page and verify the transfer succeeds end to end.
Validation Checklist
The Outbound Data Flows subscription for Transaction Created is enabled in the iPaaS.com subscriber portal.
Every source Transaction Line carries the Raisers Edge NXT LineType custom field, populated with Gift for gift lines.
The FundId mapping references a fund lookup id that exists in the subscriber's Raiser's Edge NXT tenant (the example
"GARDEN"value has been replaced).The Type value on the Gift Line mapping is a gift type Raiser's Edge NXT recognizes.
The Customer FROM iPaaS.com flow is configured so the transaction's customer can be linked to a constituent.
Any gift custom-field categories you map exist in the tenant, or the Blackbaud installation permits category auto-creation.
Additional Notes
Out of Scope
Membership and retail (Product) dispatch: At the time this documentation was written, only the Gift line type writes to Raiser's Edge NXT. Membership and Product line types are recognized by the routing convention but are not yet written to Raiser's Edge NXT.
Gift Update and Delete: Only gift creation is supported; changes to a gift after creation are made directly in Raiser's Edge NXT.
Inbound gifts (TO iPaaS.com): Gifts are written one-way, from iPaaS.com to Raiser's Edge NXT.
Other Blackbaud objects: Campaigns, Appeals, Events, and other Blackbaud objects not listed in the integration's Supported Data Flows are not transferred by this flow.
Operational Notes
Duplicate prevention relies on iPaaS.com external-id tracking rather than a Raiser's Edge NXT-side lookup before create. Once a gift id is recorded on a line, iPaaS.com will not create the gift again. The one case where a duplicate can occur is a subscriber wholesale-recreating a source Transaction so its earlier external-id links are lost.
Fund lookup runs once per gift line. When many lines reference the same fund, each triggers a lookup — a consideration for large transactions.