Overview

The Salesforce (REST API) provides a powerful platform for creating and managing customer relationships with a wide array of features like data manipulation, querying, and complex automation. With Pipedream's serverless execution, you can create workflows that automate your sales processes, sync data with other platforms, enhance customer engagement, and trigger actions based on specific events. Dive into Salesforce data, streamline lead management, track customer interactions, and push or pull data to or from Salesforce seamlessly.

Getting Started

You can install the Pipedream Salesforce app in the Accounts section of your Pipedream account, or directly in a workflow.

Prerequisite: Salesforce Edition with API Access

In order to use this application, you must be on a Salesforce Edition that has API Access, and API Access must be enabled. See here for more details.

Salesforce Editions with API Access
* Enterprise Edition
* Unlimited Edition
* Developer Edition
* Performance Edition
* Professional Edition (API access available as an add-on)

$3

Your Salesforce user needs a System Administrator profile in order to enable API access. If you don't have this on your Salesforce Profile, ask your System Administrator to enable API Access for your user.

The most straightforward way to add these permissions is to create a new Permission Set in Salesforce, and to add it to the user once created.

Here is a step-by-step on how to do this:

Create New Permission Set

1. Navigate to your Salesforce instance, and click the Setup wheel in the top-right corner.
2. Under the Administration tab on the lefthand sidebar, click Users --> Permission Sets.
3. On the Permissions Set page, click New.
4. Create a new permission set, give it a label, API name, and description. Example:

Label: Pipedream API Access
API Name: Pipedream
Description: Adds a set of permissions required for Pipedream.

Add Permissions

5. Now that the permission set is created, navigate to System Permissions.

6. From System Permissions, click Edit.

7. Select the following permission, and click Save.
- API Enabled

If you'd like to utilize Pipedream's webhook triggers, you will need to add the following permissions to the permissions set as well:
- Apex REST Services
- Author Apex
- View Roles and Role Hierarchy
- Modify Metadata Through Metadata API Functions
- View Setup and Configuration

8. The list of added permissions (6) should look like this, and click save again.

Add Permission Set to User

9. From the newly created Permission Set, click Manage Assignments, then Add Assignment.

10. Select the user you'd like to assign this permission set to, and click Assign. The user should now show up under Current Assignments.

11. You should now be able to use the Salesforce integration along with the webhook triggers if you configured the required permissions above.

Example Use Cases

Synchronization between Salesforce and External Databases

Synchronize Salesforce with external databases to ensure data accuracy and consistency without manual effort.

Real-Time Customer Support Notifications

Improve customer service responsiveness by triggering real-time notifications to support teams when new tickets are created.

Lead Scoring and Engagement Automation

Streamline lead management by automatically scoring and engaging leads through personalized campaigns, enhancing conversion rates.

Dynamic Inventory Management

Keep inventory levels accurate and responsive to sales activity by updating Salesforce in real-time based on e-commerce data.

Troubleshooting

Unable to connect your account

If you're having issues connecting your Salesforce account on Pipedream, please ensure that IP Restrictions are not enabled for Pipedream. To learn more about what this means, please see the Salesforce documentation here.

To modify these settings:
1. Navigate to Salesforce Setup.
2. Under Apps, click Connected Apps, then Connected Apps OAuth Usage.

3. If Pipedream is not yet installed, click Install, otherwise click Manage App Policies.
4. Click Edit Policies.
5. Under OAuth Policies, you should see the setting IP Relaxation. Set this to Relax IP Restrictions.

Instant trigger is not working

If you happen to stumble on the error: UNKNOWN_EXCEPTION: admin operation already in progress when creating an Instant trigger, you can follow the steps below to use the Salesforce Flow Builder to be able to use webhooks with Pipedream. This is a known error in Salesforce.

1. Create a New Workflow on Pipedream and add a HTTP trigger.
2. Login and go to your Salesforce Setup Menu Page.
3. On the left hand Quick Find Bar, search for Outbound Messages in Process Automation -> Workflow Actions.
4. Click on the New Outbound Message button in the middle of the page.
5. Select the Object Type and click Next.
6. Fill in the Name, Unique Name, and Available Fields to Send fields in the form. On the Endpoint URL field, paste the URL endpoint generated by the HTTP trigger created earlier and then click Save.
7. Back to the left hand Quick Find Bar, search for Flows in Process Automation.
8. Click on New Flow button on the upper right hand corner and then select on Record-Trigged Flow and click on Create.
9. Select the same Object Type as before and select the appropriate flow trigger.
10. Optionally set Entry Conditions, keep Actions and Related Records selected, and click on Done.
11. Click on the plus sign below the newly created trigger and click on Action.
12. Search for Outbound Message and on the search bar select the trigger that was created previously.
13. Insert a Label and an API Name and then click on Done.
14. Save the flow by clicking on the Save button, insert a Flow Label and a Flow API Name and then click on Activate next to the Save button.
15. Back to the Pipedream Workflow, create a new step with the Salesforce Convert SOAP Object action.
16. In the XML Soap Object field, select the path from the trigger or type in {{steps.trigger.event.body}}.
17. That's it! You can now deploy the workflow and you will receive instant updates from Salesforce.

API Errors

Below is a list of potential HTTP response status codes with their corresponding causes:

$3

The request couldn't be understood, usually because the JSON or XML body contains an error.

$3

The session ID or OAuth token used has expired or is invalid. The response body contains the message and errorCode.

$3

The request has been refused. Check that the logged-in user has appropriate permissions. If the error code is REQUEST_LIMIT_EXCEEDED, the API request limits in your org have been exceeded.

$3

The requested resource couldn't be found. Check the URI for errors, and ensure there are no sharing issues.

$3

The method specified isn’t allowed for the resource indicated in the URI.

$3

The request couldn’t be completed due to a conflict with the current state of the resource. Ensure the API version is compatible with the resource requested.

$3

The requested resource has been retired or removed. Update or delete references to the resource.

$3

The request wasn't executed because it didn't meet one or more preconditions specified in the request headers.

$3

The length of the URI exceeds the 16,384-byte limit.

$3

The entity in the request is in a format that's not supported by the specified method.

$3

Salesforce Edge doesn’t have routing information for the request host. Contact Salesforce Customer Support.

$3

The request wasn’t executed because it wasn't conditional. Add a Conditional Request Header like If-Match to the request.

$3

The combined length of the URI and headers exceeds the 16,384-byte limit.

$3

An error within Lightning Platform has occurred, preventing request completion. Contact Salesforce Customer Support.

$3

Salesforce Edge couldn’t communicate successfully with the Salesforce instance.

$3

The server is currently unable to handle the request, typically due to maintenance or being overloaded.