Notify when credentials for Node expire (require re-authentication)

Feature Requests
, , ,
1

The idea is:

I would like a notification of some kind (preferably email) whenever my credentials for a specific node has expired (for example, GMail or MySQL nodes).

My use case:

When a credential expires, it silently does so and I’ll only know it has expired by observing (or the lack of observing) its effects. I’d like to know directly and automatically via email.

I think it would be beneficial to add this because:

This would allow seemless implementation of my workflows, preventing them from being disrupted by the credentials expiring.

Are you willing to work on this?

Sure. Also, open to work arounds if others have found a simple solution to this issue.

2

Thanks for the suggestion! And don’t forget to upvote it :slight_smile:

3

I can’t believe this has not been implemented. This is pretty essential for any semi important workflow. Essentially any automations can silently stop working without warning, if their credentials expire.

  1. is there any way to know when credentials will expire?
  2. is there any work around for this? e.g. a workflow that can detect an expired cred and send an email (or even an API call?)
1 Like
4

You can identify if a credential has expired by setting the node to “Continue on error” instead of the default “Stop Workflow”

The output of the node will be an error and you can handle it with an IF node:

If there is an error (true) you can define whatever action you want: pushover or email notification.

if there is no error you connect the false branch to your the node.

5

Thanks for the workaround. This can help but I’d rather have a workflow triggering every 10mins etc to check the credentials work, like Zapier.

e.g. I don’t want to have to wait for a trigger to fail or do an action on a service provider to actually test credentials. I want to catch them before something fails (e.g. on a timer).

Simply put, a lot of nodes do not have an “empty” action e.g. list/search rather than create/update/do something type action etc so they can’t be easily used to test credential with an “if” node.

However, n8n already has the ability to test a credential (without preforming an action on the service provider) from the UI on the Credentials page, opening a credential and then clicking the “Rety” button on some credentials to retest the connection.

It would be great if frequent credential testing could be built-in to n8n, for all services used in a workflow as trigger, or at least expose the “test credential” UI feature under the “n8n” node so that we can run tests on a schedule using a workflow.