How to avoid HTTP 400 Bad Request invalid_payload (“no_text”):Įrror 400 will be returned by slack upon each incoming webhook packet from Particle. Url: the URL provided by the slack app setupĭevice: set as you desire to the device to listen for Quality points for this webhook integration setup in Particle:ĮventName: make sure it matches exactly the Then create a webhook integration in Particle PARTICLE_WEBHOOK.( this generates the URL that the webhook coming from the particle cloud needs).Then make it listen for webhooks SLACK_WEBHOOKS First create a slack app CREATE_SLACK_APP. On the slack side you need to create an app that listens for webhooks.I updated the title of this thread to reflect the data movement I chose and provide a lessons learned about when I did it. Webhooks to will NOT work on default settings, so read on… Requesting advice on how to go about doing what I’m trying to do in a simple sensible way. I do not need to keep/store the data… only interested in the most recent status update for each sensor).īased on searching through the forums and reading documentation… I think I’ll want to getEventStream doc_link ?īut I also see words like “JSON” - which I’m about to google… (which can be at irregular intervals, and the app will track a lot of these sensor reported events.

Not sure if I should try a google doc route and keep track of a status message by device id or exactly how to arrange the information… but big picture I need to get the data from the cloud to ultimately update a javascript app as the events happen. I will need to be able to tell which device is sending a message. Essentially I just need to write a program that can listen for and then pull from the cloud the simple text/string events as they are published by the device.

My electron doodad is now Particle.publishing to the cloud.

Slack webhooks formatting