English
Frontline Admin · Overview · Reference

Core concepts

A compact map of the Frontline concepts you need before building agents, workflows, integrations, or data models.

Reference4 min
Concept map

Core pieces for building in Frontline.

Read this like an operating glossary: what each thing is, what it is for, and where to go deeper.

Agents

Conversational behavior and reasoning.

  • AgentAn AI teammate with a role, instructions, tools, channels, and handoff rules.
  • FlowA conversation path that structures questions, responses, and captured data.
  • Flow VariableTemporary data captured inside a flow.
  • IntentClassification of what the user wants so the conversation can route correctly.

Workflows

Repeatable processes and automation.

  • WorkflowA sequence with triggers, conditions, actions, messages, logs, and handoff.
  • Workflow VariableData carried through one workflow run.
  • ToolA reusable action an agent or workflow can call.
  • Incoming WebhookA URL that lets an external system start a workflow.

Data

Structured memory and operational data.

  • ObjectA CRM entity: people, companies, deals, tickets, or custom models.
  • Record TypeAn object variant for processes that share structure.
  • TableSpreadsheet-style data for rules, catalogs, imports, or reference.

Core

Cross-cutting capabilities and developer access.

  • AI ModelThe model used to reason, generate, classify, extract, or transcribe.
  • Public APIProgrammatic access to supported resources from external systems.
  • CLITerminal commands for scripts, profiles, JSON output, and developer work.

How to use this map

Use this map when you are not sure where to build something. Start with the job: customer conversation, repeatable process, CRM/data model, or external integration.

Then choose the owner: Agents and Flows handle conversations; Workflows run processes; Objects and Tables hold data; Tools, Webhooks, API, and CLI connect systems.

Simple rule

If it behaves like a teammate, it is an Agent. If it guides a step-by-step customer conversation, it is a Flow. If it has triggers, conditions, actions, and logs, it is a Workflow. If it is persistent business data, use Objects or Tables. If it crosses system boundaries, use Tools, Webhooks, API, or CLI.

Transcript

Open searchable transcript
Core concepts helps you choose where to build: Agents and Flows for conversations, Workflows for processes, Objects and Tables for data, and Tools, Webhooks, API, or CLI for external connections.