Salesforce Custom Object Mappings — iRaiser Connect

This document describes the mapping between iRaiser (Kentaa) custom Salesforce objects and the iRaiser public API. It is intended for developers building a Salesforce application that replicates the data synchronization currently handled by iRaiser Connect.

API Documentation: https://developer.iraiser.eu/cfp-api/#introduction API Base URL: https://api.kentaa.nl/v1

Table of Contents

1. Object Hierarchy
2. General Conventions
3. Kentaa_Segment__c
4. Kentaa_Project__c
5. Kentaa_Company__c
6. Kentaa_Team__c
7. Kentaa_Action__c
8. Kentaa_ActionQuestion__c
9. Kentaa_Donation__c
10. Kentaa_NewsletterSubscription__c

1. Object Hierarchy

The iRaiser platform has a hierarchical structure. Parent objects must exist in Salesforce before child objects can be linked.

Site
 └── Segment
      └── Project
           ├── Company
           │    └── Action
           │         ├── ActionQuestion
           │         └── Donation
           └── Team
                └── Action
                     ├── ActionQuestion
                     └── Donation

Lookup cascade rule: When inserting a child object, the direct parent lookup is set, and any higher-level lookups (e.g. Project, Segment) are copied from the parent record already in Salesforce — not resolved from the API. This means parent objects must be synced first.

Donations can be attached to any level: Action, Team, Company, Project, or Segment.

2. General Conventions

Upsert strategy

All objects use upsert on the KentaaId__c external ID field. This ensures idempotent inserts and updates.

KentaaId__c (Object Key)

Each object has a unique KentaaId__c value derived from its API id. The exact format of this key is an implementation detail (e.g. prefixed with the object type). Your implementation should choose a consistent scheme to generate unique external IDs per object type.

Name field

The standard Salesforce Name field is populated as described per object and truncated to 80 characters.

HTML stripping

The description fields from the API may contain HTML. These are stored as plain text in Salesforce (HTML tags stripped).

Date/time handling

• Fields of type DateTime are stored as ISO 8601 strings (e.g. 2025-03-15T10:30:00Z).
• Fields of type Date are stored as ISO 8601 date strings (e.g. 1990-06-15).

Text truncation

Text values are truncated to the field’s defined length before upserting.

Blank values

Fields with blank/nil values are skipped (not sent to Salesforce), except for boolean fields which are always sent.

Consent selection

Where consent fields are mapped, the logic is: - Filter the consents array for consent_status = "granted". - Then find the first consent matching the relevant consent_type (e.g. "terms_conditions" for actions/donations, "newsletter_subscription" for newsletter subscriptions).

Donation filtering

Only donations with payment_status in ["paid", "refunded", "chargedback"] and a non-zero total_amount are synced.

3. Kentaa_Segment__c

Field Mapping

Relationships

None — Segment is the top-level object.

4. Kentaa_Project__c

Field Mapping

Relationships

5. Kentaa_Company__c

Field Mapping

Relationships

Parent cascade logic:

6. Kentaa_Team__c

Field Mapping

Relationships

Parent cascade logic:

7. Kentaa_Action__c

An action represents a personal fundraiser page created by a participant, linked to a project, segment, team, or company.

Field Mapping — Identification & Timestamps

Field Mapping — Fundraiser Personal Details

Personal details come partly from the action object itself (first_name, infix, last_name) and partly from the owner sub-object. The owner is a subset of the User object.

Important: The action owner object in the API response only contains id, first_name, infix, last_name, email, and avatar_url. The extended fields (address, phone, gender, birthday, etc.) require fetching the full User object via GET /v1/users/:owner_id.

Field Mapping — Action Details

Field Mapping — Statistics

Field Mapping — Team & Participation

Field Mapping — Consent

Selection logic: Filter consents array for consent_status = "granted" AND consent_type = "terms_conditions". Use the first match.

Relationships

Parent cascade logic: The action’s parent determines which lookups are set. The parent can be a Team, Company, Project, or Segment (derived from team_id, company_id, project_id, segment_id on the API response). Higher-level lookups are inherited from the parent record in Salesforce.

Note: Parent objects must already exist in Salesforce before an action can be linked. The lookup is done by KentaaId__c on the parent record.

8. Kentaa_ActionQuestion__c

Action questions are sign-up form questions answered by the fundraiser when creating an action. They are available as the questions array on the action API response.

Filtering: Questions with an empty/blank answer are skipped and not synced to Salesforce.

Field Mapping

Relationships

9. Kentaa_Donation__c

Filtering: Only donations with payment_status in ["paid", "refunded", "chargedback"] and a non-zero total_amount are synced.

Field Mapping — Identification & Timestamps

Field Mapping — Donor Details

Field Mapping — Donor Address

Address fields come from the address sub-object on the donation. Only populated if donation.address is present.

Field Mapping — Payment Details

Field Mapping — Additional Fields

Field Mapping — Consent

Selection logic: Filter consents for consent_status = "granted" AND consent_type = "terms_conditions". Use the first match.

Relationships

Target cascade logic: The donation’s target entity determines which lookups are set. The target is determined by the most specific ID present on the donation (action_id > team_id > company_id > project_id > segment_id). Higher-level lookups are inherited from the target record in Salesforce.

10. Kentaa_NewsletterSubscription__c

Field Mapping

Field Mapping — Consent

Selection logic: For newsletter subscriptions, filter consents for consent_status = "granted" AND consent_type = "newsletter_subscription". Use the first match.

Relationships

Entity resolution: A newsletter subscription has an entity with entity_type and entity_id. The entity can be a Project or Segment. Look up the corresponding record in Salesforce by KentaaId__c.