← Back to Skills Marketplace
20410
Downloads
8
Stars
0
Active Installs
19
Versions
Install in OpenClaw
/install salesforce-api
Description
Salesforce CRM API integration with managed OAuth. Install only if you need Salesforce CRM administration. Connect with the narrowest Salesforce permissions available, prefer sandbox orgs for destructive or batch work, verify the intended connection ID before each request, and revoke unused connections promptly. This integration can mutate CRM records — approve only specific write actions after checking the exact sObject, record IDs, and consequence. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Salesforce connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Salesforce action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Salesforce examples; they add no Salesforce capability - Salesforce is not an event source, a trigger cannot read Salesforce data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).
Usage Guidance
Install this only if you want an agent to access Salesforce through Maton. Use the narrowest Salesforce scopes, prefer sandbox orgs for destructive or batch work, confirm the exact connection and record IDs before writes, and remove unused connections, functions, triggers, and destinations when finished.
Capability Assessment
Credentials
Network access, a Maton account, Salesforce OAuth, and Bash use are proportionate to a CRM API gateway skill. The artifact warns that Salesforce data may include personal and regulated business data and gives scoping guidance.
Install Mechanism
Installation uses pinned Maton CLI/SDK packages from npm, Homebrew, pip, and npm SDK examples. This is expected for the integration, but users should install only from the named Maton sources and upgrade deliberately.
Instruction Scope
The instructions repeatedly require explicit user approval for new connections, writes, deletes, batch/composite operations, hosted functions, trigger destinations, and local --exec handlers; they also default to read/list operations and warn against broad exports.
Persistence & Privilege
OAuth tokens, Maton connections, hosted functions, trigger destinations, environment variables, and watch checkpoints can persist beyond one session, but these behaviors are disclosed and tied to user-approved CRM automation workflows.
Purpose & Capability
The skill's stated purpose is Salesforce CRM administration via Maton OAuth, and the documented capabilities match that purpose: SOQL queries, sObject CRUD, composite operations, and optional hosted functions/triggers.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install salesforce-api - After installation, invoke the skill by name or use
/salesforce-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.8
Simplify the login instructions to the code flow (maton login prints a link; finish with maton login --code <CODE>), drop the API Key subsection, and pin the Maton CLI install to 0.4.0.
v1.2.7
- Removed the file skill-card.md.
- No changes to code or user-facing functionality.
- Documentation and interfaces remain unchanged.
v1.2.6
Switch the login instructions to the device flow (maton login prints a link and a user code; the --oauth flag is gone) and pin the Maton CLI install to 0.3.5.
v1.2.5
Pin the Maton CLI install to 0.3.4, the current release.
v1.2.4
Add this skill's own trigger policy to the shared Triggers section: the only destination it sets up is its own hosted function inside the platform, it does not forward events to third-party hosts, and it does not use event watch --exec; each trigger reference now also says this skill configures no trigger from that source on its own.
v1.2.3
Bring the skill to the current api-gateway baseline and tell the connection-to-function-to-trigger story: the shared Functions and Triggers sections open with an example for this app (a hosted function that performs one action for it through the Maton SDK, and the trigger that runs it - its own event source where it has one, otherwise a time schedule), the description says these constructs turn the connection into automation and add no capability of their own, the passthrough is described by its enforced boundary, CLI and SDK installs are pinned to 0.3.1, absolute API URLs are placeholders, and multipart uploads use mktemp.
v1.2.2
Resolve remaining audit findings: state one consistent endpoint policy instead of conflicting scope claims, qualify the local-execution and high-impact wording, note that locale examples are illustrative, and correct app-specific auth, method and upload-path documentation
v1.2.1
Address security-audit findings: disclose the api passthrough in the access-scope and description text, warn on irreversible connection deletion, add response data-minimization guidance, and correct app-specific auth and request-body notes
v1.2.0
CLI-first rewrite with the Maton SDK examples; clarify that the CLI and SDKs keep separate credential stores, and reword webhook egress warnings
v1.1.0
CLI-first rewrite: the maton CLI with OAuth login is the documented path, every example is a maton command, SDK examples added, and the raw HTTP fallback feeds the key on stdin instead of reading it from the environment
v1.0.8
- Removed the file skill-card.md.
- No other functional or documentation changes in this release.
v1.0.7
- Adds CLI and Homebrew installation instructions for Maton CLI, expanding usage options.
- Updates API examples and references from Salesforce API version v59.0 to v63.0.
- Documents direct CLI commands for common actions (SOQL queries, connections) alongside Python and HTTP examples.
- Clarifies connection management and explicit connection selection, now with CLI examples.
- Improves authentication instructions by including CLI login/interactive login commands.
- No functional/API changes to the underlying integration; documentation update only.
v1.0.6
- Added strong security guidance: treat the API key as secret, rotate if exposed, and revoke unused Salesforce connections promptly.
- Updated description and usage to emphasize least-privilege OAuth, sandbox use for risky actions, and always verifying connection ID before requests.
- Clarified that only supported/documented endpoint paths should be used.
- Instructions now require explicit user confirmation with details before any write or batch operation; added steps to confirm record and intended impact.
- Emphasized defaulting to read-only actions and increased caution on all composite/batch operations.
v1.0.5
- Updated all Maton API endpoints from gateway.maton.ai and ctrl.maton.ai to api.maton.ai for consistency.
- Clarified instructions for specifying a Salesforce connection via the Maton-Connection header, emphasizing its use when multiple connections exist.
- Added a new "Security & Permissions" section requiring explicit user approval before any write operations (create, update, delete).
- Removed LICENSE.txt file.
v1.0.4
- Added a metadata.clawdbot section to SKILL.md, specifying a brain emoji and required environment variable (MATON_API_KEY).
- No functional changes to code or documentation content.
v1.0.3
- No file changes were detected in this version.
- Documentation, API references, code examples, and usage instructions remain unchanged.
- No new features, bug fixes, or enhancements introduced in this release.
v1.0.2
- Added suggestion to use the api-gateway skill for other third party apps in the description.
- Updated all connection management, quick start, and usage examples to use Python scripts instead of curl/bash.
- No changes to the skill logic or API endpoints; documentation improvements only.
v1.0.1
- Base URL instructions clarified to use /salesforce/{native-api-path}, explaining direct mapping to Salesforce endpoints.
- Expanded OAuth connection example response to include fields such as creation_time, last_updated_time, and metadata.
- Instructions now explain explicitly how to specify a Salesforce connection with the Maton-Connection header and clarify default selection.
- Authentication steps updated to mention creating a Maton account if you don't have one.
- Minor improvements for clarity in usage and connection handling instructions.
v1.0.0
Salesforce skill has been redesigned to use managed OAuth and direct REST API integration via Maton.
- Replaced CLI-based workflow with Maton-powered REST API endpoints.
- Managed Salesforce authentication, connections, and environments via Maton control panel.
- Added example code for Python and JavaScript.
- Documented CRUD, SOQL/SOSL query, composite, batch, describe, and admin operations.
- Centralized error handling and streamlined usage with a single API key.
Metadata
Frequently Asked Questions
What is Salesforce?
Salesforce CRM API integration with managed OAuth. Install only if you need Salesforce CRM administration. Connect with the narrowest Salesforce permissions available, prefer sandbox orgs for destructive or batch work, verify the intended connection ID before each request, and revoke unused connections promptly. This integration can mutate CRM records — approve only specific write actions after checking the exact sObject, record IDs, and consequence. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Salesforce connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Salesforce action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Salesforce examples; they add no Salesforce capability - Salesforce is not an event source, a trigger cannot read Salesforce data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe). It is an AI Agent Skill for Claude Code / OpenClaw, with 20410 downloads so far.
How do I install Salesforce?
Run "/install salesforce-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Salesforce free?
Yes, Salesforce is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Salesforce support?
Salesforce is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Salesforce?
It is built and maintained by byungkyu (@byungkyu); the current version is v1.2.8.
More Skills