Email & Calendar Integration

REDA sends real email — mass emails to council participants, visitor-access and expense notifications — and it writes real calendar entries when you book a showing or schedule an inspection. But the plumbing that makes those land in inboxes and calendars is Salesforce's, not REDA's: the Gmail and Outlook integrations, email deliverability, org-wide addresses, and calendar sync. So this article keeps that plumbing short and points to Salesforce's documentation. What it covers in full is which REDA features actually depend on it — and one feature you should not try to set up because it isn't in the released edition. After reading, you'll know exactly which integration pieces REDA relies on and which are pure Salesforce.

Which REDA features send email

Several REDA features generate outbound email, and all of them ride Salesforce's email delivery:

• Mass Email — the Mass Email quick action on a Council Event record sends to the event's participants through a configurable send flow (see Configuring Mass Email).
• Notifications — REDA ships custom notification types, including Permit Visitor Access Notification and Expense Reconciliation Calculation Notification, delivered in-app and by email.
• Job-completion emails — several REDA batch actions email the initiator when the job finishes. For example, submitting an inflation adjustment shows: "Job to calculate inflation adjustment is submitted. You will receive an email when the job is complete."

To audit what REDA has sent, use Salesforce's own email tracking — the email history logged on each record (and, where enabled, Enhanced Email tracking). A dedicated REDA Email Messages (Sent/Received) report type ships with REDA and sits under Other Reports in the New Report picker. It is built on EmailMessage and covers the emails captured by the REDA Email Integration.

Email deliverability for REDA email

None of REDA's email arrives unless the Salesforce org is set up to send it. Three org-side controls matter:

• Email Deliverability. If the org's deliverability access level doesn't allow outbound email, REDA's mass emails and notifications simply won't send. Set it to allow the email you intend to send.
• Organization-Wide Addresses. A verified branded address (for example, notifications@yourfirm) is the preferred sender for REDA mass email — but note that no org-wide address ships with REDA or exists by default. Until your administrator creates and verifies one in Setup, the branded-sender option simply won't be available, and REDA's Mass Email will fall back to sending as the current user or the default workflow user. Add and verify an org-wide address first, then point Mass Email at it (see below).
• SPF / DKIM / DMARC. These DNS-side authentication records keep REDA's outbound email out of spam folders. They're standard email authentication with no REDA-specific values.

REDA Mass Email sender configuration

REDA's Mass Email lets you choose who the email comes from. The sender can be the current user, the default workflow user, or an organization-wide address. The org-wide address is the best choice where you want mail to arrive from a branded address rather than an individual — but it's only selectable once your administrator has verified one in Setup; a fresh org has none. Configure this once as part of setting up mass email (see Configuring Mass Email).

Google / Microsoft integration

Connecting REDA to Gmail or Microsoft 365 uses Salesforce's integrations — the Gmail and Outlook integrations and calendar sync (through Einstein Activity Capture or the classic integrations). REDA ships nothing here. REDA benefits from the connection because it logs Activities — tasks and events — on its records, and its scheduling features create calendar Events that the integration can surface in a user's mailbox and calendar.

REDA's calendar-backed features

REDA's bookings, property showings, and inspections create Salesforce Events — real calendar entries. A booking's status, for instance, syncs to the showing status on its linked calendar Event. So "calendar integration" for REDA really means one thing: making sure the Events REDA writes flow out to users' Google or Outlook calendars through Salesforce calendar sync. Turn calendar sync on, and an agent's bookings and showings appear on their external calendar automatically.

Inbound email intake — now available

REDA touchpoints vs Salesforce plumbing

Worked example: making REDA email reliable before go-live

Meridian Properties is preparing to launch. Here's the deliverability-and-calendar checklist:

To also turn on inbound email intake (auto-sync plus email-to-Inquiry and email-to-Service-Request), follow Email Services: Setup & Enablement.

Where to go next

1. Configuring Mass Email — the sender and send-flow configuration.
2. Background Jobs & Logs — where job-completion emails come from.
3. Customizing REDA Objects — extending REDA's objects safely.
4. Editions: OEM vs ISV — the email differences between editions.

Frequently asked questions