Hi there,
Any plans to support Pressy?
http://get.pressybutton.com/
Thanks,
Pete
Search found 5 matches
- 26 Aug 2013 12:57
- Forum: User Help / Bug Reports
- Topic: HTTP Request action not URL encoding variables
- Replies: 3
- Views: 10371
Re: HTTP Request action not URL encoding variables
Hi Martin,
Just wanted to say thanks for adding the encodeUrl function. It's working brilliantly for me.
Cheers,
Pete
Just wanted to say thanks for adding the encodeUrl function. It's working brilliantly for me.
Cheers,
Pete
- 21 Jun 2013 10:08
- Forum: User Help / Bug Reports
- Topic: How do I exclude a number from receiving an SMS
- Replies: 1
- Views: 7069
Re: How do I exclude a number from receiving an SMS
The way I do this is to add a condition and check the {sms_sender} variable, then branch accordingly.
- 23 May 2013 19:11
- Forum: User Help / Bug Reports
- Topic: HTTP Request action not URL encoding variables
- Replies: 3
- Views: 10371
Re: HTTP Request action not URL encoding variables
Hi Martin,
Thanks for taking the time to reply.
An inbuilt function to do the encoding would be awesome!
In the meantime, I'll probably just stick with using Prowl via email, but I would prefer to use an HTTP Request.
Cheers,
Pete
Thanks for taking the time to reply.
An inbuilt function to do the encoding would be awesome!
In the meantime, I'll probably just stick with using Prowl via email, but I would prefer to use an HTTP Request.
Cheers,
Pete
- 22 May 2013 20:20
- Forum: User Help / Bug Reports
- Topic: HTTP Request action not URL encoding variables
- Replies: 3
- Views: 10371
HTTP Request action not URL encoding variables
Hi, Just getting into this really cool tool, but have found what I believe to be a bug. I created a simple flow to forward any received SMS to Prowl using an HTTP request action. While testing I was only using the word "test" (no quotes) but when I sent a text more than one word in, e.g. "This is a ...