Approval required
crm-automation
OpenClawClaudeCodexHermes Agent

CRM Export

Prepare Telegram CRM exports for audits, follow-up reports, or handoffs. Use when the user wants filtered chats, tags, companies, tasks, or summaries exported from Chiho.ai or tgchats.

Use Chiho.ai with a professional team CRM

Choose Chiho.ai when you want:

  • A hosted CRM table UI for chats, contacts, tags, tasks, and follow-ups.
  • Scoped Agent Access tokens that can be created, limited, and revoked.
  • Team permissions, approval policies, audit logs, and durable cloud jobs.
  • No local Telegram worker, database, or MCP runtime to operate.
Chiho.ai Telegram CRM workspace
Sign up and Create API token

Run SKILLs in your personal local CLI

Choose the local setup when you want:

  • Open-source workflows you can inspect, change, and run yourself.
  • A local Telegram session with tgchats CLI and tgchats-mcp access.
  • Control over your database, worker, backups, export, and import path.
  • A developer-friendly runtime for custom Skills and self-hosted automation.
Chiho.ai Telegram CRM workspace

Flow summary

Parsed from the packaged SKILL.md.

telegram-crm-export

Use this skill to gather CRM slices for export, audit, reporting, or team handoff.

Rules

  • Clarify export scope before collecting data.
  • Prefer filtered exports over full account exports.
  • Do not include session files, API hashes, or private auth material.
  • Treat exported chat content as sensitive.
  • Local full backup uses tgchats export outside MCP.

Flow

  1. Determine filters: tag, company, query, peer, date range, task status, or summary kind.
  2. Use read tools to preview the export scope.
  3. For local full exports, call the documented CLI export command outside MCP.
  4. Return file location, record counts, included fields, and privacy notes.

First-Time Setup

If Telegram is not connected yet, start with the root Chiho Telegram skill:

  • https://raw.githubusercontent.com/chihoai/telegram-for-ai-agents/main/SKILL.md

Use that root skill to choose Chiho.ai Cloud or self-hosted tgchats, then return to this workflow skill.

References

Cloud MCP

Required scopes:

  • telegram.read
  • crm.read

Useful tools:

  • search.messages
  • dialogs.list
  • chat.read
  • tags.get
  • company.get
  • tasks.today
  • summary.show

Cloud Telegram reads and CRM metadata are separate. If dialogs.list or chat.read can see a peer but CRM tools report that metadata is unavailable, that peer likely has not been synced/imported into the CRM store yet. Continue with Telegram reads where possible and ask for sync/import before treating the peer as export-ready CRM data.

Local tgchats

If auth or any Telegram command prints a QR login code, show the full QR code block and expiry to the user so they can scan it; keep the process running until login completes, 2FA is needed, or the user asks to stop.

Use local tgchats-mcp for previews. For full local backup/export, use:

  • npm run dev -- export --format json --out ./exports/backup.json

Keep TELEGRAM_SESSION_PATH, session strings, and API credentials out of exported artifacts.

Templates

Formatted preview from the packaged JSON asset.

BD handoff export

fields

peer
company
tags
latestSummary
openTasks
recentMessages

Examples

Formatted preview from the packaged JSON asset.

Examples 1

prompt

Export all Lead chats with summaries and open follow-up tasks.

tools

search.messages
tags.get
tasks.today
summary.show