Skip to main content

​
Overview

The Salesforce integration enables your agents to query, create, update, and manage records across your entire Salesforce CRM. Works with all standard objects (Accounts, Contacts, Opportunities, etc.) and any custom objects in your org — no Connected App or admin setup required.

​
Features

  • SOQL Queries: Run any SOQL query with automatic pagination
  • Full CRUD: Create, read, update, upsert, and delete records on any object
  • Custom Object Support: Works with custom objects and custom fields (__c suffix) out of the box
  • Schema Discovery: Agents can discover available objects and fields at runtime, including picklist values and relationships
  • Upsert by External ID: Match and update records using external ID fields for integration workflows
  • Secure Authentication: SOAP login with session caching and automatic re-authentication on expiry

​
Prerequisites

  • Active Salesforce account (any edition)
  • Username and password for the account
  • Security token for the account (reset via Salesforce Settings)
  • Appropriate permissions on the objects your agent needs to access

​
Setup Guide

1

Get Your Security Token

In Salesforce, go to your avatar (top right) > Settings > Reset My Security Token. Salesforce will email a new token to the email on your account. If you don’t see this option, your org may have IP restrictions configured — contact your Salesforce admin.
2

Enable Salesforce Integration

In Aster Agents, navigate to Control Hub > Integrations and locate the Salesforce card. Click Connect to begin setup.
3

Configure Connection

Provide your Salesforce connection details:
  • Login URL: https://login.salesforce.com for production, or https://test.salesforce.com for sandbox orgs
  • Username: Your Salesforce username (email address)
  • Password: Your Salesforce account password
  • Security Token: The token emailed to you in Step 1
4

Add Tools to Your Agent

Edit your agent and enable the Salesforce tools you need:
  • Salesforce Query — run SOQL queries
  • Salesforce Manage Records — create, read, update, and delete records
  • Salesforce Get Schema — discover objects and field definitions
We recommend enabling all three — the agent uses Get Schema to learn your org’s field names before querying or writing data.

​
Available Tools

​
Salesforce Query

Execute SOQL queries against your Salesforce org. Results are automatically paginated for large result sets. 
SELECT Id, Name, Industry, AnnualRevenue 
FROM Account 
WHERE Industry = 'Technology' 
ORDER BY AnnualRevenue DESC 
LIMIT 10

​
Salesforce Manage Records

Perform CRUD operations on any standard or custom object:
  • get — retrieve a record by ID
  • create — create a new record with field values
  • update — update specific fields on an existing record
  • upsert — insert or update based on an external ID field
  • delete — delete a record by ID

​
Salesforce Get Schema

Discover your org’s data model at runtime:
  • Call without parameters to list all available objects
  • Call with an object name to get detailed field information including types, picklist values, required flags, and relationship targets
This is especially useful for orgs with custom objects and fields — the agent learns your schema before making queries.

​
Security Considerations

  • Use a dedicated service account rather than a personal account for production use
  • Apply profile and permission set restrictions on the Salesforce user to limit which objects and fields the agent can access
  • Enable field-level security in Salesforce to control access to sensitive fields
  • Monitor login history in Salesforce Setup to track agent activity
  • Rotate your security token periodically by resetting it in Salesforce Settings
  • Use sandbox orgs (https://test.salesforce.com) for testing before connecting production

​
Troubleshooting

  • Verify your username, password, and security token are correct
  • Ensure your account is not locked — check your email for lockout notifications
  • If you recently changed your password, you must reset your security token as well (it changes with every password reset)
  • Confirm you’re using the correct Login URL (production vs. sandbox)
  • The Salesforce user’s profile and permission sets control what objects and fields are accessible
  • Ask your Salesforce admin to verify the user has read/write access to the required objects
  • Check field-level security if specific fields are missing from query results
  • Custom object API names always end with __c (e.g., Invoice__c)
  • Use the Salesforce Get Schema tool to list all available objects and find the correct API name
  • Managed package objects use a namespace prefix (e.g., AIM__Deal__c)
  • Security tokens are invalidated whenever you change your password — reset the token after any password change
  • If your org uses IP restrictions and your IP is whitelisted, the security token may not be required — try leaving it blank
  • Check that you’re copying the full token from the email (no extra spaces)