Salesforce
CRM account, lead, and pipeline tracking.
What it does
Reads and writes Salesforce records. For larger clients, this is often where the truth about a customer lives.
What you need
An account with Salesforce that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to Salesforce's own sign-in and consent screen, and what comes back is an authorisation rather than a password. RAiN never sees your password, and the authorisation is held by our integration provider on our instructions — see the Integrations & Connected Accounts notice for what that means.
Connecting it
Connections belong to one project. A system built for one client never acts on another client's account, and a package handed to a business runs on theirs — so the same integration is connected again, separately, for each project that needs it.
- Open the project and stay on the Visual Editor tab.
- Open the Tools & Integrations rail on the right.
- Find Salesforce and press Connect.
- Authorise in the window that opens, then come back. The rail will show it as connected.
The consent link is good for about twenty minutes. If you leave it and come back tomorrow, press Connect again rather than reusing the old tab.
To stop it, press Disconnect. That ends this project's access immediately. You can also revoke it from Salesforce's own security settings, which works even if you never open RAiN again.
What an agent can do with it
38 actions are available once connected, 7 of which delete things and are marked where they appear. They appear in the tool list for this project only — a project that has not connected Salesforce is never offered them.
| Action | What it does |
|---|---|
salesforce_create_s_object_record |
Create SObject record |
salesforce_create_account |
Create account |
salesforce_create_campaign |
Create campaign |
salesforce_create_contact |
Create contact |
salesforce_create_custom_field |
Create custom field |
salesforce_create_custom_object |
Create custom object |
salesforce_create_lead |
Create lead |
salesforce_create_opportunity |
Create opportunity |
salesforce_post_composite_sobjects |
Create records using sObject Collections |
salesforce_delete_account |
Delete account ⚠️ deletes things |
salesforce_delete_campaign |
Delete campaign ⚠️ deletes things |
salesforce_delete_contact |
Delete contact ⚠️ deletes things |
salesforce_delete_file |
Delete file ⚠️ deletes things |
salesforce_delete_lead |
Delete lead ⚠️ deletes things |
| … | and 24 more, all listed in the rail |
Tick the ones an agent may use, or choose one in an Action step to run it exactly as written with no model involved.
A worked example
An agent enriches every new lead with company information before a salesperson sees it, so the first call is informed rather than exploratory.
When it goes wrong
Field names are API names, not labels. Custom_Field__c, not 'Custom Field'.
See also
- Integrations & Connected Accounts — who holds the authorisation
- Action steps — running one action exactly as written
- Sequences — how steps fit together

