Skip to navigation

Connect: export voice agent call data to SFTP and Amazon S3

View as Markdown

Connect pushes your voice agents’ call data to storage you own on a schedule. You add a connection once (an SFTP server or an Amazon S3 bucket), then create export jobs that send data to it. You don’t need to poll Sarvam for files.

Open Monitor → Connect in the sidebar. How it works gives a short in-product walkthrough.

Supported today: SFTP and Amazon S3 (including S3-compatible stores such as MinIO). Azure Blob and Google Cloud Storage are coming soon.

Before you start

  • A dedicated SFTP user that can create folders and write files under the export folder.
  • The server is reachable from Sarvam. If it’s firewalled, ask your Sarvam account team for the egress IPs to allowlist.
  • Enough disk space for your largest export. Recordings are much larger than reports.

Add a connection

1

Open the connection form

Click New connection. If you already have connections, click Manage connections and add one from there.

2

Enter the details

Pick SFTP or Amazon S3 under Type, add a Display name, and fill in the fields below.

3

Test and continue

Sarvam checks it can reach and sign in to your storage before saving. If the test fails, you see the reason and nothing is saved. Check the host, port, credentials, firewall rules and folder permissions, then try again.

4

Pick a folder (optional)

Browse to the folder jobs should write into and click Use this folder, or click Skip to keep the path you entered. On SFTP you can create a New folder here.

FieldNotes
HostServer name only, without sftp:// or a path.
PortDefaults to 22.
Username / PasswordThe dedicated export user.
Base pathTop folder jobs write under. Defaults to /.

Credentials are encrypted at rest and never shown again after saving.

Create an export job

Click New job.

1

Destination

Choose a Connection (only tested connections are listed, or pick Add a connection) and a Frequency: Daily, Weekly, Monthly or One time. All times are IST.

2

Data

Choose All agents or specific agents, then tick what to Include. All agents is resolved at each run, so new agents are picked up automatically.

3

Review

Name the job, check the summary, and click Create job. A one-time job shows Start export instead and runs immediately.

What you can export

DataContentsFormat
Unified reportOne row per call attempt, connected or not, with agent variables and transcripts (transcript, transcript_en).CSV in a .tar
InteractionsConnected calls only, with the same fields.CSV in a .tar
RecordingsOne WAV per call. Skipped for a window with no audio.WAVs in a .tar

Debug calls are excluded. Archives are plain tar, not gzip.

What each run covers

FrequencyWindowExample
DailyThe 24 hours ending at the scheduled time.Daily at 02:00 on Nov 5 covers Nov 4 02:00 → Nov 5 02:00 IST.
WeeklyThe 7 days ending at the scheduled time.Monday 02:00 covers the previous Monday 02:00 onward.
MonthlyThe month ending at the scheduled time (day 1–28).1st at 02:00 on Dec 1 covers Nov 1 02:00 → Dec 1 02:00 IST.
One timeA past date range, start and end days included, up to 92 days. Must end before today (IST).Oct 1 → Oct 7 covers Oct 1 00:00 → Oct 7 23:59:59 IST.
  • Jobs start within 15 minutes of the scheduled time.
  • Missed windows aren’t backfilled automatically. Use a one-time job.
  • A job’s schedule can’t be edited. Create a new job and pause the old one.

Delivered files

Each run writes a dated folder per agent:

{base path}/{job name}/{organization}/{workspace}/{agent}/{date}/
{agent}_control-{date}.json
{agent}_unified_report-{date}.tar
{agent}_interactions-{date}.tar
{agent}_recordings-{date}.tar

{date} is the IST date the window ends. Files are uploaded atomically, so you never see a partly written file.

Each folder includes a control file. Only process an agent’s files when status is "success". A data type missing from the control file wasn’t produced for that window.

{
"date": "2026-11-05",
"status": "success",
"total_bytes": 123456,
"unified_report": { "records": 1000, "bytes": 120000 },
"interactions": { "records": 800, "bytes": 3000 },
"recordings": { "records": 50, "bytes": 456 }
}

Sarvam never deletes files from your storage.

Monitor and manage

  • Jobs table: filter by All jobs, Active or Paused. The cards above it show active jobs, runs today and failed runs in the last 7 days.
  • Job details: click a job for its next run, last run and run history, with each run’s date range, size and status. Open a failed run to see the error.
  • Pause / Resume: resuming schedules the next run from now, so a long-paused job doesn’t fire straight away. One-time jobs can’t be paused.
  • Manage connections: Test, Edit or Delete a connection. Untested connections show Unverified and can’t be used in jobs. To change credentials, re-enter the full set. Deleting a connection stops every job that uses it.

Troubleshooting

ProblemWhat to check
Connect is missing from the sidebarAsk your workspace admin for access.
Connection test failsHost, port, credentials, firewall allowlist, and write permission on the folder.
Job didn’t run at the exact timeJobs start within 15 minutes of the scheduled time. Check Next run in the job details.
No recordings fileNo call audio exists for that window. The run still succeeds.
Files look incompleteWait for the run to pass, then check the control file’s status.