update social nodes info
This commit is contained in:
Dave Conway-Jones
parent
dd250a77bc
commit
c60d62f27b
|
|
@ -27,8 +27,8 @@
|
|||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="dweetio out">
|
||||
<p>Sends the <b>msg.payload</b> to Dweet.io</p>
|
||||
<p>Optionally uses <b>msg.thing</b> to set the thing id, if not already set in the properties.</p>
|
||||
<p>Sends the <code>msg.payload</code> to Dweet.io</p>
|
||||
<p>Optionally uses <code>msg.thing</code> to set the thing id, if not already set in the properties.</p>
|
||||
<p>You need to make the thing id unique - you are recommended to use a GUID.<p>
|
||||
<p>For further info see the <a href="https://dweetio.io/" target="_new">Dweet.io website</a>.</p>
|
||||
</script>
|
||||
|
|
@ -70,7 +70,7 @@
|
|||
<script type="text/x-red" data-help-name="dweetio in">
|
||||
<p>Listens for messages from Dweet.io</p>
|
||||
<p>The thing id should be globally unique as they are all public - you are recommended to use a GUID.<p>
|
||||
<p>The Thing ID is set into <b>msg.dweet</b>, and the timesamp into <b>msg.created</b>.</p>
|
||||
<p>The Thing ID is set into <code>msg.dweet</code>, and the timesamp into <code>msg.created</code>.</p>
|
||||
<p>For further info see the <a href="https://dweetio.io/" target="_new">Dweet.io website</a>.</p>
|
||||
</script>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name" : "node-red-node-dweetio",
|
||||
"version" : "0.0.10",
|
||||
"version" : "0.0.11",
|
||||
"description" : "A Node-RED node to send and receive simple dweets",
|
||||
"dependencies" : {
|
||||
"node-dweetio" : "0.0.11"
|
||||
|
|
|
|||
|
|
@ -69,13 +69,13 @@
|
|||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="e-mail">
|
||||
<p>Sends the <b>msg.payload</b> as an email, with a subject of <b>msg.topic</b>.</p>
|
||||
<p>Sends the <code>msg.payload</code> as an email, with a subject of <code>msg.topic</code>.</p>
|
||||
<p>The default message recipient can be configured in the node, if it is left
|
||||
blank it should be set using the <b>msg.to</b> property of the incoming message.</p>
|
||||
blank it should be set using the <code>msg.to</code> property of the incoming message.</p>
|
||||
<p>The payload can be html format.</p>
|
||||
<p>If the payload is a binary buffer then it will be converted to an attachment.
|
||||
The filename should be set using <b>msg.filename</b>. Optionally <b>msg.description</b> can be added for the body text.</p>
|
||||
<p>Alternatively you may provide <b>msg.attachments</b> which should contain an array of one or
|
||||
The filename should be set using <code>msg.filename</code>. Optionally <code>msg.description</code> can be added for the body text.</p>
|
||||
<p>Alternatively you may provide <code>msg.attachments</code> which should contain an array of one or
|
||||
more attachments in <a href="https://www.npmjs.com/package/nodemailer#attachments" target="_new">nodemailer</a> format.</p>
|
||||
</script>
|
||||
|
||||
|
|
@ -153,9 +153,9 @@
|
|||
|
||||
<script type="text/x-red" data-help-name="e-mail in">
|
||||
<p>Repeatedly gets a <b>single email</b> from an IMAP server and forwards on as a msg if not already seen.</p>
|
||||
<p>The subject is loaded into <b>msg.topic</b> and <b>msg.payload</b> is the plain text body.
|
||||
If there is text/html then that is returned in <b>msg.html</b>. <b>msg.from</b> and <b>msg.date</b> are also set if you need them.</p>
|
||||
<p>Additionally <b>msg.header</b> contains the complete header object including
|
||||
<p>The subject is loaded into <code>msg.topic</code> and <code>msg.payload</code> is the plain text body.
|
||||
If there is text/html then that is returned in <code>msg.html</code>. <code>msg.from</code> and <code>msg.date</code> are also set if you need them.</p>
|
||||
<p>Additionally <code>msg.header</code> contains the complete header object including
|
||||
<i>to</i>, <i>cc</i> and other potentially useful properties.</p>
|
||||
<p>Uses the imap module.</p>
|
||||
<p><b>Note:</b> this node <i>only</i> gets the most recent single email from the inbox, so set the repeat (polling) time appropriately.</p>
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name" : "node-red-node-email",
|
||||
"version" : "0.1.0",
|
||||
"version" : "0.1.1",
|
||||
"description" : "Node-RED nodes to send and receive simple emails",
|
||||
"dependencies" : {
|
||||
"nodemailer" : "1.3.4",
|
||||
|
|
|
|||
|
|
@ -31,9 +31,9 @@
|
|||
|
||||
<script type="text/x-red" data-help-name="feedparse">
|
||||
<p>Monitors an RSS/atom feed for new entries.</p>
|
||||
<p>The <b>msg.topic</b> contains the original article link. The <b>msg.payload</b>
|
||||
contains the description, and <b>msg.article</b> contains the complete article object,
|
||||
which has properties such as <i>.title</i>, <i>.summary</i>, <i>.date</i> and so on.</p>
|
||||
<p>The <code>msg.topic</code> contains the original article link. The <code>msg.payload</code>
|
||||
contains the description, and <code>msg.article</code> contains the complete article object,
|
||||
which has properties such as <code>.title</code>, <code>.summary</code>, <code>.date</code> and so on.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/javascript">
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name": "node-red-node-feedparser",
|
||||
"version": "0.1.3",
|
||||
"version": "0.1.4",
|
||||
"description": "A Node-RED node to get RSS Atom feeds.",
|
||||
"dependencies": {
|
||||
"feedparser": "1.1.3",
|
||||
|
|
|
|||
|
|
@ -60,8 +60,7 @@
|
|||
Alternatively, if the number is left blank, it can be set using <code>msg.topic</code>.
|
||||
If the node is configured to make a call then the TWiML URL must be publically accessible.
|
||||
<p>You must have an account with Twilio to use this node. You can register for one <a href="https://www.twilio.com/">here</a>.</p>
|
||||
<p>You can either set your account details within the node, or provide it globally using either the settings file or a file
|
||||
called 'twiliokey.js' located in the directory above node-red.</p>
|
||||
<p>You can either set your account details within the node, or provide it globally using either the settings file.</p>
|
||||
<p>To use the settings.js file, add an entry such as:
|
||||
<pre>twilio: { account:'My-ACCOUNT-SID', authtoken:'TWILIO-TOKEN', from:'FROM-NUMBER' }</pre></p>
|
||||
<p>To use the 'twiliokey.js' file in the directory <b>above</b> node-red, use the following format:
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name" : "node-red-node-twilio",
|
||||
"version" : "0.0.8",
|
||||
"version" : "0.0.9",
|
||||
"description" : "A Node-RED node to send SMS messages via the Twilio service.",
|
||||
"dependencies" : {
|
||||
"twilio" : "1.6.0"
|
||||
|
|
|
|||
|
|
@ -125,9 +125,9 @@
|
|||
<li>direct messages received by the authenticated user</li>
|
||||
</ul></p>
|
||||
<p>Use space for <i>and</i> and comma , for <i>or</i> when searching for multiple terms.</p>
|
||||
<p>Sets the <b>msg.topic</b> to <i>tweets/</i> and then appends the senders screen name.</p>
|
||||
<p>Sets <b>msg.location</b> to the tweeters location if known.</p>
|
||||
<p>Sets <b>msg.tweet</b> to the full tweet object as documented by <a href="https://dev.twitter.com/overview/api/tweets">Twitter</a>.
|
||||
<p>Sets the <code>msg.topic</code> to <i>tweets/</i> and then appends the senders screen name.</p>
|
||||
<p>Sets <code>msg.location</code> to the tweeters location if known.</p>
|
||||
<p>Sets <code>msg.tweet</code> to the full tweet object as documented by <a href="https://dev.twitter.com/overview/api/tweets">Twitter</a>.
|
||||
<p><b>Note:</b> when set to a specific user's tweets, or your direct messages, the node is subject to
|
||||
Twitter's API rate limiting. If you deploy the flows multiple times within a 15 minute window, you may
|
||||
exceed the limit and will see errors from the node. These errors will clear when the current 15 minute window
|
||||
|
|
@ -201,11 +201,11 @@
|
|||
</script>
|
||||
|
||||
<script type="text/x-red" data-help-name="twitter out">
|
||||
<p>Twitter out node. Tweets the <b>msg.payload</b>.</p>
|
||||
<p>Twitter out node. Tweets the <code>msg.payload</code>.</p>
|
||||
<p>To send a Direct Message (DM) - use a payload like "D {username} {message}"</p>
|
||||
<p>If <b>msg.media</b> exists and is a Buffer object, this node will treat it
|
||||
<p>If <code>msg.media</code> exists and is a Buffer object, this node will treat it
|
||||
as an image and attach it to the tweet.</p>
|
||||
<p>If <b>msg.params</b> exists and is an object of name:value pairs,
|
||||
<p>If <code>msg.params</code> exists and is an object of name:value pairs,
|
||||
this node will treat it as parameters for the update request.</p>
|
||||
</script>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name" : "node-red-node-twitter",
|
||||
"version" : "0.1.4",
|
||||
"version" : "0.1.5",
|
||||
"description" : "A Node-RED node to talk to Twitter",
|
||||
"dependencies" : {
|
||||
"twitter-ng": "0.6.2",
|
||||
|
|
|
|||
|
|
@ -37,8 +37,8 @@
|
|||
<script type="text/x-red" data-help-name="xmpp in">
|
||||
<p>Connects to an XMPP server to receive messages.</p>
|
||||
<p>The <b>Buddy</b> field is the id of the buddy or room you want to receive messages from.</p>
|
||||
<p>Incoming messages will appear as <b>msg.payload</b> on the first output, while <b>msg.topic</b> will contain who it is from.</p>
|
||||
<p>The second output will show the presence and status of a user in <b>msg.payload</b>. Again <b>msg.topic</b> will hold the user.</p>
|
||||
<p>Incoming messages will appear as <code>msg.payload</code> on the first output, while <code>msg.topic</code> will contain who it is from.</p>
|
||||
<p>The second output will show the presence and status of a user in <code>msg.payload</code>. Again <code>msg.topic</code> will hold the user.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/javascript">
|
||||
|
|
@ -91,10 +91,10 @@
|
|||
|
||||
<script type="text/x-red" data-help-name="xmpp out">
|
||||
<p>Connects to an XMPP server to send messages.</p>
|
||||
<p>The <b>To</b> field is optional. If not set the <b>msg.topic</b> property of the message is used.</p>
|
||||
<p>If you are joining a room then the <b>To</b> field must be filled in.</p>
|
||||
<p>You may also send a msg with <b>msg.presence</b> to set your presence to one of <i>chat, away, dnd</i> or <i>xa</i>.
|
||||
If you do so then the <b>msg.payload</b> will set your status message.</p>
|
||||
<p>The <b>To</b> field is optional. If not set the <code>msg.topic</code> property of the message is used.</p>
|
||||
<p>If you are joining a room then the <b>To</b> field must be supplied.</p>
|
||||
<p>You may also send a msg with <code>msg.presence</code> to set your presence to one of <i>chat, away, dnd</i> or <i>xa</i>.
|
||||
If you do so then the <code>msg.payload</code> will set your status message.</p>
|
||||
</script>
|
||||
|
||||
<script type="text/javascript">
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
{
|
||||
"name" : "node-red-node-xmpp",
|
||||
"version" : "0.1.3",
|
||||
"version" : "0.1.4",
|
||||
"description" : "A Node-RED node to talk to an XMPP server",
|
||||
"dependencies" : {
|
||||
"simple-xmpp" : "1.3.*"
|
||||
|
|
|
|||
Loading…
Reference in New Issue