<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[send the flic button and action in http request body]]></title><description><![CDATA[<p dir="auto">Re: <a href="/topic/17330/http-apply-default-settings-and-flic-id-variable">HTTP 'apply default settings' and 'Flic ID' variable?</a></p>
<p dir="auto">Is there a way to automatically include the flic button id into the body of a http request and also the type of clic that has triggered the button?</p>
<p dir="auto">I have several buttons, and hate to create separate bodies now for each button when they all need to access my own raspberry pi. Would be nice if it could be done with default variables like $ID and $ACTION</p>
]]></description><link>https://community.flic.io/topic/17938/send-the-flic-button-and-action-in-http-request-body</link><generator>RSS for Node</generator><lastBuildDate>Wed, 11 Mar 2026 06:38:35 GMT</lastBuildDate><atom:link href="https://community.flic.io/topic/17938.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 07 Oct 2020 14:56:57 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to send the flic button and action in http request body on Wed, 28 Oct 2020 06:23:04 GMT]]></title><description><![CDATA[<p dir="auto">The HTTP header does contain the following information: button-serial-number; button-battery-level; button-name. I agree it would be nice if it also included the button-action. I just put the info in the URL (eg <code>flic/1/click</code>) so I don't have to set a body. I then handle this in Node Red where I can specify the endpoint as <code>flic/:from/:action</code> and it pulls the parameters out for me automatically.</p>
]]></description><link>https://community.flic.io/post/19597</link><guid isPermaLink="true">https://community.flic.io/post/19597</guid><dc:creator><![CDATA[michael]]></dc:creator><pubDate>Wed, 28 Oct 2020 06:23:04 GMT</pubDate></item></channel></rss>