sheaffy/node-red-contrib-monzo

This is a wrapper that will allow a connection to the monzo bank API for use within node-red

node-red-contrib-monzo's Issues

Monzo Webhooks

Create a "Monzo live" node, which will use Webhooks to receive live transactions and live notifications from Monzo.

clarify in readme what monzo is

Interesting node.
I think it would be good for people who don't know "monzo" to make clear in the readme that it is a bank that is currently only available for UK residents.

Returning duplicate responses for one account with other(s) missing.

When I trigger the 'monzo in' node with 'all accounts' setting, I get three separate output messages - all three are identical, and for only one account. My login should show two accounts (one in my name, and a joint account, plus potentially two savings accounts). The three responses I get are for the joint account data only.

I think it's setup correctly and I don't think I was given any options around which specific accounts the auth could access.

Any thoughts?

Monzo Credentials

The ability to correctly authenticate as described by the Monzo API docs, by creating a Monzo "client" requesting an access code and getting a refresh token and an access token.. then use the refresh token and client secret every 7 hours to get a new and valid access token..
This will be in addition to the current "enter access token" from the playground. so as to allow for backwards compatability.

Webhook doesn't work after a deploy

Hi,

Firstly great component - very cool.

Noticed no monzo messages were coming from, but the web server reverse proxy was showing the requests were coming in and were successful. Adding some console.logs in the code, and posting data to it from postman comes to the conclusion that when nodered first loads, the node works - when you deploy changes, the node stops outputting what it's getting - despite the fact the node is getting the messages.

My hunch (but I'm new to nodered dev so I could be wrong) - is that the listener on the url is hanging around, but trying to push to an old instance of the node - is it possible that we need to destroy the listener on the close function at the bottom of the webhook file, so it gets recreated with the new node var?

I've kinda come to the end of my knowledge of nodered - otherwise I'd fix it, I'm not sure how you destroy the RED.httpAdmin.post - and I might be going down the wrong path anyway.

Is it possible you can have a look?

Thanks

unable to authenticate

Hey, I know this node is super old! wondering if its still in use. I'm trying to set it up, I have logged onto the Monzo API and created a new OAuth Client with the confidential flag set to true. I then copy the client id and secret into the node settings and clicking Authorise with Monzo takes me to the Developer page, then when I type in my email and click next I get "Oops, there was a problem sending your magic link"?

Do I need to do have anything in the redirect URL of the OAuth client? or does this node just no longer work with Monzo?