Salesforce Alerts Integration
Use the Salesforce Alerts integration to connect a Salesforce org to OpenLM Cloud Broker. After you connect Salesforce, Cloud Broker collects usage signals so OpenLM Platform can monitor licensed seats, raise alerts on critical events, and feed downstream services such as Subscription Optimizer.
After you complete this guide, OpenLM Platform authenticates to your Salesforce org through a Connected App, the connection succeeds in Cloud Broker, and Salesforce data is available to OpenLM Alerts and reporting.
Before you begin
Confirm these prerequisites:
- Salesforce Alerts Integration is activated in OpenLM Products.
- Cloud Broker is active in OpenLM Platform. The integration authenticates and retrieves Salesforce data through Cloud Broker.
- You can sign in to Salesforce as an administrator.
- You can sign in to OpenLM Platform as an administrator.
To open the integration, select Navigation (the grid icon in the OpenLM Platform header), then Integrations, then Salesforce Alerts Integration.
For related tasks, see Cloud Broker, OpenLM Alerts, and Subscription Optimizer.
How the integration works
OpenLM Platform uses a Salesforce Connected App with OAuth and the username-password flow to authenticate. You register the connected app in Salesforce, copy the Consumer Key and Consumer Secret, and provide them, together with the Salesforce username and password, in OpenLM Cloud Broker. Cloud Broker uses those credentials to retrieve data and surface it to OpenLM Alerts and downstream services.
Components you need
You need these components to connect Salesforce to OpenLM Platform:
- An OpenLM Platform account with Cloud Broker active and Salesforce Alerts Integration activated.
- A Salesforce org where you can create and manage Connected Apps. Use a sandbox for first-time setup.
- Salesforce administrator access to turn on the OpenID Connect settings, create the Connected App, and adjust its access policies.
The integration expects the Salesforce login host https://login.salesforce.com. Sandboxes that use https://test.salesforce.com need additional configuration. Confirm the target host with OpenLM Support before you connect a sandbox.
Configure the integration
Complete the tasks in this section in order. The Salesforce side comes first because OpenLM needs the Connected App credentials.
Turn on the OpenID Connect settings in Salesforce
To turn on the OpenID Connect settings in Salesforce:
- In Salesforce, open Setup, then select Identity, then OAuth and OpenID Connect Settings.
- Turn on Allow OAuth Username-Password Flows.
- Turn on Allow OAuth User-Agent Flows.
- Save your changes.
Create a Connected App
To create a Connected App:
- In Salesforce Setup, open Apps, then App Manager.
- Select New Connected App.
- Complete the basic information:
- Connected App Name: a descriptive name, for example
OpenLM Cloud Broker. - API Name: Salesforce fills this from the Connected App Name. Keep it or adjust it as needed.
- Contact Email: an administrator email address.
- Connected App Name: a descriptive name, for example
- In the API (Enable OAuth Settings) section:
- Select Enable OAuth Settings.
- Set Callback URL to
http://localhost. Salesforce accepts thehttpscheme for this flow. - Add OAuth scopes. Select all available scopes except Issue JSON Web Token (JWT) based access tokens.
- Save the Connected App.
After Salesforce provisions the Connected App, the Consumer Key and Consumer Secret are available on the Manage Connected Apps page. You copy these values into OpenLM in a later step.
Adjust access policies
Salesforce blocks OAuth flows by default until you adjust access policies on the Connected App. To adjust them:
- Open Setup, then Apps, then Manage Connected Apps.
- Select your Connected App.
- Set Permitted Users to All users may self-authorize.
- Set IP Relaxation to Relax IP restrictions.
- Save.
All users may self-authorize is the simplest setting for proof of concept. For production, scope the Connected App to a specific permission set or profile and review the IP relaxation setting with your security team.
Activate Salesforce Alerts Integration in OpenLM Platform
To activate Salesforce Alerts Integration in OpenLM Platform:
- Sign in to OpenLM Platform.
- From the Navigation menu, open Products.
- Find the Salesforce Alerts Integration card.
- Select Activate.
Connect Salesforce in Cloud Broker
To connect Salesforce in Cloud Broker:
- From the Navigation menu, open Cloud Broker.
- Select Salesforce from the list of supported services.
- If Active is not selected, select it.
- Enter the credentials you gathered earlier:
| Field | What to enter |
|---|---|
| Consumer Key | The Consumer Key from your Salesforce Connected App. |
| Consumer Secret | The Consumer Secret from your Salesforce Connected App. |
| Username | The Salesforce username Cloud Broker authenticates as. |
| Password | The password for that Salesforce user. |
- Save the configuration.
Run the first Salesforce sync
To run the first Salesforce sync:
- In Cloud Broker, open Commands.
- Run the Salesforce sync command.
- Confirm that the command shows a success state.
If the command fails, see Troubleshooting.
Verify the integration
After the first sync succeeds, verify that data flows into OpenLM Platform.
- In Cloud Broker, confirm that the last successful sync timestamp updates.
- In OpenLM Alerts, define an alert rule that targets Salesforce data and confirm that the rule triggers when its conditions are met.
- In your reporting tool of choice, confirm that Salesforce-sourced rows appear.
Troubleshooting
The following table lists symptoms, their likely causes, and the fixes:
| Symptom | Likely cause | Fix |
|---|---|---|
| Cloud Broker reports an authentication failure. | The Consumer Key, Consumer Secret, username, or password is incorrect, or the Connected App is not active. | Verify all four fields character-by-character. Confirm the Connected App is saved and access policies are set. |
| Cloud Broker connects but returns no data. | The Salesforce user has no access to the relevant objects. | Assign the appropriate Salesforce profile or permission set to the user. |
| The Connected App rejects the request with an IP block. | IP Relaxation is set to Enforce IP restrictions. | Set IP Relaxation to Relax IP restrictions on the Connected App. |
| The Connected App rejects the request with a self-authorization error. | Permitted Users is set to Admin approved users are pre-authorized and the user is not pre-authorized. | Set Permitted Users to All users may self-authorize, or pre-authorize the relevant profile. |
| The Salesforce user is in a sandbox and the connection fails. | The integration assumes login.salesforce.com. | Contact OpenLM Support to confirm the target host before connecting a sandbox. |
Known limitations
Keep these limitations in mind:
- The integration assumes the production Salesforce login host. Sandbox support requires confirmation from OpenLM Support.
- The Cloud Broker UI lists fields as Client ID and Client Secret in some places. These correspond to Consumer Key and Consumer Secret in Salesforce. Treat the names as synonyms.
- The Password field in Cloud Broker is not masked when you enter the password. Avoid sharing the screen during configuration.
Related
For more information, see these pages:
The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.