
Project data from Monday.com
Yres retrieves data from monday.com through the monday.com GraphQL API, at the fixed address https://api.monday.com/v2. It signs in with a personal API v2 token that is sent as an Authorization header on every call. The token has the same permissions as the user who created it, so that user determines which boards Yres can read. The retrieved data lands in an Azure SQL database in your own Azure tenant, where it can be combined with your other sources for Power BI.
If you only want to follow the progress of projects and tasks, the views inside monday.com are enough and you do not need a data warehouse.
Yres earns its place once the work in monday.com has to sit next to figures from other systems, such as logged hours, invoicing or staffing, or when you want to see what a board looked like on an earlier date. monday.com shows the state of today; the data warehouse keeps earlier versions of changed rows.
Every board the user behind the API token has read access to, and no others. If a board is missing, first check that account's permissions in monday.com.
No. You enter the fixed API address, https://api.monday.com/v2. The form only accepts addresses that start with https://api.monday.com/; the address of your own account environment does not work.
The GraphQL API. Technically the connection runs over a REST connection in Azure Data Factory that sends the token as a header, but the queries Yres puts to monday.com are GraphQL queries on the v2 address.
The token belongs to one user. So create it under an account deliberately chosen for this purpose with sufficient read access, and keep an eye on any expiry date. If you replace the token, you update it on the source in Yres.
Full technical description in the knowledge base →·Last reviewed:
Built for organisations on Azure and Power BI. Yres connects your sources, keeps the history and promotes changes in a controlled way, without manual work.