Salesforce

Connect a Salesforce organization by saving its Connected App credentials (Consumer Key/Secret + My Domain host) for the OAuth 2.0 Client Credentials Flow, after checking they actually work. You'll need a Connected App with Client Credentials Flow enabled and a 'Run As' integration user configured (Setup > App Manager > New Connected App).

List the connected Salesforce organizations.

Create a new record of any Salesforce sObject type -- standard (Account, Contact, Lead, Opportunity, Case, Task, Event, Campaign, User...) or custom (any __c object). The REST API is generic across every object, so this one tool covers all of them.

Read one record of any Salesforce sObject type by Id, optionally limited to specific fields.

Update selected fields on an existing record of any Salesforce sObject type. Only given fields change.

Create or update a record by matching an External ID field instead of the Salesforce record Id -- the standard way to sync from an external system without tracking Salesforce Ids yourself.

Permanently delete one record of any Salesforce sObject type by Id. Salesforce keeps it recoverable in the Recycle Bin for 15 days.

Read the field-level metadata (schema) of a Salesforce sObject type -- every field's API name, label, type, and whether it's required/updateable/a picklist. Use this to discover what fields exist on a standard or custom object.

List every sObject type available in this org -- standard objects and custom (__c) objects alike.

Run a SOQL query against Salesforce records, e.g. "SELECT Id, Name FROM Account WHERE Industry = 'Technology'". Returns up to 2000 rows plus a next_records_url to page through more with continue_soql.

Fetch the next page of a large SOQL result set, using the next_records_url returned by run_soql/continue_soql.

Run a SOSL full-text search across multiple sObject types at once, e.g. "FIND {Acme} IN ALL FIELDS RETURNING Account(Id, Name), Contact(Id, Name)".

Run up to 25 different sObject operations in ONE atomic-or-not HTTP request -- Salesforce's own native batching, not a wrapper. Each sub-request has a reference_id so later sub-requests in the same call can reference its result.

Start a Bulk API 2.0 job for mass insert/update/upsert/delete/hardDelete/query/queryAll -- for volumes too large for single record calls or run_soql's 2000-row page (Bulk API 2.0 handles up to 150 million records per job). For insert/update/upsert/delete, pass csv_data (header row + data rows); for query/queryAll, pass a SOQL query instead.

Check the status of a Bulk API 2.0 job -- state, records processed, records failed.

List recent Bulk API 2.0 jobs in this org, most recent first.

Read the CSV results of a completed Bulk API 2.0 job -- successful records, failed records, unprocessed records, or the query rows for a query/queryAll job.

Abort a Bulk API 2.0 job that is still open or in progress.

Convert a Lead into an Account, Contact, and (optionally) an Opportunity -- Salesforce's own dedicated conversion process, not a plain field update. Requires the org's actual 'Converted' Lead Status picklist value.

Post a new Chatter feed item (a comment/update) on any record -- the collaboration layer Salesforce users see on a record's page.

Read the Chatter feed (comments/updates) posted on one record.

Add a comment to an existing Chatter feed item.

List files (ContentDocuments) attached to a record via the Files related list.

Upload a file and attach it to a record -- creates a ContentVersion and links it via ContentDocumentLink.

List Salesforce reports available to run.

Run a Salesforce report by Id and return its summarized result rows.

List Salesforce dashboards.

Read one dashboard's components/values by Id.

Submit a record into its assigned Approval Process (e.g. a big discount Opportunity, or an Expense Report over a threshold).

Approve, reject, or remove a pending approval work item -- acting on behalf of the assigned approver.

List pending approval work items across the org (records currently awaiting a decision).

Send a transactional email through Salesforce (using the org's own send-email capability), optionally logging it against a related record.

Read the org's current API/storage/feature limits and how much of each has been used -- e.g. daily API request budget remaining.

Publish a custom Platform Event -- Salesforce's own pub/sub messaging mechanism for notifying other systems/Flows/Apex triggers in near real time.

Update the same fields on up to 200 explicit records of one object type in a single call -- for routine batch fixes too small for a Bulk API 2.0 job.

Delete up to 200 explicit records of one object type in a single call -- for routine batch cleanup too small for a Bulk API 2.0 job.

Build an aggregated org health snapshot: API usage limits plus headline record counts (Account/Contact/Lead/Opportunity/Case) -- same value-add shape as MuleSoft/UiPath/Automation Anywhere/Blue Prism's estate audits.

Disconnect one Salesforce organization. Nothing in Salesforce itself is changed; only the saved credentials here are deleted.