The problem
If you run fundraising or memberships on Salesforce, FinDock already handles the payment. It matches the money from your forms to a contact and collects it.
That is the moment for the next email, such as a thank-you for a donation or a confirmation for a sign-up. 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.
What the app does
JB Quicksend sends a transactional email from Salesforce the moment something happens. A transactional email is a one-to-one message triggered by a single event, such as one donation.
You set this up as a send. A send is one rule: when this happens, send this email with this data. You give each send a name, such as “Donation thank-you”.
At launch, FinDock is the trigger and Marketing Cloud Engagement is the email platform. FinDock comes as a trigger pack called FinDock Triggers, with two events.
- Donation received. FinDock matches the payment from a form to a contact and collects it.
- Sign-up confirmed. FinDock matches a form without a payment to a contact.
When marketing adds a new field to an email in Marketing Cloud Engagement, you map it in the send. No Apex and no Flow rebuild.
Quicksend is a Salesforce managed package (an app you install into your org from one versioned package). It runs inside Salesforce, so there is nothing to host and no middleware.
See it in a demo
This 4-minute demo, recorded in a test org, walks through the Home page, a send, the field defaults, and the connection to Marketing Cloud Engagement.
Read the transcript
This is JB Quicksend. It sends a transactional email from Salesforce the moment something happens: a confirmation, a thank-you, or a receipt.
You build the email in your email platform. Quicksend decides when it goes out, and which Salesforce data fills it in.
The Home page walks you through the set-up. First, connect your email platform. At launch, that is Marketing Cloud Engagement.
Next, the trigger pack. A trigger is the event that starts a send. At launch, that is FinDock Triggers.
FinDock records donations and sign-ups across several objects, so it takes logic to know when a donation has really come in. The FinDock trigger pack holds that logic. You pick an event, such as Donation received or Sign-up confirmed.
Field defaults say which Salesforce field fills which email field. For example, the first name comes from the Person Account. You set them once, and every new send starts with them filled in.
Choose New send, and a wizard takes you through four steps. Pick the trigger. Pick the email: Quicksend lists the transactional emails and journeys you already set up in Marketing Cloud Engagement, with their fields. Check the personalisation. The field defaults fill every email field with a matching name, and Quicksend highlights any field without one. Then send a test to your own inbox, and set the send live.
For FinDock, each send has a send code. Your form puts that code on the FinDock Inbound Report, so Quicksend knows which send to use.
The Status panel shows how many sends are active, how many emails went out, and when the last one was sent.
The Sends tab lists every send: its trigger, its email and connection, its status, how many emails it sent, and when it last sent one.
Open a send to see it on one page. This one sends the Form Subscribe Email when FinDock confirms a sign-up.
You see the data it uses, the email and the business unit it goes through, and the last send and last error. From here you can send a test, or pause the send.
Personalisation shows which Salesforce field fills each email field. When you add a field to the email in Marketing Cloud Engagement, choose Check for new fields. Then choose Edit, and pick the Salesforce field that fills it. No change to a Flow or Apex.
On the Field defaults tab you manage the defaults that every new send starts with. That saves time when several emails use the same fields. Changing a default later does not change the sends you already have.
Settings holds your connections. Each connection is one Marketing Cloud Engagement business unit, set up with Named Credentials in Salesforce Setup. You can add more than one, and test each one here.
You set up each send inside Salesforce. A new field takes a field default, not a change to a Flow or Apex.
JB Quicksend is expected at the end of 2026. To hear first, join the early-access list on the JB Quicksend page at journeybuilders.eu.
How it works
Create a send in four steps
Quicksend guides you through each send in four steps.
- When. Choose the trigger and the event, for example FinDock Triggers and Donation received.
- Email. Choose a Marketing Cloud transactional email or journey. You can search the list and filter it by type and status.
- Personalise. Quicksend fills the email fields from your field defaults. Change any field for this send only, or save the change as the new default. Quicksend highlights fields that have no default. Preview the email with data from a recent FinDock Inbound Report.
- Test and go live. Send a test to your own inbox. For FinDock, Quicksend gives you a send code. Put that code in the JB Quicksend field of the Inbound Report your form creates.
Field defaults fill the email for you
An email field is a placeholder in the email that Quicksend fills with Salesforce data. Field defaults set which Salesforce field fills which email field, unless you change it in a send. Quicksend matches them on the email field name.
Examples are Contact First Name, Contact Email, Installment Amount and Campaign Public Name.
Changing a default later never changes the sends you already have. When marketing adds a field to an email in Marketing Cloud Engagement, choose Check for new fields on the send to find it, then map it under Personalisation.
See what each send is doing
Each send has a status: Draft, Active or Paused. You can pause a send and resume it later without losing its setup.
Each send also shows how many emails it has sent, when it last sent and its last error.
Set up from the Home page
The Home page in Quicksend has a setup checklist.
- Connect your email platform, and check it with the Test connection button.
- Check that Quicksend has found FinDock.
- Set your field defaults.
- Create your first send.
- Send a test.
How Quicksend connects
Quicksend connects to Marketing Cloud Engagement through Named Credentials and your business unit. Named Credentials are Salesforce settings that store the address of an outside system and how to sign in to it. A setup guide for the Marketing Cloud installed package is planned.
On the FinDock side, Quicksend listens to FinDock’s InboundReport__c and Installment__c objects.
What is planned
The aim is to send transactional email from Sales Cloud and Service Cloud in general, not only from FinDock. These additions are planned.
- More trigger types. A Salesforce record change, when a record is created or a field changes, on any object. And Flow, so you can call a send as an action from your own Flow.
- More email platforms. Quicksend calls each email platform a connection. Marketing Cloud Next and Mailchimp are planned.
Get it
JB Quicksend 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 Quicksend 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 trigger types and email platforms come next.
If you would rather wait for general availability, join the list anyway and we will tell you when it ships.