Before configuring “Salesforce” action nodes, you will need to have at least one Salesforce integrations connected in your organization. You can refer to this Help Center article to learn more about Salesforce integrations.
Search Salesforce object records
The “Search Salesforce records” action node allows you to search for and retrieve a specific Salesforce record based on defined criteria. It is essential for workflows that require existing customer data to determine the next action.
To update a specific Salesforce record accurately, you will need to provide the relevant record ID. The “Search Salesforce records” action allows you to retrieve the correct record by searching Salesforce based on defined criteria. Once the matching record is found, its ID can be used in the “Update Salesforce record” action node to ensure seamless and precise data updates between platforms.
To set up the node, follow these steps:
- Click on the “Search Salesforce records” action node to open up its form, which will appear on the right side of the screen
- The node form contains the following fields for you to configure your action:
- Organization: Select the connected Salesforce organization. If you haven’t set up your Salesforce integration, refer to this Help Center article to learn more about Salesforce integrations.
- Object type: Choose Contact, organization, Deal, Ticket, or a Custom object.
-
Set search conditions
- Property: Select the Salesforce property to match (e.g., email, phone, hs_object_id, domain, dealname, custom fields).
- Operator: Choose the comparison (e.g., equals, contains, starts with, greater than, less than).
-
Value: Enter a static value or insert a variable (trigger, contact, or mid‑flow) using the picker. For example:
-
Find contact by email: Property: email → Operator: equals → Value: {Contact: email}
-
Find contact by email: Property: email → Operator: equals → Value: {Contact: email}
-
Handle error: Toggle this on to set up a fallback path whenever a search request fails. When enabled:
- An additional branch will appear in the flow, specifically for failed requests
- You can configure this branch to define what should happen when the request cannot be completed, for example, create a new contact
