Seat-based app recommendations are now once again based on an account's monday.com plan size, rather than the number of active users. This change comes after we received user and developer feedback about earlier updates that would only count the account's number of active users.
You can use the new apps_monetization_info object to retrieve the correct number of seats an account has.
All app and sales analytics widgets now list the last updated date in the top-right corner to help provide you with more detailed and insightful analytics! This date signifies the last time the data was refreshed.
We are announcing the marketplace revenue sharing program!
The revenue sharing program, scheduled to launch on September 1st, 2024, is structured to support our partners’ growth and incentivize the development of high-quality apps.
How will it work?
Once an app reaches the milestone of $200,000 in lifetime accumulated revenue*, the revenue sharing model is activated.
For every subsequent month, 85% of the revenue generated by the app will go to the developer and 15% of the revenue will be collected by monday.com
For instance, if an app makes $10,000 in a month post the milestone, the app builders will keep $8,500, and monday.com will collect $1,500.
This model has been carefully crafted to ensure that our developers are supported as they scale, and to reflect our shared success. This will ensure our overall growth that will continue to amplify the reach of your apps and help you thrive. Read more about it here.
*Accumulated revenue refers to the total amount of revenue generated by a product, service, or entity over its entire existence.
We just added the runtimeMetadata property to the action execution body. It contains two new attributes:
actionUuid: A UUID representing the execution of an action.
triggerUuid: A UUID representing the execution of an entire automation (same as the activity log's run ID). If one action is used multiple times in a recipe, they will all have the same triggerUuid.
{
"payload": {
"blockKind": "action",
"inboundFieldValues": {
"boardId": 1234567890,
"columnId": "text"
"itemId": 9876543210
},
"inputFields": { // input fields are based on the input fields configuration of your action and depend on the field type
"boardId": 1234567890,
"itemId": 9876543210,
"columnId": "text"
},
"recipeId": 123456, //unique ID of the recipe for your app. if multiple accounts are using the same recipe, the same recipe ID will be sent
"integrationId": 123456 //unique ID of the integration recipe added to your board
},
"runtimeMetadata": {
"actionUuid": "a6676dzce11zd50b25c4871417e1zez1", // uuid that represents the execution of the action
"triggerUuid": "z607d55cc428bb438ba02cbbcde6a25e" // uuid that represents the execution of the entire automation (same as run id in the activity log)
}
}
We recently added the secretsManager to read secrets for your app in a deployed monday-code project through the get and getKeys methods. These methods only allow you to read secrets, but you can set them through the monday code section of the Developer Center UI!
Starting July 1st, 2024, new marketplace apps must be monetized through monday, and we will no longer approve those that utilize an external monetization system.
Our monetization handles the entire payment and billing process, ultimately giving you more time to focus on building and improving your app. We are constantly upgrading our native capabilities and are committed to continued efforts to improve them.
This change does not affect existing apps, and it will be applicable to new apps submitted after the effective date.
To increase app security, we will remove the allow-top-navigation and allow-top-navigation-by-user-activation directives from iframes on June 1st, 2024.
These directives enable apps to redirect customers from their monday account to another website, which poses a security risk for many customers.
Here are good and bad examples of what’s currently allowed:
// Open link in a new tab - GOOD
window.open("<https://www.mozilla.org/">, "mozillaTab");
// Open link in a new window - GOOD
window.open("<https://www.mozilla.org/",'name','height=300,width=650,screenX=400,screenY=350'>)
// Redirect the user outside of monday - BAD
window.top.location.href = "<https://www.mozilla.org/">;
After deprecating these directives, any links utilizing this functionality won’t work but won’t impact app functionality. This update will only disablewindow.top.location.href (see example below):
If you need to direct customers to an external link from the app, you can still do so by opening it in a new tab using the SDK or the window.open method.