Integrations

FundraisingBox

Sync donors, donations and membership data without additional hosting.

FundraisingBox is a native data integration. Audryo runs the import, background synchronization and webhook receiver. No additional server or automation account is required.

Connect

  1. Open Settings → Integrations → FundraisingBox.
  2. Enter the API token for an account with the API Package and read access to people, projects and sources. Donations and recurring payments are imported when that user can read them. Without that permission, people still synchronize and payment fields stay empty. Save the connection.
  3. Optionally enter additional custom field IDs. The default source timezone is Europe/Berlin; use your FundraisingBox account's timezone.
  4. Choose Verify access. Under Review and synchronize, group related tags into fields. One tag becomes yes or no. Tags that share a field store the tag name, so Webinar 09 and Webinar 10 stay one field. Suggestions use only the tag name and can be edited. Saving the mapping does not import people.
  5. Choose Preview contacts, then Start first import. Preview reads source data but does not import people, record events, grant consent or start journeys. Progress updates automatically.
  6. Give FundraisingBox support the displayed webhook URL, username audryo and the one-time password. Request person create/update/delete/restore, donation and recurring-payment notifications. HTTP Basic authentication over HTTPS is required. JSON and XML notifications both work: Audryo treats the notification as a hint and reads canonical data back through the API.

API tokens are encrypted and never returned. The webhook password is encrypted, returned only on create/rotation, and displayed only in the current setup session. Replacing it invalidates the previous password immediately.

Imported data

SourceAudryo representation
First/last name, birthday, title, salutation, greeting, company and main emailContact attributes, using first_name, last_name, birthday, email, etc.
Manual tagsTags prefixed with FundraisingBox: ; unrelated Audryo tags remain intact
Tags mapped in Review and synchronizeOne tag becomes a yes/no field such as fundraisingbox_member. Tags that share a field store the matching tag names. A person with none of those tags gets false, or an empty value when the field is shared. Removing the mapping clears the field on the next sync.
Selected membership tag IDsfundraisingbox_is_member, including tags mapped to that same field; unknown until configured
Confirmed donationsfundraisingbox.donation.recorded events with the original donation date
Confirmed donations with received_atfundraisingbox.donation.received events with the receipt date
Donation source/projectOriginal IDs plus readable source and project names on events
Received donation count, latest date/amount/currency/project/sourcefundraisingbox_donation_count, fundraisingbox_last_donation_at, fundraisingbox_last_donation_amount, etc.
Received totalsfundraisingbox_total_by_currency; currencies are never added together
Active recurring agreementsfundraisingbox_recurring_payments, fundraisingbox_active_recurring_count, fundraisingbox_has_active_recurring, fundraisingbox_recurring_intervals
Selected custom fieldsObjects keyed by stable source field IDs; no custom fields are copied by default

A contact can have several recurring agreements and can also make one-time payments. There is no single contact-level “donation type” or “interval”. Donation records preserve a recurring-payment reference/interval when supplied by the API; missing references are not guessed from a donor's other agreements.

Bank details, card details, SEPA mandates, free-text donor messages and raw webhook bodies are not stored. Test donations are excluded.

Identity and field ownership

Contacts use a stable ID scoped to the connection and FundraisingBox person ID. Changing an email updates the same person. Different people sharing an email are not merged automatically. Existing Audryo contacts from other sources are not matched by email; review existing data before importing to avoid duplicate people.

The connector owns its standard imported fields and all fundraisingbox_* attributes. Changes, including cleared fields and removed source tags, synchronize from FundraisingBox. Other custom attributes and unrelated tags remain intact.

History and live behavior

The first import records history without emitting journey triggers, conversions, goal exits or outbound contact updates. Imported people are excluded from existing signup/audience-entry journeys, including the periodic audience poll. Journeys first activated after import deliberately include those people. Pausing and resuming an existing journey does not reset its historical baseline. Other future triggers, such as birthdays and new paid donations, behave normally.

A new donation with an original date before the first import completed is also historical, even if it arrives later. Repeated notifications or overlapping API pages cannot create duplicate donation events. Corrections update stored event facts without replaying its original journey trigger. Counts/totals are recomputed from canonical source records, never incremented for each webhook.

After setup, webhooks queue updates as FundraisingBox sends them. Those updates read changes since the previous sync, with a 10-minute overlap. Once a day, Audryo reconciles the whole account, including removed people and reversed donations. Recurring agreements are scanned completely on each run because the documented list API has no update-date filter. Source removals can therefore take until the next daily reconciliation to appear. A webhook received during an active sync schedules a follow-up run.

ID-only list responses are hydrated through the canonical detail endpoints. Large first imports can take longer when this requires one request per record. Each API page and projection batch is checkpointed transactionally. Network/server failures retry automatically. Rate limits honor x-ratelimit-reset. Persistent failures appear in the integration status; Sync now starts a safe fresh scan. Progress is a record count and current stage, not an estimated percentage.

Importing people, donations, membership tags or newsletter flags never grants marketing consent or mailing-list membership. Import separately documented consent through Audryo's consent ledger. A source wants_no_email block creates an Audryo suppression; clearing the source flag never silently removes an existing block.

A person missing from a full scan is looked up directly. Only a canonical 404 confirms removal and erases the person in Audryo; a changing list order cannot erase someone by itself. Local erasure also scrubs source snapshots and keeps a source-ID tombstone, so later syncs cannot resurrect the person. Restore notifications do not override an erasure. Review the records before intentionally reimporting.

Pause sync cancels the current run and rejects webhooks with a retryable status. Disconnect removes the connection, credential, run log and source snapshots; imported contacts, events, consent and suppressions remain in Audryo.

API

The generic connection lifecycle is at /v1/projects/{projectId}/integration_connections, with provider fundraisingbox. Member actions are verify, preview, sync and rotate. Reads require read; configuration, previews and synchronization require write. The public events endpoint requires its separate webhook Basic Auth credentials.

See the OpenAPI contract for schemas.

FundraisingBox references