> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getdialed.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> Workflow automation for contact center operations

GetDialed is a workflow automation platform built for contact center operations. You describe a workflow — a **Flow Definition** — as a series of steps and tasks, and GetDialed executes it durably: retries, scheduling, batching, and fan-out are handled by the platform's durable-execution engine.

## What you can build

* **Data pipelines into your dialer** — upload a file of contacts and have each row flow through enrichment, validation, and delivery into a Five9 dialing list.
* **Scheduled operations** — run a report every morning, sync lists nightly, or pace outbound work through a business-hours window.
* **Event-driven processes** — trigger a flow per API call, wait on external signals, and branch on conditions evaluated against live data.

## How it fits together

<Steps>
  <Step title="Define">
    Create a **Flow Definition**: inputs, variables, and steps. Each step contains tasks that call actions from the integration catalog (e.g. Five9 list operations).
  </Step>

  <Step title="Trigger">
    Fire the definition with a single record or thousands — via the REST API or on a recurring schedule.
  </Step>

  <Step title="Execute">
    Each trigger creates a **Job**; each record becomes an **Execution** — one durable workflow run with its own status, result, and error trail.
  </Step>

  <Step title="Observe">
    Query jobs and executions through the API to track progress, aggregate outcomes, and retrieve results.
  </Step>
</Steps>

## Start here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Create and trigger your first flow in a few minutes.
  </Card>

  <Card title="Core Concepts" icon="book-open" href="/concepts/architecture">
    Definitions, jobs, executions, and how the pieces connect.
  </Card>

  <Card title="Expressions" icon="code" href="/concepts/expressions">
    Bind data between steps with the expression language.
  </Card>

  <Card title="API Reference" icon="square-terminal" href="/api-reference/introduction">
    Every endpoint, with a live playground.
  </Card>
</CardGroup>