Docs

Reference

Report a problem or idea

Report a problem or idea to the Telegram-Auto team: bug, tool_friction (confusing, too many steps, unclear error), missing_capability, docs_gap, question, improvement, praise, security or other. Use it when something blocks you or costs meaningful extra work, or once at the end of a task if something was confusing — not after every call, and not for errors you can fix yourself (validation, permissions, rate limits, waiting jobs). Who sees it: the Telegram-Auto support team and this workspace's admins. Send only technical facts: goal, what you tried, expected vs actual, operation names, error codes, trace_ids. Never include passwords, cookies, tokens, 2FA codes, customers' names, handles, phone numbers or message text: such content is rejected or masked. If the report would include the user's own business data, ask the user first. Returns ticket_id: tell the user, keep working with a safe workaround, and check replies later with feedback_get. Reporting the same problem again returns the existing ticket.

View MarkdownThis page is generated from the source code on every release.

Report a problem or idea to the Telegram-Auto team: bug, tool_friction (confusing, too many steps, unclear error), missing_capability, docs_gap, question, improvement, praise, security or other. Use it when something blocks you or costs meaningful extra work, or once at the end of a task if something was confusing — not after every call, and not for errors you can fix yourself (validation, permissions, rate limits, waiting jobs). Who sees it: the Telegram-Auto support team and this workspace's admins. Send only technical facts: goal, what you tried, expected vs actual, operation names, error codes, trace_ids. Never include passwords, cookies, tokens, 2FA codes, customers' names, handles, phone numbers or message text: such content is rejected or masked. If the report would include the user's own business data, ask the user first. Returns ticket_id: tell the user, keep working with a safe workaround, and check replies later with feedback_get. Reporting the same problem again returns the existing ticket.

Overview

Name Value
Code feedback.create
Scope needed feedback
Risk Write
May need confirmation No
Runs as Answers right away
Needs Idempotency-Key Yes
Member roles allowed owner, manager, agent, viewer
In the app Settings → AI connections → AI feedback

Input fields

Field Type Required Description
category "bug" | "tool_friction" | "missing_capability" | "docs_gap" | "question" | "improvement" | "praise" | "security" | "other" Yes
title text Yes
description text Yes
impact "blocking" | "degraded" | "minor" | "suggestion" No
expected text No
actual text No
steps_attempted text[] No
workaround text No
suggested_capability text No
related_operation text No
related_trace_ids text[] No
related_ticket_id text No
docs_url text No
agent_model text No
agent_client text No

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/feedback.create \
  -H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: <unique key per operation>" \
  -d '{"category":"bug","title":"…","description":"…"}'

Output fields (data)

Field Type Required
suggested_docs object[] Yes
visibility "product_support_and_workspace_admins" Yes
next_step "Tell the user the ticket id. Continue with a safe workaround if you can. Check replies later with feedback_get; do not file the same problem again." | "Báo mã ticket cho người dùng. Làm tiếp bằng cách vòng an toàn nếu có. Xem trả lời sau bằng feedback_get; đừng gửi lại cùng vấn đề." Yes
poll_after_seconds number Yes
dropped_related_ticket_id text No
ticket_id text Yes
status "resolved" | "new" | "triaged" | "planned" | "in_progress" | "waiting_on_reporter" | "closed" Yes
category "question" | "bug" | "tool_friction" | "missing_capability" | "docs_gap" | "improvement" | "praise" | "security" | "other" Yes
deduplicated true/false Yes
occurrences number Yes
redactions object[] Yes
dropped_trace_ids text[] Yes

Example answer

{
  "data": {
    "suggested_docs": [
      {
        "title": "text",
        "url": "text"
      }
    ],
    "visibility": "product_support_and_workspace_admins",
    "next_step": "Tell the user the ticket id. Continue with a safe workaround if you can. Check replies later with feedback_get; do not file the same problem again.",
    "poll_after_seconds": 1,
    "dropped_related_ticket_id": "00000000-0000-4000-8000-000000000000",
    "ticket_id": "00000000-0000-4000-8000-000000000000",
    "status": "resolved",
    "category": "question",
    "deduplicated": true,
    "occurrences": 1,
    "redactions": [
      {
        "field": "text",
        "kind": "text",
        "count": 1
      }
    ],
    "dropped_trace_ids": [
      "text"
    ]
  }
}

Using it over MCP

Tool feedback_create is listed on the profiles: Real-time operations (realtime), Automation setup (setup), Discover (prospecting), Reports (reports), Administration (admin), Full (full). On other profiles, find it with tools_search and run it with tools_run.

Was this page helpful?

Last checked: 10/24/2026 · build 2.0