Privacy and analytics

We use necessary technical cookies and, only with your consent, analytics and marketing pixels to improve the website and measure campaigns.

Privacy policyCookie policy
Docs
English
EspañolEnglishFrançaisDeutschItalianoPortuguês

Getting started

  • What is Nömad?
  • Getting started with Nömad
  • Create your brand and complete the Genome
  • Invite your team
  • Glossary

Brand OS

  • What is inside Brand OS
  • What is the Genome?
  • Who is Nödo?
  • What does a Brand Manager do?
  • Brand Kit and Library
  • Posts and calendar
  • Connections
  • Meetings

Work

  • Work and tasks
  • Ordering work
  • Following, reviewing and approving deliveries
  • Custom quotes
  • Yes, there are humans behind it

Account and billing

  • Plans and pricing
  • Billing and payments
  • Roles and permissions
  • Workspaces and multiple brands
  • Languages, apps and data

Help

  • How to get help

API

  • Brand API

MCP

  • MCP server

Connectors

  • Brand connectors

Nödo and agents

  • Nödo in the brand
    • Soul
    • Memory
    • Widgets
Nödo and agents/Nödo in the brand
Reference2 min read

Widgets

Interactive conversation modules.

On this page
  • Contract
  • Catalog

Updated on January 1, 1970

Previous
Русский
한국어
日本語
中文
हिन्दी
Open the app
Memory

In this section

  • Soul
  • Memory
Can't find what you need? Write to usWrite to usGo to the app
© 2026 Nömad · Nömad documentationLinkedInInstagramFacebookTikTokYouTubeX
Go to nomad.oooBack to top

On this page

  • Contract
  • Catalog

When an answer is better touched than read, Nödo returns a widget: an interactive module with typed data and actions. The same JSON renders on the web, the Apple app and Android, and outside Nömad it is served as an MCP App.

Contract

{
  "type": "widget",
  "kind": "review",
  "version": 1,
  "fallback": "Logotipo · revisión 2 espera tu aprobación.",
  "data": { "taskId": "…", "title": "Logotipo · revisión 2" },
  "actions": [
    { "id": "approve", "capability": "works.tasks.review", "confirm": true },
    { "id": "changes", "capability": "works.tasks.review" }
  ]
}
  • Every action calls a capability; the widget carries no logic of its own.
  • It always carries fallback: an app that does not know the kind or version shows that text.
  • Apps enable widgets when the server announces chat.widgets.v1.
  • No answer ratings and no payments inside widgets: buying keeps its own screen.

Catalog

KindNamePurposeFamily
recordRecordTitle, key facts, optional image and up to two actions.Base
listListRows with status and one action each; paginated.Base
carouselCarousel3 to 8 cards with an image and one action.Base
formFormShort fields: text, number, date, select.Base
choiceChoiceSingle or multiple options plus an own answer.Base
confirmConfirmSummary of what will happen, accept or cancel.Base
progressProgressLong task in progress with steps and cancel.Base
sourcesSourcesWhere the answer comes from: Genome, memory, files.Base
action_linkAction linkOpens an app screen or an external authorization.Base
file_requestFile requestRequests and uploads files to a task or the Library.Base
palettePaletteColors with role, copyable HEX and contrast.Brand
calendar_weekWeekSeven days with deliveries, posts and dates.Brand
reviewReviewDeliverable preview: approve or request changes.Brand
image_galleryGalleryGenerated images: approve or another version.Brand
managerYour Brand ManagerPerson, availability and talk to them.Brand
usagePlan limitsHow much of each plan limit is used.Brand