Skip to content
Corlecti Map
Open the app

Recipes

Four things people actually build once they have decided to use Corlecti Map as more than a browser tab: a bot under their own name, letting somebody else into it, an agent scoped to one part of a map, and a system of their own writing into it.

Your own Telegram bot under your own name

What you get. A bot separate from Corlecti Map's own shared one — your own name, your own picture — that is both a capture channel and a full conversation with the agent, sharing its transcript with the browser: ask it something on the way home, and the conversation is on the map when you open it. Every message that is plain text or a voice note becomes a block; a voice note is transcribed first.

Limits, Free · Pro · Workspace:

Bots of your own          1 · 5 · unlimited

Steps:

  1. Create a bot with @BotFather on Telegram and copy

the token it gives you.

  1. In Corlecti Map, open Settings → Telegram and paste the token. It is

encrypted at rest.

  1. Point the bot at one map, or leave it reading all of yours — a card on the

same settings screen decides which.

  1. Message it. The first message from a chat claims that bot for the account

that registered it.

Commands, once connected:

/map <name>       write into this map instead
/inbox            sugar for /map Inbox
/last             the most recent block on the current map, with a link
/where            which map this bot writes to
/scenario         the interviews this account can run
/scenario <slug>  start (or resume) that interview
/continue         resume the run on this map, from the step it left off
/stop             pause the run — capture keeps working
/reminders on|off opt in or out of the bot writing to you first (below)
/clear            ask what a full reset of this chat would erase
/help             the command list

Anything else — a plain line, or a voice note — becomes a block on whichever map this chat currently points at. A photo, a file or a sticker gets an honest "not yet" and creates nothing; a voice note is the one attachment the bot does read, and it always transcribes it.

Coming: the bot writing to you first. It will pick two blocks that look related and are not connected, and ask — answering will draw the link, at no cost to your allowance. /reminders off already opts a chat out for the day this starts; nothing sends a question on the live deploy yet.

Guests — letting other people write to your bot

What you get. Somebody without a Corlecti account can add material to one of your maps through your own bot, in one of two ways: invited by their Telegram handle, or let in for a stretch of time with no name asked at all. Either way, what they write spends your allowance — that is what a guest is paying for.

Limits, Free · Pro · Workspace:

People who may write to your bot     — · 5 · 5

On Free the limit is zero, so inviting a guest refuses in your own settings, in front of you — nobody who writes to the bot is left waiting on a silent refusal.

Steps — inviting somebody by name:

  1. Settings → Telegram, on your bot's card, add their Telegram handle.
  2. They message the bot; their first message is matched to the invitation and

accepted from then on.

Steps — the door, for somebody with no Telegram handle to invite:

  1. On the same card, open "the door": choose how many people (1–25) and for

how long (15 minutes up to a week).

  1. Anyone who messages the bot while it is open is let in as a guest, up to

the seat count; the door then closes itself.

A key seated on one branch

Coming. A single MCP key or Telegram bot will be narrowable to one branch of a map — one block and everything hanging under it — rather than the whole map, so several assistants would each hold their own scoped piece of the same map without being able to touch each other's. Seating will be chosen once, when the key or bot is created, and will not be movable afterwards.

What already works today: narrow a key to one whole map — see the MCP page's "Narrowing a key" section — which is the right tool now for keeping one assistant off maps that are not its concern.

Building your own thing on top

What you get. A system of your own — a website's contact form, a support inbox, a script that watches an RSS feed — filing what it finds straight into one of your maps, through the same MCP surface an assistant uses.

Worked example: a website that files leads into a map.

  1. In Corlecti Map, create (or choose) the map leads should land on.
  2. Settings → MCP Server → mint a key narrowed to that one map. Your

server never needs to know the map's id — the key already carries it.

  1. On each form submission, your server calls apply_map with the lead as one

node:

{
  "name": "apply_map",
  "arguments": {
    "boardId": "the-map-this-key-is-narrowed-to",
    "document": {
      "version": "mmap.v1",
      "kind": "fragment",
      "nodes": [
        {
          "ref": "lead1",
          "title": "Jane Doe — [email protected]",
          "content": "Interested in the Workspace plan. Submitted via the contact form."
        }
      ],
      "edges": []
    }
  }
}
  1. Send an Idempotency-Key header built from your own form-submission id, so

a retried request after a dropped connection cannot file the same lead twice.

  1. Read the map back with get_board — or open it in the app — to triage,

tag or connect what came in.

The key never grants more than the one map it was narrowed to: a bug in your own server cannot reach anything else in your account. See The .mmap format for every field apply_map accepts, and Limits for the MCP call quota this recipe runs against.