Skip to content
Communications ⇄ CRM

Amazon SES to Salesforce integration — real-time, two-way sync

Keep Amazon SES and Salesforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Amazon SES and Salesforce

Keep Salesforce and Amazon SES working from the same contacts, and log every call, message, and meeting back on the record, in real time and in both directions.

Salesforce holds the people the business talks to: the contacts, their phone numbers and email addresses, and which rep owns the relationship. Amazon SES is where the talking happens, whether that is calls, texts, email, or meetings. The two depend on the same people, and when the contact list in one drifts from the other, outreach goes to stale numbers and the record of what was said never makes it back to the account.

Stacksync syncs Accounts, Contacts, Leads, Opportunities in Salesforce with Contact Lists, Email Templates, Suppression List, Verified Identities in Amazon SES field by field, in real time, and in both directions. Current contact details flow out to Amazon SES so it can reach the right person, and the calls, messages, and meetings Amazon SES produces flow back onto the matching record in Salesforce. You decide which system owns which fields, and conflicts resolve by rules you set.

Common use cases

  • 01 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.
  • 02 Sync Accounts, Contacts, and Opportunities bi-directionally with Postgres so engineering teams read and write CRM data with plain SQL.
  • 03 Stream SES sending events (delivery, bounce, complaint, open, click) from a configuration-set event destination into a warehouse for deliverability reporting.
  • 04 Write bounced and complained addresses from the SES Suppression List back onto CRM and marketing records so other tools stop emailing them.

Common sync patterns

New contacts reachable right away

A contact created or updated in Salesforce appears in Amazon SES within seconds, so outreach starts without exporting a list or re-keying numbers.

Where Amazon SES reaches out: contacts kept current

Names, phone numbers, email addresses, and the owning rep from Salesforce stay current in Amazon SES, so every call, text, or email goes to the right person at the right address.

Calls, messages, and meetings on the record

Activity handled in Amazon SES appears on the matching contact and account in Salesforce, so the next person sees the full history without leaving the CRM.

What you can sync between Amazon SES and Salesforce

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Amazon SES objects Salesforce objects How this pairing syncs
Contacts Subscribers in the contact list with per-topic opt-in state; CRUD via CreateContact/ListContacts/UpdateContact/DeleteContact, each carrying a LastUpdatedTimestamp for polling. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Email Templates Reusable subject/HTML/text templates with replacement variables; synced via CreateEmailTemplate, GetEmailTemplate, ListEmailTemplates, and UpdateEmailTemplate. Cases Support records; synced with help desk tools or internal databases for escalation workflows. Email Templates is specific to Amazon SES and Cases to Salesforce — each maps to any object or custom field on the other side.
Suppression List Addresses auto-added on bounce or complaint; read with ListSuppressedDestinations and written with Put/DeleteSuppressedDestination to control re-sends. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Suppression List is specific to Amazon SES and Campaigns to Salesforce — each maps to any object or custom field on the other side.
Verified Identities Email-address and domain identities cleared to send; managed via CreateEmailIdentity, ListEmailIdentities, GetEmailIdentity (DKIM and verification status). Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Verified Identities is specific to Amazon SES and Tasks and Events to Salesforce — each maps to any object or custom field on the other side.
Configuration Sets Named send-time rule groups that attach event destinations, IP pools, and suppression options; managed via Create/List ConfigurationSet operations. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Configuration Sets is specific to Amazon SES and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.
Sending Events Per-message send, delivery, bounce, complaint, open, and click events; not on any API, read from a configuration-set event destination (SNS/EventBridge/Firehose). Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. Sending Events is specific to Amazon SES and Custom Objects to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Amazon SES and Salesforce

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Amazon SES Salesforce Sub-second propagation

DetectionAmazon SES notifies Stacksync of record changes through webhook events. Message events (delivery, bounce, complaint, open, click) are pushed in near real time through configuration-set event destinations.

DeliveryEach detected change is written to Salesforce through its API, with automatic retries and rate-limit backoff.

Salesforce Amazon SES Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

DeliveryEach detected change is written to Amazon SES through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Amazon SES: Every SES API action except SendEmail, SendRawEmail, and SendTemplatedEmail is throttled to 1 request/second per Region; the send rate and 24-hour sending quota are account-specific, adjustable, and per Region.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Amazon SES ⇄ Salesforce

Connect Amazon SES and Salesforce for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Amazon SES–Salesforce connection.

Real-time

Two-way sync

Changes in Amazon SES or Salesforce instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Amazon SES or Salesforce data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Amazon SES or Salesforce record.

Observability

Monitoring

Track your Amazon SES ⇄ Salesforce sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Amazon SES and Salesforce.

How the Amazon SES and Salesforce connectors work

Amazon SES

Integration surface
AWS SES API v2 (REST/JSON over HTTPS) plus an SMTP sending interface
Authentication
AWS IAM credentials (access key + secret) signed with Signature Version 4, or an assumed IAM role via STS; the SMTP interface uses SMTP credentials derived from an IAM user
Change detection
Message events (delivery, bounce, complaint, open, click) are pushed in near real time through configuration-set event destinations (SNS/EventBridge/Firehose); contacts, templates, and suppression entries are polled via List/Get operations
Capabilities
read · write · webhooks
Rate limits
Every SES API action except SendEmail, SendRawEmail, and SendTemplatedEmail is throttled to 1 request/second per Region; the send rate and 24-hour sending quota are account-specific, adjustable, and per Region

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

How to connect Amazon SES to Salesforce — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Amazon SES and Salesforce with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Amazon SES connected
    Salesforce connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Amazon SES and Salesforce objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Amazon SES ⇄ Salesforce
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Amazon SES Salesforce
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Amazon SES and Salesforce integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 441 integrations available for Amazon SES and Salesforce.

Popular · 7 of 441
All Amazon SES integrations All Salesforce integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own