node-red-contrib-salesforce

A set of Node-RED nodes to interact with Salesforce and Force.com.

Install

---

Run the following command in the root directory of your Node-RED install

npm install node-red-contrib-salesforce-bp3

Usage

Each node uses a connection object to hold and share Salesforce connected app settings (consumer key, consumer secret, username, etc.). This determines the org that each node operates against.

The credential fields can be left blank and passed in the message (msg.sf), this allows you to store them outside of the flow so that they will not be exposed when exporting it.

SOQL

Executes a SOQL query.

select id, name
from contact
limit 2

The resulting message has the following properties:

• msg.payload.size - the number of records returned from the query.
• msg.payload.records - the array of records returned from the query.

The query can be configured in the node, however if left blank, the query should be set in an incoming message on msg.query.

By default the query will return the first 2,000 records from the query result. If you wish to return the full result set then tick the 'Fetch all result records' checkbox.

See the Salesforce SOQL documentation for more information.

SOSL

Executes a SOSL query.

FIND {united*} IN ALL FIELDS
RETURNING Account (Id, Name), Contact (Id, Name)

The resulting message has the following properties:

• msg.payload.size - the number of records returned from the query.
• msg.payload.records - the array of records returned from the query.

The query can be configured in the node, however if left blank, the query should be set in an incoming message on msg.query.

See the Salesforce SOSL documentation for more information.

DML

Executes an insert, update, upsert or delete DML statement.

The action and object can be configured in the node, however if left blank, the following should be set in an incoming message:

• msg.action - the DML action to perform
• msg.object - the sObject for the DML action

Insert Action

This action inserts the contents of msg.payload and returns the newly created ID.

{
firstname: "Nikola",
lastname: "Tesla"
}

Update Action

This action updates the specified record with the the contents of msg.payload. It assumes that the payload contains an id property with the id of the record to be updated.

{
id: "00337000002uFbW",
firstname: "Nikola",
lastname: "Tesla"
}

Upsert Action

The upsert action matches contents of the msg.payload with existing records by comparing values of one field. If you don’t specify a field when calling this action, the operation uses the id value in the msg.payload to match with existing records to update. Alternatively, you can specify a field to use for matching in msg.externalId. This field must be marked as external ID. If a matching record is not found, a new records is inserted.

Sample msg.payload to be used with an external id.

{
firstname: "Nikola",
lastname: "Tesla"
}

Sample msg.externalId specifying the field and value to be used for matching.

{
field: "Ext_ID_c",
value: "12345"
}

If record(s) are updated, the resulting payload will resemble:

{
"payload": {
"success": true,
"object": "contact",
"id": {
  "field": "Ext_ID__c",
  "value": "12345"
},
"action": "update"
}
}

If a new record is inserted, the resulting payload will resemble the following containing the id of the newly created record:

{
"payload": {
"success": true,
"object": "contact",
"id": "00337000002uwUVAAY",
"action": "insert"
}
}

Delete Action

This action deletes the record specified by the id property in msg.payload.

{
"id": "00337000002uwUVAAY"
}

See the Apex DML Operations for more information.

Streaming

Creates a client that subscribes to a PushTopic for the Streaming API.

When the client receives a message it sends `msg.payload` with the following:

• msg.payload.event - the information on the event that was received.
• msg.payload.sobject - the sobject information received.

Assuming the PushTopic was created with the query SELECT Id, Name FROM Contact, then a resulting message would look like:

{
"event": {
"type": "updated", "createdDate": "2015-07-31T18:38:21.000+0000"
},
"sobject": {
"Name": "Nikola Tesla", "Id": "a0037000001pplrZZZ"
}
}

See the Quick Start Using Workbench to get started or the Streaming API documentation for complete details.

OBM

When used with an http in node, parses the XML from a Salesforce Outbound Message to a JSON object.

The resulting msg.payload should look something like:

{
"organizationId": "00D37000000PdLZAE1",
"actionId": "04k370000008OrqZZE",
"sobject": {
"type": "Contact",
"id": "a0037000001I1EvWWO",
"name": "Nikola Tesla",
"firstname": "Nikola",
"lastname": "Tesla"
},
"sessionId": "00D37000000PdLB!"
}

Connect this node downstream from a POST http input node to parse the XML received from an Outbound Message call from Salesforce. Use the URL from the http in node for the Endpoint URL for your Outbound Message.

See the Salesforce Setting Up Outbound Messaging documentation for more information.