PipedreamHQ / pipedream

Connect APIs, remarkably fast. Free for developers.
https://pipedream.com
Other
8.9k stars 5.27k forks source link

[BUG] Vestaboard `get_current_message` throws error #7587

Closed johndbritton closed 1 year ago

johndbritton commented 1 year ago

Describe the bug When I use the get_current_message action, I get an error.

To Reproduce Steps to reproduce the behavior:

  1. Go to edit a workflow
  2. Add a step and choose Vestabord - get_current_message
  3. Select the correct account
  4. See error: {"status":"error","message":"Missing Read / Write Key"}

Expected behavior Retrieve the current message.

Screenshots N/A

Desktop (please complete the following information):

Additional context The account is configured correctly, the create_message action works fine.

vunguyenhung commented 1 year ago

Hi @johndbritton, I don't have a vestaboard myself so I couldn't reproduce your issue. So my only suggestion for now is that could you double check they readwrite key you have input in the connection popup? image

johndbritton commented 1 year ago

Here's what I see:

Screenshot 2023-08-15 at 12 47 05 PM

My account credentials are stored as part of jdb-board. In another step I can use the same account successfully:

Screenshot 2023-08-15 at 12 48 54 PM

The only thing that I can think of is that the create_message has a subscription parameter, is something similar needed for the get_current_message?

dylburger commented 1 year ago

Without more information, I'm going to close this issue. Feel free to reopen and add more details, if you'd like.

vunguyenhung commented 1 year ago

Hi @johndbritton, sorry for the late response. Would you mind confirming that you have inputed the Read/Write key correctly? Since the Get Current Message and Create Message used different APIs, so they might work differently

Screenshot 2023-08-23 at 09 48 36
dylburger commented 1 year ago

Without more information, I'm going to close this issue. Feel free to reopen and add more details, if you'd like.

johndbritton commented 1 year ago

@vunguyenhung The readwrite API key was missing, but other values were included. That fixed it. I didn't realize there were multiple keys needed.

Thanks!