Configuring a pushbullet credential in n8n

Describe the problem/error/question

Hello. I am using the self hosted version of n8n, and I was going through the list of services that you (the n8n devs) have included integrations for to see what all I can automate, and I eventually got to the pushbullet account. Since I have a pushbullet account, I attempted to link it with n8n when I noticed something interesting. N8n seems to indicate that the only method available to authenticate to the pushbullet api is via an Oauth2 app, however, when I log into my pushbullet account, not only do I not see any way to create an Oauth2 app, but I do see that pushbullet does have the ability to allow users to authenticate via a generated access token (see below image). Now, I am not sure if pushbullet actually does allow for users to authenticate via Oauth2, but I do know that there is an option to authenticate via a generated access token that n8n does not take advantage of that it probably should. Just my thoughts on the matter.

What is the error message (if any)?

Please share your workflow

No workflow.  Just trying to create a pushbullet credential object.

Share the output returned by the last node

None of this is applicable.

Information on your n8n setup

  • Not
  • Applicable

you’re right — pushbullet def supports API tokens, but n8n currently only supports OAuth2 for this integration. more of a feature request than a config issue. if it’s blocking your workflow, might be worth checking github issues to see if anyone else requested this

1 Like

I’m going to check it out and find a solution for you

Fixed it for you fist you go here Pushbullet - Your devices working better together and set upand oauth client just fill in the redirect_uri: https://oauth.n8n.cloud/oauth2/callback
as for th allowed_origin: * or something more secure depending on your use case
then they will give you a client_id: and client_secret: , get those and go to n8n and put it in the authentication part and then click on the connect to pushbullet account and your done

hope this helps you out reach out if you need more help

welcome to the n8n community @enthusedcoder
So for now, I’d probably skip the built-in Pushbullet credential and call the Pushbullet API through an HTTP Request node instead, using my access token in the auth header, or Basic Auth as described in Pushbullet’s docs.