Reference
Look up a known identity
Telegram @username or user id → the person in this workspace's CRM and the chats you may see with them. Stored data only, no Telegram call; found=false means unknown here (use contacts.check_exists or contacts.start_chat).
View MarkdownThis page is generated from the source code on every release.
Telegram @username or user id → the person in this workspace's CRM and the chats you may see with them. Stored data only, no Telegram call; found=false means unknown here (use contacts.check_exists or contacts.start_chat).
Overview
| Name | Value |
|---|---|
| Code | contacts.resolve |
| Scope needed | crm.read |
| Risk | Read |
| May need confirmation | No |
| Runs as | Answers right away |
Needs Idempotency-Key |
No |
| Member roles allowed | owner, manager, agent, viewer |
| In the app | Inbox → New message → search box |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
username |
text |
No | |
tgUserId |
text |
No |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/contacts.resolve \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
found |
false |
Yes |
person |
null |
Yes |
conversations |
any[] |
Yes |
Example answer
{
"data": {
"ok": true,
"found": false,
"person": null,
"conversations": []
}
}Using it over MCP
Tool contacts_resolve 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.