Missing credentials

If an automation or workflow has failed, you may have seen the following error message:

monday.com is failing to correctly send credentials.

Follow the steps at https://credentials.m365.app/

What’s happening here?

Automations can fail for a number of reasons, but when the above error message is sent by the automation block, this is because there is an error in the way that monday.com’s own OAuth credentials infrastructure is working.

When an automation block runs, our app requests that monday.com provides us with a new set of credentials to access Microsoft 365. This process is completely abstracted away from our app by monday.com, so that the app only even has access to a short-lived access token for Microsoft 365 access.

If monday.com fails to correctly present our app with a valid access token for Microsoft 365, then the above error message is displayed, and the automation block fails.

What to do next?

Contact support@monday.com with details of the automation block which is failing.

To speed up support ticket resolution:

Provide them with a link to this page to give them additional context on the reason that the automation block is failing
Preemptively grant them remote support access, and tell them that you have done this
Provide them with a link to the board which the automation block was used on, and if it’s called from a workflow, also provide a link to the workflow
Ask them to add support@dsapps.dev to the support ticket too, so that we can track progress on the ticket

If you miss out any of the first 3 steps above, expect to be asked those in one of the first few replies you receive from monday.com support.

Technical details (for monday.com support)

This section is included to help monday.com support to understand the problem that is occuring.

During normal times, the automation block expects monday.com to POST a payload to the app which is in the following shape:

CODE

{
  "payload": {
    "credentialsValues": {
      "microsoftToken": {
        "userCredentialsId": 1231,
        "accessToken": "..."
      }
    }
    ...
  }
}

We use the accessToken part of this, which is supplied by monday.com to connect to the Microsoft Graph APIs on the user’s behalf.

When this problem occurs, the payload is in a different shape, and looks more similar to this:

CODE

{
  "payload": {
    "credentialsValues": { }
    ...
  }
}

The access token required to connect to Microsoft 365 is missing from the payload, so the connection with Microsoft 365 cannot be made.

In order for this automation block to work as normal, the monday.com infrastrcuture must be fixed to provide a correctly shaped payload to this app.