A Node.js REST API wrapper for Salesforce, Force.com, and Database.com, simplifying integration with OAuth helpers and streaming support.
nforce is a Node.js library that wraps the Salesforce REST API, providing a streamlined interface for authentication, CRUD operations, queries, and streaming. It solves the problem of verbose Salesforce integration by offering intelligent sObject handling, OAuth helpers, and a plugin system.
Node.js developers building applications that need to integrate with Salesforce, Force.com, or Database.com, especially those working on backend services or integration tools.
Developers choose nforce for its clean API, multi‑user OAuth support, built‑in streaming client, and extensibility via plugins—reducing the boilerplate required for Salesforce integrations compared to raw REST calls.
nforce is a node.js salesforce REST API wrapper for force.com, database.com, and salesforce.com
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides native promise support and callbacks, simplifying asynchronous Salesforce operations compared to raw REST calls, as shown in the query and CRUD examples.
Factory methods and change tracking for Salesforce records reduce boilerplate code for CRUD operations, with automatic field update detection for efficient writes.
Supports both single-user and multi-user modes with auto-refresh tokens, making it suitable for multi-tenant applications without re-authenticating frequently.
Easy integration with Salesforce PushTopics and Platform Events via a dedicated stream client, enabling real-time data updates without additional dependencies.
The repository is explicitly archived with no updates, bug fixes, or security patches, posing a significant risk for production use and future compatibility.
Core functionality is limited to basic REST APIs; accessing Tooling, Chatter, or Metadata APIs requires community plugins that may be outdated or unsupported.
Being unmaintained, the documentation and examples might not reflect current Salesforce API changes or best practices, increasing implementation hurdles.