This repository contains a collection of contributed nodes for Losant's Visual Workflow Engine. These nodes provide additional capabilities and third-party integrations above and beyond the built-in nodes provided by the Losant workflow editor.
Each folder in this repository is made up of one or more .node files. Each file represents a self-contained node that can be imported into your Losant Application as a Custom Node.
First, download the .node file that you'd like to import to your local computer. Next, navigate to your application's Custom Nodes page by using the Workflows -> Custom Nodes main application menu. Lastly, import the node using the Import button that's located at the top-right of the Custom Node list. This will prompt you to upload the .node file you previously downloaded.
Once the Contributed Node is imported, it will immediately be available in the Custom Nodes section in your workflow palette.
| Node | Latest Version | Description |
|---|---|---|
| Address Lookup | v1.0.0 | Uses the Google Maps API to do a reverse lookup for GPS coordinates and returns the address found. |
| Aruba Meridian | v1.0.0 | Retrieves data from the Meridian Asset Tracking API. |
| Convert Temperature | v1.0.0 | Converts temperatures between Celsius, Fahrenheit, and Kelvin. |
| Dark Sky | v1.0.0 | Retrieves weather information from the Dark Sky API. |
| Downsample | v1.0.0 | Filters a streaming set of data by downsampling multiple data points into a single value. |
| GPS Distance | v1.0.0 | Calculates the distance, in meters, between two GPS coordinates. |
| Hologram | v1.0.0 | Retrieves details about a specific Hologram device. |
| Loggly | v1.0.0 | Log payload data to Loggly using their HTTP API. |
| Moving Average | v1.0.0 | Calculates a moving average over a configurable number of data points. |
| Particle | v1.0.0 | Provide access to Particle's Remote Diagnostics API to retrieve device information. |
| Sigfox | v1.0.0 | Provide access to Sigfox's REST API to retrieve a device's information. |
Contributing nodes to this catalog is an excellent way to expose your product or service to the Losant developer community.
The first step to contributing a node is to following the custom node documentation and walkthrough to develop your new node within your own Losant application. The existing nodes in this catalog provide great reference examples.
When you're ready to submit the node, create a version of the node using Semantic Versioning. Following Semantic Versioning is a requirement for all contributed nodes. This allows the consumers of these nodes to better understand the impact of each new revision.
Using Losant's built-in export feature, export the node to a .node file. The name of the .node file should be the same as your custom node's name with spaces replaced with dashes. For example, if your node's name is "Moving Average", the exported file should be named moving-average.node.
Contributing nodes to this catalog is performed by submitting a pull request against the master branch of this repository. Each contribution will be reviewed by the Losant team.
If you are contributing a single node, add a new folder with the name of the node. If your contribution is made up of several nodes, which is common for integrations with third-party services or APIs, name the folder after the service or product. Each folder can contain multiple .node files.
If at all possible, try to keep each node self-contained, which means they do not depend on other contributed nodes for their functionality.
Add a README.md file to your folder with instructions on how to properly consume your contributed node. Refer to the nodes in this repository for example readme files.
Add a LICENSE file to your folder with your specific licensing terms. Losant prefers the MIT License where applicable.
Copyright © 2018 Losant IoT, Inc