JB Findock Marketing Triggers

The problem

If you run fundraising or memberships on Salesforce, FinDock already handles the payment. It records the payment intent, schedules the instalments, matches incoming money and deduplicates contacts.

The moment a payment is matched and collected, you have everything you need for the next email. That is the thank-you, renewal reminder or tax-receipt confirmation that keeps a donor or member.

Getting that email out of Salesforce and into Marketing Cloud Engagement today means one of three things.

• A Flow with an HTTP Callout that needs an admin every time marketing wants a new field.
• Hand-written Apex that nobody on the team wants to touch.
• A batch job that runs every few hours, so the donor hears from you tomorrow instead of now.

None of these is a good base for a fundraising programme.

What the app does

JB Findock Marketing Triggers is a Salesforce managed package (an app you install into your org from one versioned package). It listens to FinDock’s own objects. When a payment is matched and collected, it sends the record to a Marketing Cloud journey (an automated email programme). The journey sends a transactional email, a one-to-one message triggered by that payment.

The field mapping lives in a configurator screen, not in a Flow. A merge field is a placeholder the email fills from a Salesforce field. When marketing wants a new one, they pick it from a dictionary an admin has approved and send the email themselves. No Apex, no Flow rebuild, no ticket.

Because the package runs inside Salesforce, there is nothing to host, nothing to monitor and no middleware to licence.

How it works

The package has three connected pieces.

1. Source connector. Listens to FinDock’s InboundReport__c and Installment__c objects and joins the two streams. It fires only when a payment is genuinely matched and collected, not before.
2. Mapping configurator. A screen where marketers choose, per campaign, which Salesforce fields go to which data extension columns. A data extension is the table Marketing Cloud stores contact data in. An admin curates the list of available fields in a data dictionary, so marketers can only pick from fields that are safe to send.
3. Flow trigger. An invocable Apex action, which is an action you can call from any Flow you already have. Use it to combine the app with your wider automation.

The package discovers journeys and data extensions through the Marketing Cloud REST API. Marketers pick a journey from a list of real journey names, not a list of IDs.

We built the source and destination connectors as separate parts. The first release connects FinDock to Marketing Cloud. Marketing Cloud Next, Mailchimp and Spotler are on the roadmap as further destinations, using the same configurator, field dictionary and Flow component.

Get it

JB Findock Marketing Triggers will ship as a managed package at launch, expected at the end of 2026. Pricing is on request. Use the Request information page, or join the early-access list below to hear first.

Early access

We expect to launch JB Findock Marketing Triggers at the end of 2026. We are releasing it in stages, starting with a small group of design partners who run FinDock with Marketing Cloud.

The team that built the app helps each design partner set it up. Design partners get discounted licence terms in exchange for a reference call and case-study rights. They also help decide which destination ships next and which fields go into the curated dictionary.

If you would rather wait for general availability, join the list anyway and we will tell you when it ships.