All apps & connectors
OrgPulse logo

OrgPulse

ChatGPTby CloudCounsel Limited

OrgPulse monitors a Salesforce org for the things that expire or run out and break logins and integrations, and answers questions about them in ChatGPT. It saves Salesforce admins the routine work of checking an org by hand: daily checks, alerts before something breaks, and plain answers about who can see what. Its tools only read from Salesforce. They never create, change or delete anything in your org. What it does Expiring items. Lists what is about to expire and could break a login or an integration: certificates (including SAML and credential certificates), user passwords, time-limited permission set assignments, licences, trial expiry, scheduled jobs, refresh tokens (estimated from the connected app's policy) and retiring API versions your org still uses. If OrgPulse cannot read one of these because the integration user lacks a permission, it says so and names the permission, instead of reporting an empty list. Limits and storage. Reports API limits, data and file storage, licence counts and async queue depth, so you can see how close you are to a limit. Access explanations. Pick a user and a field, an object or a record (by its Salesforce ID), and OrgPulse shows the full access path, including which profile, permission set, group or sharing rule grants each piece. When access is denied it names the one change that would grant it. You can also compare two users on the same field. Alerts. A daily check of each org can send email or Slack alerts when an item nears a threshold you set and again when it clears, without repeats. Watches are configured in OrgPulse, never in Salesforce. History. OrgPulse keeps the latest check, a daily summary and every change (new, moved, resolved or expired items and limit changes), so it can say what is new since the last check. Coverage depends on the integration user's licence. Anything OrgPulse cannot read is listed under "Not checked". How it connects An org admin signs in to OrgPulse and proves they own the org through Salesforce's standard OAuth login. They then choose who the checks run as: a dedicated read-only integration user with a limited permission set that OrgPulse provides (recommended), or, for a quick trial, the admin themselves. ChatGPT never receives Salesforce credentials; it holds only an OrgPulse access token. What it does not detect Tokens held by External Credentials, Auth Provider upstream secrets, security tokens, Salesforce-managed domain certificates, user licence contract dates, sandbox lifecycle, and the TLS certificates of remote endpoints. Refresh token expiry is an estimate. Access and data No tool writes to Salesforce. Outside ChatGPT, during setup and only if the admin asks, OrgPulse makes three changes scoped to its own access (listed on the connect page) using the admin's sign-in for that one request. Configuring a watch writes only OrgPulse's own settings, and replaces that watch's earlier settings. OrgPulse stores org identifiers, the integration username, check results and change history, and alert settings. It does not store customer record data. See the privacy policy for what is collected, why, who receives it, how long it is kept and how to delete it.

Details

Listed Oct 8, 2026
by CloudCounsel Limited
Version 1.0.0
Lifecycle
  1. First seenNov 17, 2026
    created Oct 8, 2026
  2. PublishedLive in ChatGPT
    last changed Nov 17, 2026
  3. Visible in app store•
  4. Featured•