Plexara
Salesforce
- Catalog
- Salesforce REST API v67.0
- Operations indexed
- 91
- Access
- Read and write
The catalog is organized into four sections. The assistant opens the section it needs, or searches all 91 operations by intent, then reads one operation's parameters before it calls. Operations that change data are labelled as writes, and a role can be limited to the read operations.
Endpoint surface
What the assistant can reach
| Area | Operations | Covers |
|---|---|---|
| Core: discovery, queries, and object metadata | 27 | Org limits, SOQL with paging, SOSL and parameterized search, object describe, layouts, list views, quick actions, and records created, updated, or deleted in a time window. |
| Records and composite | 16 | Single-record create, read, update, and delete, upsert and lookup by external id, relationship traversal, and composite, batch, tree, graph, and collection calls for many records per request. |
| Bulk and analytics | 28 | Bulk API 2.0 ingest and query jobs for large loads and extracts, report runs with filters, asynchronous report runs, and dashboard results and refresh. |
| Automation and UI API | 20 | Approval processes, workflow rules, invocable flows and Apex, standard actions, Tooling API queries, and UI API records, object info, and picklist values. |
Example questions
Questions an assistant can answer
- Which accounts were created or changed since yesterday?
- Which open opportunities close this quarter, by owner and stage?
- Which fields on Account are custom, and which are required?
- Run the weekly pipeline report and summarize what changed from last week.
- How much of the org's daily API allowance is left?
- Update the billing contact on these twelve accounts from the attached sheet.
What the agent calls. This is the exchange the agent has with Plexara on your behalf, shown for the technical reader. You ask in plain language; you never type any of it.
| Asked | API | First result |
|---|---|---|
| Which customer records changed since yesterday? | Salesforce, 91 operations | GET /services/data/v67.0/sobjects/{sobject}/updated |
Knowledge pages
The knowledge on this connection
Every Salesforce org is customized. A knowledge page attached to the connection records what yours means, so the assistant queries the right object and field the first time.
1
Your custom objects and the fields that matter
Which custom objects hold invoices or applications, and which account field carries the customer number used by the ERP. The page names them, so the assistant does not infer meaning from API names.
2
The integration user sets the boundary
Every call runs as one integration user. Object and field permissions are that user's. A field the assistant cannot see is outside that user's grant.
3
Query results page by path
A large SOQL result returns a path to the next page, not a cursor. The page tells the assistant to follow it until the result reports done.
4
The daily API allowance is shared
The org's allowance is shared with every other integration. The page tells the assistant to check remaining limits before a heavy extract and to prefer a bulk query job.
5
Writes change production records
Create, update, upsert, and delete act on the live org. The page states which roles hold them and which objects they may touch.
Combinations
Works with
CRM and ERP in agreement. Which customers changed in the CRM but not yet in the ERP?
The full index of APIs in production is on the API connections page.
Plexara is not affiliated with or endorsed by Salesforce. Salesforce is a trademark of its owner.
Next
API connections
The APIs already in service, and the questions that use more than one of them in a single session.