Learn how to query apps built with the monday.com apps framework
Using the apps framework, you can build apps on top of the monday.com platform. These apps extend the platform's core functionality by bridging gaps and enabling you to customize your workflows.
Apps can be shared directly with select accounts, listed in the app marketplace for all monday.com users, or kept private within the account. They are created and managed in the Developer Center.
Queries
You can use the app query to retrieve app data via the API.
- Returns an object containing metadata about an app
- Can be queried directly at the root or nested within a
daily_analyticsquery
query {
platform_api {
daily_analytics {
by_app {
app {
name
features {
type
name
}
id
api_app_id
state
}
usage
}
}
}
}import { ApiClient } from "@mondaydotcomorg/api";
const mondayApiClient = new ApiClient({ token: myToken });
const query = `query ($appId: ID!) { app (id: $appId) { features { id type } } }`;
const variables = {
appId: 1234567890,
};
const response = await mondayApiClient.request(query, variables);Arguments
You can use the following argument to reduce the number of results returned in your app query.
| Argument | Description |
|---|---|
id ID! | The app's unique identifier. |
Fields
You can use the following fields to specify what information your app query will return. Some fields support their own subfields.
Field | Description | Enum Values | Supported Subfields |
|---|---|---|---|
account_id | The app's account ID. | ||
api_app_id | The app's unique API consumer identifier. | ||
client_id | The app's unique API consumer identifier. | ||
collaborators | The app's collaborators. | ||
created_at | The app's creation date. | ||
created_by | The unique identifier of the user who created the app. | ||
description | The app's description. | ||
features | The app's features. | app_id | |
id | The app's unique identifier. | ||
kind | The app's kind. | ||
name | The app's name. | ||
permissions | The app's permissions. | ||
photo_url | The URL of the app's photo. | ||
photo_url_small | The URL of the app's photo in a small size. | ||
slug | The app's slug. | ||
state | The app's state (active/inactive). | ||
status | The app's status. |
| |
updated_at | The date the app was last updated. | ||
user_id | The unique identifier of the user who created the app. | ||
version_type | The app's latest version type. | ||
webhook_url | The app's webhook endpoint URL. |
Mutations
The API allows you to create and update apps using the following mutations.
Create app
The create_app mutation creates a new app via the API. You can specify which fields to return in the mutation response.
mutation {
create_app(
input: {
collaborators: [54321, 12345],
description: "The updated app description.",
name: "The updated app name.",
kind: PUBLIC,
permissions: ["docs:write", "me:read"]
}
) {
description
name
kind
permissions
collaborators {
id
}
}
}Arguments
You can use the following arguments to define the new app's characteristics.
Argument | Description | Supported Fields |
|---|---|---|
input | An object containing the new app's configuration data. | collaborators |
Update app
The update_app mutation allows an app collaborator to update an app via the API. You can specify which fields to return in the mutation response.
mutation {
update_app(
id: 123456,
input: {
collaborators: [54321, 12345],
description: "The updated app description.",
name: "The updated app name."
}
) {
description
name
collaborators {
id
}
}
} Arguments
You can use the following arguments to define the app's updated characteristics.
Argument | Description | Supported Fields |
|---|---|---|
id | The unique identifier of the app to update. | |
input | An object containing the updated app's configuration data. | collaborators |
