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

# Actions

> Your APIs are the actions - call them mid-conversation, or push every outcome to the systems that act on it.

An agent that only talks is half an app. Actions are how a conversation
changes something: a booking held, a lead created, a row updated, a ticket
opened. In Unpod your own APIs are the actions. The agent calls them
mid-conversation, and every outcome is pushed to the systems that act on it
after the call.

## The primitives

| Primitive | What it is | Where it lives today |
| - | - | - |
| In-call actions | HTTP tools the agent calls mid-conversation | Production - [playbook tools](https://docs.unpod.ai/superdialog/tools.md), or Agent Studio → Persona → Tools |
| After-call actions | The post-call webhook delivers the transcript and structured outcome to your endpoint | Production - [post-call data](https://docs.unpod.ai/api/post-call-data.md) |
| Google Sheets sync | Two-way: each call's row lands in the sheet, and a new row triggers a call | Production - Agent Studio → Integration → Google Sheet Sync |
| In-call SMS | A template SMS sent during the call, to Indian numbers | Production, narrow |
| Ready-made connectors | CRM, payment, booking and helpdesk connectors | Not yet - use an in-call HTTP tool or the post-call webhook |

```yaml playbook.yaml (excerpt) theme={null}
tools:
  - id: create_lead
    type: http
    method: POST
    url: "{{ env.CRM_BASE_URL }}/leads"
    headers: {Authorization: "Bearer {{ env.CRM_TOKEN }}"}
    body: {name: "{{ slots.name }}", budget: "{{ slots.budget }}"}
    store_response_as: lead
    run_once: true
```

## On the spine

An action is part of the interaction that ran it. An in-call tool's result
is recorded on the interaction, and the outcome that reaches your webhook is
the same outcome the [Context Engine](https://docs.unpod.ai/core-engine/context-engine.md) keeps.

## What stays hidden

Delivery mechanics: webhook retries and redelivery, Sheets polling, and SMS
carrier routing.

## Status

**Production:** HTTP tools, the post-call webhook, two-way Google Sheets
sync, and in-call SMS. **In build:** a helpdesk connector for messaging
journeys. **Not yet:** ready-made CRM, payment and booking connectors.

## Go deeper

> **[Tools](https://docs.unpod.ai/superdialog/tools.md)**
>
> Declare HTTP tools in a playbook.

> **[Post-call data](https://docs.unpod.ai/api/post-call-data.md)**
>
> The payload your webhook receives.

> **[Agent Harness](https://docs.unpod.ai/core-engine/agent-harness.md)**
>
> Retries and fallbacks around every tool call.

> **[Flows & Journeys](https://docs.unpod.ai/core-engine/flows-journeys.md)**
>
> Workflows that decide which action comes next.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.