KosmoKrator

communication

Front CLI for AI Agents

Use the Front CLI from KosmoKrator to call Front tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

7 functions 6 read 1 write Bearer token auth

Front CLI Setup

Front can be configured headlessly with `kosmokrator integrations:configure front`.

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure front --set access_token="$FRONT_ACCESS_TOKEN" --enable --read allow --write ask --json
kosmokrator integrations:doctor front --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then use the same stored profile from scripts, coding CLIs, Lua code mode, and the MCP gateway.

KeyEnv varTypeRequiredLabel
access_token FRONT_ACCESS_TOKEN Secret secret yes Access Token
url FRONT_URL URL url no API Base URL

Call Front Headlessly

Use the generic call form when another coding CLI or script needs a stable universal interface.

kosmo integrations:call front.front_get_contact '{
  "id": "example_id"
}' --json

Use the provider shortcut form for shorter human-facing commands.

kosmo integrations:front front_get_contact '{
  "id": "example_id"
}' --json

Agent Discovery Commands

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

kosmo integrations:docs front --json
kosmo integrations:docs front.front_get_contact --json
kosmo integrations:schema front.front_get_contact --json
kosmo integrations:search "Front" --json
kosmo integrations:list --json

All CLI Functions

Every function below can be called headlessly. The generic form is stable across all integrations; the provider shortcut is shorter but specific to Front.

front.front_get_contact

Read read

Get details of a specific Front contact by ID, including name, emails, phone numbers, and custom fields.

Parameters
id

Generic CLI call

kosmo integrations:call front.front_get_contact '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:front front_get_contact '{"id":"example_id"}' --json

front.front_get_conversation

Read read

Get details of a specific Front conversation by ID, including subject, participants, status, tags, and metadata.

Parameters
id

Generic CLI call

kosmo integrations:call front.front_get_conversation '{"id":"example_id"}' --json

Provider shortcut

kosmo integrations:front front_get_conversation '{"id":"example_id"}' --json

front.front_get_current_user

Read read

Get the profile of the currently authenticated Front user. Returns name, email, and account details.

Parameters
none

Generic CLI call

kosmo integrations:call front.front_get_current_user '{}' --json

Provider shortcut

kosmo integrations:front front_get_current_user '{}' --json

front.front_list_contacts

Read read

List and search contacts in Front. Search by name, email, or other identifiers. Returns paginated contact details.

Parameters
page, limit, q

Generic CLI call

kosmo integrations:call front.front_list_contacts '{"page":1,"limit":1,"q":"example_q"}' --json

Provider shortcut

kosmo integrations:front front_list_contacts '{"page":1,"limit":1,"q":"example_q"}' --json

front.front_list_conversations

Read read

List and search conversations in Front. Filter by status or search by keyword. Returns paginated results with conversation IDs, subjects, and metadata.

Parameters
page, limit, status, q

Generic CLI call

kosmo integrations:call front.front_list_conversations '{"page":1,"limit":1,"status":"example_status","q":"example_q"}' --json

Provider shortcut

kosmo integrations:front front_list_conversations '{"page":1,"limit":1,"status":"example_status","q":"example_q"}' --json

front.front_list_messages

Read read

List all messages in a Front conversation. Returns paginated message details including sender, body, and timestamps.

Parameters
conversation_id, limit, page

Generic CLI call

kosmo integrations:call front.front_list_messages '{"conversation_id":"example_conversation_id","limit":1,"page":1}' --json

Provider shortcut

kosmo integrations:front front_list_messages '{"conversation_id":"example_conversation_id","limit":1,"page":1}' --json

front.front_send_message

Write write

Send a reply message to an existing Front conversation. Supports HTML and plain-text bodies, and explicit TO/CC recipients.

Parameters
conversation_id, body, text, to, cc

Generic CLI call

kosmo integrations:call front.front_send_message '{"conversation_id":"example_conversation_id","body":"example_body","text":"example_text","to":"example_to","cc":"example_cc"}' --json

Provider shortcut

kosmo integrations:front front_send_message '{"conversation_id":"example_conversation_id","body":"example_body","text":"example_text","to":"example_to","cc":"example_cc"}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

front.front_get_contact

Get details of a specific Front contact by ID, including name, emails, phone numbers, and custom fields.

Operation
Read read
Schema command
kosmo integrations:schema front.front_get_contact --json
ParameterTypeRequiredDescription
id string yes The contact ID (e.g., "crd_123abc").

front.front_get_conversation

Get details of a specific Front conversation by ID, including subject, participants, status, tags, and metadata.

Operation
Read read
Schema command
kosmo integrations:schema front.front_get_conversation --json
ParameterTypeRequiredDescription
id string yes The conversation ID (e.g., "cnv_123abc").

front.front_get_current_user

Get the profile of the currently authenticated Front user. Returns name, email, and account details.

Operation
Read read
Schema command
kosmo integrations:schema front.front_get_current_user --json
ParameterTypeRequiredDescription
No parameters.

front.front_list_contacts

List and search contacts in Front. Search by name, email, or other identifiers. Returns paginated contact details.

Operation
Read read
Schema command
kosmo integrations:schema front.front_list_contacts --json
ParameterTypeRequiredDescription
page integer no Page number for pagination (1-based).
limit integer no Number of contacts per page (max 100).
q string no Search query to filter contacts by name, email, or other identifiers.

front.front_list_conversations

List and search conversations in Front. Filter by status or search by keyword. Returns paginated results with conversation IDs, subjects, and metadata.

Operation
Read read
Schema command
kosmo integrations:schema front.front_list_conversations --json
ParameterTypeRequiredDescription
page integer no Page number for pagination (1-based).
limit integer no Number of conversations per page (max 100).
status string no Filter by conversation status: open, archived, assigned, unassigned, starred, snoozed.
q string no Search query to filter conversations by subject, content, or contact.

front.front_list_messages

List all messages in a Front conversation. Returns paginated message details including sender, body, and timestamps.

Operation
Read read
Schema command
kosmo integrations:schema front.front_list_messages --json
ParameterTypeRequiredDescription
conversation_id string yes The conversation ID (e.g., "cnv_123abc").
limit integer no Number of messages per page (max 100).
page integer no Page number for pagination (1-based).

front.front_send_message

Send a reply message to an existing Front conversation. Supports HTML and plain-text bodies, and explicit TO/CC recipients.

Operation
Write write
Schema command
kosmo integrations:schema front.front_send_message --json
ParameterTypeRequiredDescription
conversation_id string yes The conversation ID to reply to (e.g., "cnv_123abc").
body string yes HTML body of the message.
text string no Plain-text version of the message body.
to array no Array of recipient objects, each with a "handle" key. Example: [{"handle": "[email protected]"}].
cc array no Array of CC recipient objects, each with a "handle" key. Example: [{"handle": "[email protected]"}].

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.