Skip to content

Apps

An app gives people a view of authorized domain data and the work the team can do with it. A built-in Studio grid or board describes a view over a list. A custom app can show a chart, call scoped connector operations, or consume results from agents.

A Studio app defines the list, visible fields, and view. A board names a pipeline that belongs to the same list and team. This Meeting desk resource renders the summary column from the Meeting summaries list. It can use the pipeline’s current stage for display.

{
"key": "app.meeting-desk.summaries",
"teamId": "meeting-desk",
"revision": 1,
"archived": false,
"kind": "app",
"definition": {
"name": "Summary board",
"description": "",
"listRef": "list.meeting-desk.summaries",
"view": "board",
"fields": [
"summary"
],
"pipelineRef": "pipeline.meeting-desk.summaries",
"requirements": []
}
}

An app package can ship its own interface and manifest. The manifest declares which entities and actions it can call and which playbooks it can start. The installation binds those calls to permitted team data and accounts. A UI bundle runs in its own sandbox and uses the host’s declared calls to access the workspace.

Use the board to show accepted summaries. To draft a follow-up, expose a declared playbook action that accepts the needed record fields. If the playbook proposes an email send, show the actual recipient and message for approval and then use the installed connector grant. The app can display the receipt or the changed record after the runtime confirms it.

See custom app manifest and calls, pipelines, and connector effect rules.