erxes Skill — erxes 技能

erxes– Чадварууд 记录in

Use scripts/记录in.sh for authentication.

ERXES_BASE_URL= ERXES_命令行工具ENT_ID=${ERXES_命令行工具ENT_ID:-erxes-local} bash scripts/记录in.sh

ERXES_BASE_URL is required. ERXES_命令行工具ENT_ID is optional. Default to erxes-local. Accept the URL in whatever form the user gives and normalize it to ERXES_BASE_URL=. Do not explAIn OAuth internals unless the user asks. Do not ask the user to copy 令牌s manually. Do not store 令牌s in project files. The script opens the browser, wAIts for 应用roval, and prints a 会话 JSON payload to stdout.

Read erxes-应用-令牌-auth.md only when you need the quick 记录in reference.

API calls

After 记录in, use the returned 会话 payload directly.

Read 访问令牌 from the 记录in JSON 响应. 发送 Authorization: Bearer <访问令牌> and erxes-subdomAIn: headers on GraphQL calls. If the 访问 令牌 expires during the current task, use the in-memory refresh令牌 to 获取 a new 访问 令牌. Do not write 令牌s to .auth.json or any other project file. Read erxes-graphql-API.md only when you need 查询 or mutation examples. Assume OpenClaw is operating as the erxes owner unless the live API proves otherwise. Do not 停止 a normal 工作流 just because the backend source defines 权限 names. Treat those as implementation detAIl, not a user-facing blocker. Safe Action Rules Read, 列出, 搜索, 过滤器, group, and summarize can 运行 directly. If the user asks to group 结果s, fetch the matching 列出 first and group the returned records in the 响应. For 创建 or 更新, if the tar获取 record or required fields are unclear, summarize the planned change and ask only for the missing in格式化ion. For 删除, 移除, deactivate, publish, unpublish, end, transfer, or convert actions, always identify the exact record and ask for explicit confirmation before 发送ing the mutation. Never print 访问令牌, refresh令牌, raw 会话 JSON, or auth headers. Keep the auth 会话 in memory only for the current task. Assume owner-mode 访问 for discovered 工作流s. Only mention 访问 problems if the live API actually rejects the 请求. Follow-Up Rules If the user gives a name but not an _id, 搜索 first, show the likely matches, then ask which record should be used. If the 工作流 depends on team, project, 状态, milestone, cycle, building, zoning, or unit IDs, fetch the choices first instead of guessing. Ask only for fields that are still missing. Warn before risky mutations: block删除Building fAIls if the building still has zonings. block删除BuildingZoning fAIls if the zoning still has units. block更新Unit can fAIl if the unit already has a 签名ed contract. blockOpptyConvertToContract needs 机器人h a tar获取 unit and a payment plan. operationConvertTria获取oTask may need a valid team-specific 状态 type. Харилцагч Бүх харилцагчийн жагсаалт харах Нэр, имэйл, утсаар хайх Харилцагчийн дэлгэрэнгүй мэдээлэл харах Төрлөөр нь бүлэглэх (үйлчлүүлэгч / боломжит / зочин) Шинэ харилцагч нэмэх Харилцагчийн мэдээлэл засах Харилцагч устгах Давхардсан харилцагчийг нэгтгэх Бүтээгдэхүүн Бүтээгдэхүүний жагсаалт харах Нэг бүтээгдэхүүний дэлгэрэнгүй харах Шинэ бүтээгдэхүүн нэмэх Бүтээгдэхүүн засах, устгах, нэгтгэх Ангилал болон хэмжих нэгж удирдах Шошго Бүх шошго харах Шошго нэмэх, засах, устгах Харилцагч эсвэл бүтээгдэхүүнд шошго хавсаргах Баримт бичиг Баримт бичгийн жагсаалт харах Баримт бичиг нэмэх, засах, устгах Брэнд Брэндийн жагсаалт харах Брэнд нэмэх, засах, устгах Автоматжуулалт Бүх автоматжуулалтын жагсаалт харах Автоматжуулалт нэмэх, засах, идэвхжүүлэх, устгах Байгууллагын бүтэц Хэлтэс, салбар, нэгж, албан тушаалын бүтэц харах Хэлтэс, салбар, нэгж, тушаал нэмэх, засах, устгах Багийн гишүүд Гишүүдийн жагсаалт харах Шинэ гишүүн урих Гишүүний мэдээлэл засах Гишүүнийг идэвхгүй болгох Block 插件 Use block-API.md when the user wants help with block-side SaaS 工作流s such as projects, buildings, floor zonings, units, unit types, opportunities, 状态es, payment plans, contracts, offers, invoices, documents, attachments, notes, or the developer 性能分析. Natural language examples: "Show me all blocks grouped by 状态" "创建 a new block with these detAIls" "Find all units in this building" "Move this opportunity to another 状态" "创建 a payment plan for this project" Read and 列出 actions can 运行 directly. 创建 and 更新 actions should summarize the planned write first when 导入ant fields are ambiguous. 删除, publish, unpublish, transfer, and convert actions must always ask for confirmation first. Operation 插件 Use operation-API.md when the user wants help with operation-side SaaS 工作流s such as projects, tasks, triage, teams, 状态es, cycles, milestones, notes, activities, and templates. Natural language examples: "Show me active projects" "Find tasks with no as签名ee" "创建 a triage item for this team" "Convert this triage item to a task" "Summarize milestone 进度" Read and 列出 actions can 运行 directly. 创建 and 更新 actions should sum