How to reduce the number of Salesforce calls/requests

Best Practices
1

The following are how the number of Salesforce calls/requests are made based on the Salesforce step that is being used:

  • Salesforce source step - 1 request to Salesforce.
  • Salesforce Lookup mapper step - x number of requests based on the limit in the SOQL query or Limit field.
  • Salesforce destination step - x number of requests based on the number of records that are integrating.
  • Salesforce Bulk destination step - x number of requests based on the number of batches that are being sent to Salesforce.

To reduce the number of Salesforce requests which are coming from the Salesforce Lookup mapper step, there are 2 options which are the following:

  1. Create a new flow where you use Salesforce as a source step (it’s 1 request from Salesforce since it will be a batch) and reference that flow as a Sync Flow destination step in the flows where the Salesforce Lookup mapper step is. This allows the data to come from Salesforce and go through the main/parent flow and the records can be filtered by using the Condition field in the Sync Flow destination step or a Filter mapper step or a Calculator mapper step.

The link below provides guidance on how to use the Sync Flow destination step:

Synchronous Flow Destination Step

OR

  1. Create a new flow where you use Salesforce as a source step and send the data to a Buffer destination step. Replace the Salesforce Lookup mapper steps with a Buffer Lookup mapper step to do a lookup for the record. This will require you to add a Schedule trigger and it can be set depending how often you require the Salesforce lookup data to be updated eg. weekly or daily.

The below link provides guidance on how the Buffer Lookup mapper step works:

Buffer Lookup Mapper step

The link below provides assistance on how to use the Schedule trigger step:

Schedule Trigger Step