You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat(salesforce): add Tooling API schema tools (custom field/object) + metadata query
Add salesforce_create_custom_field, salesforce_update_custom_field,
salesforce_delete_custom_field, salesforce_create_custom_object, and
salesforce_tooling_query so the connector can make schema/metadata changes
(e.g. create a custom field on Account). Previously the integration only did
record CRUD via the REST Data API. Existing `api` OAuth scope covers the
Tooling API; metadata creation is profile-permission gated, so no scope change.
Also: fix Opportunity closeDate being wrongly required on update_opportunity,
make list_reports/list_dashboards descriptions honest (recently-viewed scope),
and document run_report's includeDetails default.
* improvement(salesforce): non-destructive custom field update + align metadata param types
- update_custom_field now does a read-modify-write (GET existing Metadata,
overlay only provided changes, PATCH) so omitted properties are preserved
instead of being reset by the Tooling API's full-metadata PATCH; no more
fabricated label or injected create-time defaults on update
- fieldType is now optional on update (kept from the existing field unless changed)
- widen length/precision/scale/visibleLines param types to number | string to
match the tool param configs (type: number)
* improvement(salesforce): preserve picklist values and clear stale metadata on field type change
- custom field update now unions provided picklist values with the field's
existing values instead of replacing the whole valueSet (no data loss)
- when fieldType changes on update, drop the prior type's type-specific
metadata (length/precision/scale/visibleLines/valueSet/defaultValue/unique/
externalId) and backfill the new type's required defaults
* improvement(salesforce): scope custom field update to attributes, never the type
update_custom_field no longer changes a field's data type: Salesforce treats a
type change as a separate conversion operation, and a stale forwarded fieldType
could otherwise trigger an unintended destructive migration. The merge keeps the
field's existing type and overlays only the other provided properties, dropping
the type-change/stale-metadata-stripping logic entirely.
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/integrations/salesforce.mdx
+147-3Lines changed: 147 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ The Salesforce tool is ideal for workflows where your agents need to streamline
27
27
28
28
## Usage Instructions
29
29
30
-
Integrate Salesforce into your workflow. Manage accounts, contacts, leads, opportunities, cases, and tasks with powerful automation capabilities.
30
+
Integrate Salesforce into your workflow. Manage accounts, contacts, leads, opportunities, cases, and tasks, run reports and SOQL queries, and manage org schema by creating custom fields and objects via the Tooling API.
31
31
32
32
33
33
@@ -717,7 +717,7 @@ Delete a task
717
717
718
718
### `salesforce_list_reports`
719
719
720
-
Get a list of reports accessible by the current user
720
+
Get a list of up to 200 recently viewed reports for the current user
721
721
722
722
#### Input
723
723
@@ -814,7 +814,7 @@ Get a list of available report types
814
814
815
815
### `salesforce_list_dashboards`
816
816
817
-
Get a list of dashboards accessible by the current user
817
+
Get a list of recently used dashboards for the current user
818
818
819
819
#### Input
820
820
@@ -1029,6 +1029,150 @@ Get a list of all available Salesforce objects
1029
1029
| ↳ `totalReturned`| number | Number of objects returned |
0 commit comments