PusherRequestError when using Run Node.js code with Pusher step

Help
,
1

This topic was automatically generated from Slack. You can find the original thread here.

Grady Sain : does anybody here use pusher.com with pipedream? I’m having some newb troubles

2

Dylan Sather (Pipedream) : Hi , I built that integration so could probably help you out. What kind of trouble are you having?

3

Grady Sain : hi Dylan, i’m getting this error (today is my first day w both pusher and pipedream so i have no clue what i’m doing)

We got an unhandledRejection in this step.  Please check that you are awaiting all your promises. The error was: PusherRequestError: Request failed with an error
4

Dylan Sather (Pipedream) : Would you mind clicking the Share button in the top-right of your workflow, and share it with dylan@pipedream.com ?

5

Grady Sain : sent… di u get it?

6

Dylan Sather (Pipedream) : I did, thanks

7

Grady Sain : i’m using free account / sandbox and … pusher channel if that helps

8

Dylan Sather (Pipedream) : I’m trying to replicate on my end (I’ve also for a free pusher account)

9

Dylan Sather (Pipedream) : Would you mind pasting the following code in the test Pusher step in your workflow and trying to run it once more?

const Pusher = require('pusher')

const { appId, key, secret, cluster } = auths.pusher
const pusher = new Pusher({
  appId,
  key,
  secret,
  cluster,
  useTLS: true
})

await pusher.trigger('my-channel', 'my-event', {
  "message": "hello world"
})
10

Grady Sain : replace all code? or append?

11

Dylan Sather (Pipedream) : replace all the code in that step. You can also add a new step to your workflow, find the Pusher app, and choose the option to Run Node.js code with Pusher - I’ve modified the step to include this code, which should work now.

12

Dylan Sather (Pipedream) : (Pusher appears to have changed their npm package, hence the change I had to make here)

13

Grady Sain : question- in my Create a new connection to Pusher dialog i enter the appId, kety, etc… with double quotes … like “xxxx” maybe a problem?

14

Grady Sain : getting a different error now…

15

Grady Sain : ```
This step was still trying to run code when the step ended. Make sure you promisify callback functions and await all Promises. (Reason: GetAddrInfoReqWrap, Learn more: Running asynchronous code)

16

Dylan Sather (Pipedream) : Would you mind trying to connect a new Pusher account to that step, just to make sure your credentials were properly configured? I’m not able to replicate on my Pusher account, with the same code, and while the error from Pusher doesn’t provide great detail, I have a feeling it could be related to that.

17

Dylan Sather (Pipedream) : if you hover over the connected Pusher account above the code, you should see the option to unlink the account, and try configuring a new account and enter your details from the App Keys section of your Pusher account once more .

You can also visit Connected Accounts - Pipedream, find your Pusher account, and click on the ellipsis on the right of the account, choosing the option to Reconnect. That’ll let you see / edit your current account details

18

Dylan Sather (Pipedream) : I just want to make sure everything in Pipedream is consistent with what you’re seeing in the App Keys section of Pusher

19

Grady Sain : on it… but should i be using quotes in the field for appId, key , etc…

20

Grady Sain : it was the quotes i think. seems like it’s working now… my next step is to learn what i can do with the new toys :slightly_smiling_face: thanks!