Skip to content
SendPulse logoSalesforce logo

Connect SendPulse to Salesforce

Move data between SendPulse and Salesforce the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

SendPulse triggers
3
SendPulse actions
6
Salesforce triggers
9
Salesforce actions
27

Automation ideas

What you can build with SendPulse and Salesforce

A few flows teams run between SendPulse and Salesforce. Use one as a starting point, or build your own from scratch.

  • New Subscriber in SendPulse creates Add Contact to Campaign in Salesforce

    Fires when new subscriber is added

  • New Case Attachment in Salesforce creates Add Subscriber in SendPulse

    Fires when a new Attachment or File is added to any Case record.

  • New Subscriber in SendPulse creates Add File to Record in Salesforce

    Fires when new subscriber is added

  • New Case Attachment in Salesforce creates Change Variable for Subscriber in SendPulse

    Fires when a new Attachment or File is added to any Case record.

  • New Subscriber in SendPulse creates Add Lead to Campaign in Salesforce

    Fires when new subscriber is added

  • New Case Attachment in Salesforce creates Delete Contact in SendPulse

    Fires when a new Attachment or File is added to any Case record.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in SendPulse and acts in Salesforce, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.