This document explains the Salesforce Reader node, which lets you pull data from Salesforce objects for use in your automations.

​
Node Inputs

​
Required Fields

  • Object: Choose which Salesforce object to read (e.g., Account, Lead, Contact, Opportunity)
  • Fields: Select which fields to retrieve from the chosen object
    • Important: When using filtered List Views, make sure to include any fields used in the filter criteria

​
Optional Fields

  • List View: Filter records using predefined Salesforce views
    • Select “All Views” to read from the entire object
    • The node will respect any filters set in your Salesforce views

​
Node Output

Each selected field becomes an output list that you can connect to other nodes.

​
Node Functionality

The Salesforce Reader node connects to your Salesforce instance and:

  • Retrieves data from any standard or custom object
  • Pulls complete datasets without record limits
  • Uses your predefined list views for filtering
  • Supports Loop Mode for processing multiple list views or objects
  • Maintains secure authentication through Gumloop

​
Common Salesforce Field Issues and Workarounds

​
Why Some Fields May Appear Empty or Missing

When using the Salesforce Reader, you may sometimes find certain fields are unavailable or return as None even though they appear in Salesforce. Here’s why this happens and how to fix it:

​
1. List View Query Limitations

List Views in Salesforce only fetch specific fields in their underlying queries:

  • Only fields included in the List View’s actual SOQL query are available
  • Fields used only for filtering but not displayed may not be retrievable
  • Fields may appear in the Salesforce UI but aren’t directly accessible via the API query

Workaround: Create a custom List View in Salesforce that explicitly includes all the fields you need.

​
2. ID Fields vs. Display Values

You’ll often see ID fields (like AccountId) instead of their display values (like the Account Name):

  • Salesforce returns relationship fields as IDs (e.g., AccountId: 001xx000003DGb2AAG)
  • Users typically expect to see the display value (e.g., “Acme Corporation”)

Workaround: Create formula fields in Salesforce that directly reference the display value:

Custom Field: Account_Name_Formula__c
Formula: Account.Name

​
3. Permission Issues

Some fields may be inaccessible due to permission settings:

  • Fields the connected user doesn’t have read access to
  • Fields restricted by field-level security
  • Object permissions that limit access

Workaround: Check field-level permissions for the connected user and adjust as needed.

​
4. Polymorphic Relationship Fields

Certain fields like WhatId in Task objects can reference different object types:

  • These fields are particularly challenging because they could point to various object types
  • The display value isn’t consistently accessible

Workaround: Create formula fields for each potential object type the field could reference.

​
Best Practice Workarounds Summary

  1. Create Formula Fields:

    • Add custom formula fields that directly reference related data
    • Example: Account_Name_Text__c formula field with value Account.Name
    • These formula fields will be consistently available to the Salesforce Reader

  2. Customize List Views:

    • Create specific List Views that include all fields you need
    • Add any fields used in filters to the displayed columns
    • Save these views with descriptive names for your automation

  3. Use Text Formula Fields:

    • For lookups and relationships, create text formula fields
    • These are more reliable than trying to access the relationship directly
    • Example: For a Contact’s Account Name, create Account_Name__c as a formula field

  4. Check Field Accessibility:

    • Ensure the connected Salesforce user has access to all required fields
    • Review field-level security settings if fields are consistently missing

​
Example Workflows

​
1. Lead Enrichment Pipeline

Salesforce Reader → Enrich Contact Information → Salesforce Updater
Salesforce Configuration:
- Object: Lead
- Fields: Email, Company, Name, Title
- List View: "New Leads This Week"
Next Steps:
- Enrich contact details
- Update Salesforce records with new information

​
2. Account Analysis with AI

Salesforce Reader → Ask AI → Slack Message Sender
Salesforce Configuration:
- Object: Account
- Fields: Description, Industry, Annual Revenue, Customer Health Score
- List View: "Strategic Accounts"
Next Steps:
- Analyze account health with Ask AI or Categorizer node
- Send insights to the selected Slack channel

​
3. Automated Customer Communication

Salesforce Reader → Ask AI → SendGrid Email Sender
Salesforce Configuration:
- Object: Contact
- Fields: Name, Email, Last Purchase Date, Account Name
- List View: "Active Customers"
Next Steps:
- Generate email content via AI
- Send personalized email campaigns through SendGrid

​
4. Support Queue Management

Salesforce Reader → AI List Sorter → Slack Message Sender
Salesforce Configuration:
- Object: Case
- Fields: Subject, Priority, Status, Account Name
- List View: "Open Cases"
Next Steps:
- Sort cases by priority and impact using AI list sorter
- Alert support team in Slack

​
Important Notes

​
Authentication Setup

  1. Configure your Salesforce credentials in Gumloop Credentials
  2. Ensure proper Salesforce permissions for the chosen objects and list views

In summary, the Salesforce Reader node provides flexible data extraction from Salesforce objects, supporting filtered views and customizable field selection for efficient data retrieval. With the right setup and workarounds for common field issues, you can ensure consistent and reliable data access from your Salesforce instance.