Guide

How to automate SFTP file feeds end to end

TL;DR: point the recurring feed at an SFTP inbox, attach a no-code cleanup rule with a file-arrival trigger, and the whole pipeline — receive, clean, deliver — runs itself the moment each file lands. Server-side, 24/7, nobody babysitting it.

The recurring file-feed problem

Banks, suppliers, payroll bureaus, and legacy systems don't call APIs — they drop files. Usually on a schedule, usually onto SFTP, and usually in a format the next system can't use as-is. So somebody's job becomes: check the folder, download the file, clean it up, load it where it goes. Every day or every week, forever.

The work is completely rule-shaped — same file type, same fixes, same destination — which makes it the single best candidate for automation in most finance and ops teams.

The setup, step by step

  1. Set up your SFTP inbox. On Team plans and up, Morph provides an SFTP inbox — a secure folder your counterparties (or your own systems) can drop files into. No server to run yourself.
  2. Point the feed at the inbox. Give the bank, supplier, payroll bureau, or internal system the inbox credentials, or redirect an existing scheduled upload to it.
  3. Build the cleanup rule once. Define how each file type should be cleaned, mapped, and reshaped — the same no-code rules used everywhere in Morph.
  4. Attach a file-arrival trigger. Link the rule to the inbox. The moment a matching file lands, the rule runs — instantly, server-side, with no one logged in.
  5. Deliver and monitor. The cleaned output lands in your inbox's outputs folder — retrievable over the same SFTP connection — and can also be delivered to Google Drive or downloaded as CSV. Failed runs are flagged, the original file is kept, and failures never count against your syncs.

How file-arrival triggers compare to schedules

Scheduled runs (daily on Starter, hourly on Pro and up) fit data you pull — a nightly Xero export, for instance. File-arrival triggers fit data that arrives on someone else's clock: the trigger fires when the file lands, however irregular the sender is. Both run server-side with no one logged in, and both follow the same rule — only successful runs count, failed runs are always free.

See pricing for which plans include which triggers, or the integrations overview for everything the cleaned output can be delivered to.

FAQ

Common questions

Do I need my own SFTP server?

No. Team plans and up include a Morph-provided SFTP inbox. Files your counterparties drop there stay in your inbox, under your control, and trigger your rules on arrival. (On Pro, SFTP is available as an add-on.)

How fast does the trigger fire when a file lands?

On arrival — the trigger is event-driven, not polled on a timer. Processing runs server-side, so it works at 3am on a Sunday with nobody logged in.

What happens if a file is malformed and the run fails?

The run is flagged as failed so you can see what happened, the original file is preserved, and failed runs never count against your plan's syncs.

Which plans include SFTP file-arrival triggers?

Team (£149/month) and up include the SFTP inbox and its file-arrival triggers; Pro can add SFTP as an add-on. See the pricing page for the full plan table.

Put the file feed on autopilot

SFTP inbox + file-arrival triggers on Team and up