Auto-Processing

Overview

Auto-Processing lets you automatically transcribe recordings when they’re uploaded, and optionally generate summaries when transcription completes — without any additional API calls. Benefits:

Zero-code processing pipeline — upload once, get transcription and summary automatically
Configurable per organization, project, end user, or device
Choose your preferred ASR provider and LLM provider at each level
Non-blocking — auto-processing errors never fail the upload

Use Cases:

Medical clinics: Upload recording → auto-transcribe → auto-generate SOAP notes
Sales teams: Upload call recording → auto-transcribe → auto-generate deal summary
Legal firms: Upload consultation → auto-transcribe → auto-generate legal memo
Enterprise: Upload meeting → auto-transcribe → auto-generate meeting notes

Quick Start

Enable auto-processing for an entire project with a single API call:

curl -X PUT https://api.bota.dev/v1/projects/proj_xxx/config/processing \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "auto_transcription": {
      "enabled": true
    },
    "auto_summary": {
      "enabled": true,
      "template": "general_notes"
    }
  }'

Now every recording uploaded in this project will be automatically transcribed and summarized.

How It Works

Processing Flow

Recording upload completes — your app calls POST /v1/recordings/:id/upload-complete
Auto-transcription check — the system resolves the processing config for the recording’s device/end_user/project
If enabled — a transcription job is queued automatically (same as calling POST /v1/recordings/:id/transcribe)
Transcription completes — the worker checks the same config for auto-summary settings
If enabled — a summary job is queued automatically (same as calling POST /v1/summaries)
Webhooks fire — transcription.completed and summary.completed events are sent as usual

Config Resolution

The system determines which processing settings to apply based on the recording’s context: This means you can set different processing rules at each level. See Hierarchical Configuration for details on how inheritance works.

Error Handling

Auto-processing is non-blocking. If auto-transcription or auto-summary fails:

The upload still completes successfully
The error is logged but does not affect the parent operation
You can always retry manually via the API

Auto-processing requires that the relevant AI provider API keys are configured. If you’re using user-provided API keys, they will be used automatically. Otherwise, the system falls back to Bota’s default keys.

Configuration

Processing Config Schema

{
  "processing": {
    "auto_transcription": {
      "enabled": false,
      "provider": "whisper"
    },
    "auto_summary": {
      "enabled": false,
      "provider": "gemini",
      "template": "general_notes"
    }
  }
}

Auto-Transcription Settings

Field	Type	Default	Description
`enabled`	boolean	`false`	Enable automatic transcription on upload
`provider`	string	System default	ASR provider to use

Available ASR Providers:

Provider	Description
`whisper`	OpenAI Whisper (default) — 99 languages, word timestamps
`deepgram`	Deepgram Nova-2 — real-time capable, speaker diarization
`assemblyai`	AssemblyAI — Best/Nano models
`elevenlabs`	ElevenLabs — high accuracy, language detection

Auto-Summary Settings

Field	Type	Default	Description
`enabled`	boolean	`false`	Enable automatic summary after transcription
`provider`	string	System default	LLM provider to use
`template`	string	`general_notes`	Summary template

Available LLM Providers:

Provider	Description
`gemini`	Google Gemini 2.0 Flash (default) — JSON output
`openai`	OpenAI GPT-4o — JSON mode
`claude`	Anthropic Claude Sonnet 4 — structured output

Available Templates:

Template	Industry	Output
`general_notes`	General meetings	Key points, action items, decisions
`sales_call`	Sales	Pain points, budget, timeline, next steps
`clinical_soap`	Healthcare	SOAP notes (Subjective, Objective, Assessment, Plan)
`legal_memo`	Legal	Facts, issues, analysis, conclusion

Setting Config at Different Levels

Auto-processing uses the hierarchical configuration system, so you can set it at any level.

Project Level

Apply to all recordings in a project:

curl -X PUT https://api.bota.dev/v1/projects/proj_xxx/config/processing \
  -H "Authorization: Bearer sk_live_..." \
  -d '{
    "auto_transcription": { "enabled": true, "provider": "whisper" },
    "auto_summary": { "enabled": true, "template": "sales_call" }
  }'

End User Level

Override for a specific end user (e.g., a clinician who needs SOAP notes):

curl -X PUT https://api.bota.dev/v1/end-users/eu_drsmith/config/processing \
  -H "Authorization: Bearer sk_live_..." \
  -d '{
    "auto_summary": { "template": "clinical_soap" }
  }'

You only need to specify the fields you want to override. Dr. Smith’s recordings will still inherit auto_transcription and auto_summary.enabled from the project level — only the template changes.

Device Level

Override for a specific device:

curl -X PUT https://api.bota.dev/v1/devices/dev_abc123/config/processing \
  -H "Authorization: Bearer sk_live_..." \
  -d '{
    "auto_transcription": { "provider": "deepgram" }
  }'

Disable for a Specific Entity

Disable auto-processing at a lower level even if the parent has it enabled:

# Project has auto-transcription enabled, but disable for this device
curl -X PUT https://api.bota.dev/v1/devices/dev_abc123/config/processing \
  -H "Authorization: Bearer sk_live_..." \
  -d '{
    "auto_transcription": { "enabled": false }
  }'

Remove Override (Revert to Inherited)

Delete the processing override to revert to the parent’s settings:

curl -X DELETE https://api.bota.dev/v1/devices/dev_abc123/config/processing \
  -H "Authorization: Bearer sk_live_..."

Monitoring

Webhook Events

Auto-processing triggers the same webhook events as manual processing:

Event	Trigger
`transcription.started`	Auto-transcription job begins
`transcription.completed`	Auto-transcription finished
`transcription.failed`	Auto-transcription failed
`summary.started`	Auto-summary job begins
`summary.completed`	Auto-summary finished
`summary.failed`	Auto-summary failed

Subscribe to these events to track processing status. See Webhook Events for payload details.

Checking Results

After auto-processing completes, retrieve results the same way as manual processing:

# Get transcription for a recording
curl https://api.bota.dev/v1/transcriptions/txn_abc123 \
  -H "Authorization: Bearer sk_live_..."

# Get summary
curl https://api.bota.dev/v1/summaries/sum_abc123 \
  -H "Authorization: Bearer sk_live_..."

Verifying Current Config

Check the resolved processing config for any entity:

curl https://api.bota.dev/v1/devices/dev_abc123/config/processing \
  -H "Authorization: Bearer sk_live_..."

{
  "data": {
    "auto_transcription": {
      "enabled": true,
      "provider": "whisper"
    },
    "auto_summary": {
      "enabled": true,
      "provider": "gemini",
      "template": "clinical_soap"
    }
  }
}

Troubleshooting

Recording Uploaded But Not Auto-Transcribed

Check:

Processing config is enabled: GET /v1/devices/:id/config/processing
Recording reached uploaded status (check recording.uploaded webhook)
ASR provider API key is configured (system default or user-provided)

Auto-Transcription Works But No Summary

Check:

auto_summary.enabled is true in resolved config
Transcription completed successfully (not failed)
LLM provider API key is configured

Wrong Provider or Template Used

Config is resolved from the recording’s context at the time of processing. Check which level the setting is coming from:

# Check device-level override
GET /v1/devices/:id/config/processing

# Check end-user-level override
GET /v1/end-users/:id/config/processing

# Check project-level config
GET /dashboard/projects/:projectId/config

A more specific level always takes precedence. To revert to the parent’s setting, delete the override at the lower level.

Hierarchical Config

Learn how config inheritance works

Create Transcription

Manual transcription API reference

Create Summary

Manual summary API reference

Webhook Events

Subscribe to processing events

Getting Started

Features

Hardware

Webhooks

Legal & Compliance

Auto-Processing

Overview

Quick Start

How It Works

Processing Flow

Config Resolution

Error Handling

Configuration

Processing Config Schema

Auto-Transcription Settings

Auto-Summary Settings

Setting Config at Different Levels

Project Level

End User Level

Device Level

Disable for a Specific Entity

Remove Override (Revert to Inherited)

Monitoring

Webhook Events

Checking Results

Verifying Current Config

Troubleshooting

Recording Uploaded But Not Auto-Transcribed

Auto-Transcription Works But No Summary

Wrong Provider or Template Used

Hierarchical Config

Create Transcription

Create Summary

Webhook Events

Getting Started

Features

Hardware

Webhooks

Legal & Compliance

​Overview

​Quick Start

​How It Works

​Processing Flow

​Config Resolution

​Error Handling

​Configuration

​Processing Config Schema

​Auto-Transcription Settings

​Auto-Summary Settings

​Setting Config at Different Levels

​Project Level

​End User Level

​Device Level

​Disable for a Specific Entity

​Remove Override (Revert to Inherited)

​Monitoring

​Webhook Events

​Checking Results

​Verifying Current Config

​Troubleshooting

​Recording Uploaded But Not Auto-Transcribed

​Auto-Transcription Works But No Summary

​Wrong Provider or Template Used

Hierarchical Config

Create Transcription

Create Summary

Webhook Events

Overview

Quick Start

How It Works

Processing Flow

Config Resolution

Error Handling

Configuration

Processing Config Schema

Auto-Transcription Settings

Auto-Summary Settings

Setting Config at Different Levels

Project Level

End User Level

Device Level

Disable for a Specific Entity

Remove Override (Revert to Inherited)

Monitoring

Webhook Events

Checking Results

Verifying Current Config

Troubleshooting

Recording Uploaded But Not Auto-Transcribed

Auto-Transcription Works But No Summary

Wrong Provider or Template Used