Triagic + Salesforce: ticket investigations over your business systems, read-only
Query accounts, contacts, cases and any other object with SOQL, search across records, and describe object schemas. Record, metadata and Apex writes aren't exposed. Triagic connects to Salesforce from the desktop app on each member's machine, with a credential you configure, and shows every call it makes while it investigates a ticket. Nothing is copied out of Salesforce.
What you can ask
- Pull the Salesforce record for this customer and summarise the last three interactions
- In Salesforce, has anyone else reported this since Monday?
- Which Salesforce tickets from this account are still open, and who owns them?
- Does Salesforce show a refund or a failed payment for order 8812?
- What did the customer say in the Salesforce thread before this ticket was filed?
What the agent can do
These are the 5 tools Triagic exposes from the Salesforce MCP server. Anything else the server lists is dropped at connect time.
- salesforce_search_objects
- salesforce_describe_object
- salesforce_query_records
- salesforce_aggregate_query
- salesforce_search_all
Connect in three steps
- 1
Mint a read-only credential in Salesforce
Create a dedicated user or token that can only read. An allowlist of SOQL query, SOSL search and describe tools, none of which can write, and the run-as user's profile bounds which records they see.
- 2
Add it in the Triagic portal
Integrations, then Add shared data source, then Salesforce.
- Instance URL: The org's My Domain URL, from Setup → My Domain. Client credentials only works against this URL, not login.salesforce.com.
- Consumer key: From an External Client App (or Connected App) with OAuth on and the Client Credentials Flow enabled. Setup → External Client App Manager → your app → Settings → OAuth Settings → Consumer Key and Secret.
- Consumer secret: From the same place. The token acts as the app's “Run As” user, so give that user a read-only profile or permission set with API Enabled.
- Username: An integration user with API Enabled and read access to the objects you need. Don't use an admin's login.
- Password
- 3
Let a desktop pick it up
Saving validates the shape of what you typed. The first desktop app to sync starts Salesforce locally and reports running or degraded with the error text.
Field-by-field setup, TLS options and the error table: Salesforce in the docs.
Read-only, by construction
An allowlist of SOQL query, SOSL search and describe tools, none of which can write, and the run-as user's profile bounds which records they see.
FAQ
- Can Triagic change anything in Salesforce?
- No. An allowlist of SOQL query, SOSL search and describe tools, none of which can write, and the run-as user's profile bounds which records they see. Give it a read-only credential as well, so the guarantee does not rest on one layer.
- What do I need to connect Salesforce?
- Instance URL, Consumer key, Consumer secret, Username, Password. The desktop app on a member's machine starts the connection; the portal never holds a live process.
- Does Salesforce cost extra?
- No. Every connector is included in the seat price. Start a 14-day trial without a card.
Related integrations
- AtlassianConfluence pages and Jira issues, read-only. Fill in at least one product.
- StripeLook up customers, invoices, subscriptions, and disputes, read-only.
- SlackSearch channels and threads for context on an incident. Posting is off unless you turn it on.
- NotionSearch the workspace and read runbook and wiki pages behind an alert.
Try it on your own Salesforce
No card. Install the desktop app, connect Salesforce read-only, and triage a real ticket this afternoon.