Use the Front CLI from KosmoKrator to call Front tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
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 --jsonkosmokrator integrations:doctor front --jsonkosmokrator integrations:status --json
Credentials
Authentication type: Bearer tokenbearer_token. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
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.
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.
List and search conversations in Front. Filter by status or search by keyword. Returns paginated results with conversation IDs, subjects, and metadata.
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.
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.