Este artículo solo está disponible en inglés.
Para Data owners · Actualizado el 6 nov 2026
Send files through SFTP
SFTP is a simple way to get started quickly. Your team, or a vendor, uploads files to a Scowtt SFTP account on an agreed schedule. It needs no cloud account on your side, and it also suits one-time history drops, such as call records from a system you no longer use. Login is by key only, with no passwords.
How it works: You create a key and upload files. Scowtt sets up your SFTP account and checks the data with you.
Before you start
- Someone who can run a terminal command to create a key.
- A tool or script that can export your tables to files and upload them on a schedule.
Steps
-
You: Tell your Scowtt team what you'll send
Let your Scowtt team know which files, who will upload them (your team or a vendor), whether it's a one-time drop or recurring, and how often. If you already have a Scowtt SFTP account, Scowtt adds a folder to it instead of creating a new one.
-
You: Generate an SSH key pair
On Mac, Linux or Windows 10 and later (PowerShell), run this command, replacing the email with your own:
ssh-keygen -t ed25519 -C "your@email.com" -f ~/.ssh/scowtt_sftp_keyIf your file-transfer tool doesn't accept ed25519 keys, use
ssh-keygen -t rsa -b 4096with the same options instead. -
You: Send Scowtt your public key
The command creates two files. Keep ~/.ssh/scowtt_sftp_key private and don't share it. Send ~/.ssh/scowtt_sftp_key.pub, your public key, to your Scowtt team, as the file or its one-line contents. Never send the private key.
-
Scowtt: Set up your account and send your connection details
Scowtt provisions an SFTP account and sends you your username, the host
sftp.scowtt.com, and the fingerprint of the key Scowtt registered. To check it matches yours, runssh-keygen -lf ~/.ssh/scowtt_sftp_key.pub. -
You: Test the connection
sftp -i ~/.ssh/scowtt_sftp_key <username>@sftp.scowtt.comFiles you upload land at the top level of your account.
-
You: Upload the historical backfill
Use one folder per table, for example
/appointments/2026-10-30/. Tell your Scowtt team when it's done. -
Scowtt: Check the files with you
Scowtt confirms the files arrived and checks row counts, schema and sample records with you. If anything needs fixing, your Scowtt team sends the specifics.
-
You: Turn on recurring uploads
Schedule recurring uploads, ideally hourly and at least 4 times a day, following Scowtt's data format standards.
Good to know
- SFTP uses port 22. If your network limits outbound connections, allow port 22 to
sftp.scowtt.com. - Upload each file under a temporary name, such as
.tmp, and rename it when the upload finishes, so Scowtt never reads a half-written file. - Put the date and time in every file name, so new files never replace earlier ones.
- For a scheduled job, store the private key in your tool's secure key store. Anyone with that key can upload to your account, so tell your Scowtt team right away if it's exposed and Scowtt will replace it.
Who does what
| Step | Who | What changes hands |
|---|---|---|
| Tell your Scowtt team what you'll send | You | Which files, who uploads them, how often |
| Generate an SSH key pair | You | — |
| Send Scowtt your public key | You | Your public key (.pub file) |
| Set up your account and send your connection details | Scowtt | Username, host, key fingerprint |
| Test the connection | You | — |
| Upload the historical backfill | You | History files |
| Check the files with you | Scowtt | Confirmation, or fixes needed |
| Turn on recurring uploads | You | Recurring files |