Skip to content
Respond.io logoSalesforce logo

Connect Respond.io to Salesforce

Move data between Respond.io 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.

Respond.io triggers
7
Respond.io actions
9
Salesforce triggers
9
Salesforce actions
27

Automation ideas

What you can build with Respond.io and Salesforce

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

  • Contact Tag Updated in Respond.io creates Add Contact to Campaign in Salesforce

    Triggers when a tag is added or removed from a contact in Respond.io.

  • New Case Attachment in Salesforce creates Add Comment to Conversation in Respond.io

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

  • Contact Tag Updated in Respond.io creates Add File to Record in Salesforce

    Triggers when a tag is added or removed from a contact in Respond.io.

  • New Case Attachment in Salesforce creates Add Tag to Contact in Respond.io

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

  • Contact Tag Updated in Respond.io creates Add Lead to Campaign in Salesforce

    Triggers when a tag is added or removed from a contact in Respond.io.

  • New Case Attachment in Salesforce creates Assign or Unassign Conversation in Respond.io

    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 Respond.io 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.