Skip to content
Checkout.com logoSalesforce logo

Connect Checkout.com to Salesforce

Move data between Checkout.com 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.

Checkout.com triggers
2
Checkout.com actions
7
Salesforce triggers
9
Salesforce actions
27

Automation ideas

What you can build with Checkout.com and Salesforce

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

  • Payment Events in Checkout.com creates Add Contact to Campaign in Salesforce

    Trigger order fulfillment when payment is approved.

  • New Case Attachment in Salesforce creates Create Customer in Checkout.com

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

  • Payment Events in Checkout.com creates Add File to Record in Salesforce

    Trigger order fulfillment when payment is approved.

  • New Case Attachment in Salesforce creates Update Customer in Checkout.com

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

  • Payment Events in Checkout.com creates Add Lead to Campaign in Salesforce

    Trigger order fulfillment when payment is approved.

  • New Case Attachment in Salesforce creates Create Payment Link in Checkout.com

    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 Checkout.com 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.