about from the node red website https //nodered org/ node red is an open source project originally developed by ibm to provide a simple, visual, low code development tool for wiring together hardware devices, apis and other online services servicely promotes node red as a simple alternative for more complex middleware systems (microsoft biztalk, mulesoft anypoint, oracle fusion, etc ) for clients that have simple requirements for integrating servicely with on premise or behind the firewall applications what is it used for a node red (or any other middleware product) is useful in a number of situations for example where connectivity between servicely and a target system is limited for example querying active directory account status for an on premise active directory system populating servicely account information from an on premise ldap directory credentials for executing actions belong outside of servicely for example adding users to an active directory group without servicely requiring an authorized account integrating applications use methods not natively supported by servicely for example loading user or other information from a file drop loading information from on premise databases integrating with in house message queuing systems in these situations, node red can easily be configured to securely perform these actions without servicely requiring direct (inbound) connectivity or credentials installation the node red getting started page https //nodered org/docs/getting started/ should provide enough information for any system additionally, you should follow the recommendations on the https //nodered org/docs/user guide/runtime/securing node red https //nodered org/docs/user guide/runtime/securing node red page to ensure the installation is secure, including https encryption and enforced authentication installing servicely nodes the official documentation for adding nodes to the node red palette is here https //nodered org/docs/user guide/runtime/adding nodes this is a simple process as demonstrated below nodes queue queue nodes connect a node red flow to a servicely instances asynchronousqueue events these events can be triggered by end users executing ‘smart actions’, initiated by triggers, or triggered by scheduled imports/jobs success response to messages initiated from the queue node, and marks the event as having succeeded the corresponding queue event in servicely will be marked as being completed and successful failure responds to messages initiated from the queue node, and marks the event as having failed the corresponding queue event in servicley will be marked as competed, but having failed connector a connector node is used to configure the servicely instance subsequent nodes are to use if not otherwise configured the rest, import and transform nodes are examples of nodes that can use the instance configured by this node note that this node is typically not required if a queue node was used to initiate a flow, as the queue node also sets this connection information this node is typically used from client initiated flows (e g responding to an event on the client side, not a servicely asynchronousqueue event) rest provides a simple mechanism to interact with the servicely rest api to query or update records import provides the ability to load data into a servicely importtable import tables are staging tables that allow etl type activities to be performed on data extracted from other systems usually used in conjunction with the transform node transform provides the ability to apply an import transform to previously imported data (using the import node) always used in conjuction with the import node