什么是 Front？

Openclaw Skills 的 Front 技能为 Front.app API 提供了强大的接口，使开发人员和支持团队无需离开终端或代理环境即可管理客户沟通。它支持从列出收件箱到标记对话和分配团队成员的所有功能，使其成为自动化客户支持和内部协作工作流的重要组成部分。

通过利用此技能，用户可以将 Front 的多渠道功能集成到更广泛的 AI 驱动的自动化技术栈中。这确保了每次互动都能得到跟踪、分类并获得高效响应，无论是通过自动回复还是团队协调努力。

下载入口:https://github.com/openclaw/skills/tree/main/skills/rdewolff/front

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

Front 应用场景

• 监控未分配的收件箱对话以实现快速响应。
• 使用电子邮件、帐号或标签搜索特定的客户历史记录。
• 通过评论为对话添加内部团队备注或上下文，以实现更好的协作。
• 自动化消息回复或创建草稿供人工审核，以维持高服务水平。
• 根据工作量、专业知识或优先级将对话分配给特定的团队成员。

1. 该技能使用用户配置中提供的安全 Bearer 令牌与 Front API 进行身份验证。
2. 用户或代理通过 front.sh 脚本执行 CLI 命令，与各种 API 端点进行交互。
3. 该技能获取对话、消息和标签等数据，或将回复和内部评论等数据发送到 Front 公司特定的 API 基址。
4. 高级过滤允许检索未分配、已分配或已归档的对话，以保持严格的收件箱整洁度。
5. 它提供实时反馈和结构化数据输出，允许在 Openclaw Skills 工作流中实现复杂逻辑。

Front 配置指南

首先，通过导航到“设置” -> “开发人员” -> “API 令牌”从 Front 获取您的 API 令牌。您可以将该令牌配置为环境变量或在本地配置文件中进行配置。

设置环境变量：

export FRONT_API_TOKEN=your_token_here

或将其添加到 ~/.clawdbot/clawdbot.json：

{
  "skills": {
    "entries": {
      "front": {
        "apiKey": "YOUR_FRONT_API_TOKEN"
      }
    }
  }
}

Front 数据架构与分类体系

Front 技能与 Front.app 生态系统中的几个核心实体进行交互。数据通常作为代表以下结构的对象返回：

name: front
description: Front.app API for managing conversations, messages, comments, and team collaboration.
homepage: https://front.com
metadata: {"clawdbot":{"emoji":"??","requires":{"bins":["curl"],"env":["FRONT_API_TOKEN"]},"primaryEnv":"FRONT_API_TOKEN"}}

Front

Use Front's API to manage conversations, read/send messages, and collaborate with team comments.

Setup

Get your API token from Front → Settings → Developers → API Tokens. Store it in ~/.clawdbot/clawdbot.json:

{
  "skills": {
    "entries": {
      "front": {
        "apiKey": "YOUR_FRONT_API_TOKEN"
      }
    }
  }
}

Or set env: FRONT_API_TOKEN=your_token

Quick Reference

List Inboxes

{baseDir}/scripts/front.sh inboxes

List Conversations

{baseDir}/scripts/front.sh conversations [inbox_id]      # Active conversations (unassigned + assigned)
{baseDir}/scripts/front.sh conversations --all           # Include archived
{baseDir}/scripts/front.sh conversations --archived      # Archived only
{baseDir}/scripts/front.sh conversations --unassigned    # Unassigned only
{baseDir}/scripts/front.sh conversations --assigned      # Assigned only
{baseDir}/scripts/front.sh conversations --limit 200     # Increase result limit (default: 100)

Get Conversation Details

{baseDir}/scripts/front.sh conversation 

List Messages in Conversation

{baseDir}/scripts/front.sh messages 

Search Conversations

{baseDir}/scripts/front.sh search "query text"
{baseDir}/scripts/front.sh search "from:client@example.com"
{baseDir}/scripts/front.sh search "tag:urgent"

Read Comments (Team Notes)

{baseDir}/scripts/front.sh comments 

Add Comment (Team Note)

{baseDir}/scripts/front.sh add-comment  "Your team note here"

Reply to Conversation

{baseDir}/scripts/front.sh reply  "Your reply message"
# With --draft flag to save as draft instead of sending:
{baseDir}/scripts/front.sh reply  "Draft message" --draft

List Teammates

{baseDir}/scripts/front.sh teammates

Assign Conversation

{baseDir}/scripts/front.sh assign  

Tag Conversation

{baseDir}/scripts/front.sh tag  

List Tags

{baseDir}/scripts/front.sh tags

Get Contact Info

{baseDir}/scripts/front.sh contact 

List Drafts

{baseDir}/scripts/front.sh drafts [inbox_id]    # Search conversations for drafts

Note: Front API doesn't have a global drafts endpoint. This command checks active conversations for draft replies.

Common Workflows

Daily inbox review:

# List unassigned open conversations
{baseDir}/scripts/front.sh conversations --unassigned --status open

Find customer conversations:

{baseDir}/scripts/front.sh search "from:customer@company.com"

Add team context:

{baseDir}/scripts/front.sh add-comment cnv_abc123 "Customer is VIP - handle with care"

Notes

• API base: Auto-detected (company-specific, e.g., https://company.api.frontapp.com)
• Auth: Bearer token in header
• Rate limit: 120 requests/minute
• Conversation IDs start with cnv_
• Inbox IDs start with inb_
• Always confirm before sending replies

API Limitations

• No global search: The /conversations/search endpoint may return 404 depending on API plan
• No global drafts: Drafts are stored per-conversation, not globally accessible
• Conversations vs Inbox: By default shows non-archived/non-deleted conversations (open, unassigned, assigned)