Back-office automation for Canadian lenders. Calls by phone or video.For Canadian lenders

Book a free call
AI Agency Canada.

Files, payments and screening, on schedule

Examples · No. 1 of 4

A daily customer file to the card processor by SFTP, without anyone logging in

A Canadian consumer lender's daily customer-records export now goes from SharePoint to its card-payment processor over key-based SFTP. Each transfer is confirmed by a separate watchdog, with an error alert on any failed run. It replaced a weekly manual upload.

Our part: we built it.

We build scheduled SFTP transfers like this for Canadian lenders and finance companies, from $995, fixed in writing after a free working prototype.

  • Live in production
  • A Canadian consumer lender
  • No AI: the file is moved, never changed
At a glance
RunsDaily
TakesThe lender's daily customer-records export, from SharePoint
SendsThat file to the card-payment processor, over key-based SFTP
ChecksEach transfer is confirmed by a separate watchdog, with an error alert on any failed run
ReplacedA weekly manual upload
Toolsn8n, SharePoint, Microsoft Graph, SFTP
Our partWe built it
StatusLive in production

What does it do?

  1. Retrieves the daily customer-records export from SharePoint.
  2. Delivers it to the card-payment processor over key-based SFTP.
  3. Sends an error notification if a run fails.
  4. Runs an independent watchdog that confirms each transfer happened.
Daily file transfer to the card processor Daily customer-records export retrieved from SharePoint, delivered by key-based SFTP to the card processor, with each transfer confirmed by a separate watchdog and an error alert on any failed run. Daily customer-records export from SharePoint n8n picks up the file daily, through Microsoft Graph Key-based SFTP delivery to the card-payment processor Card processor's SFTP server file arrives unchanged confirms Separate watchdog confirms each transfer happened
An error alert also goes out on any failed run.

What doesn't it do?

  • Change the file. The loan system's report decides what's in it.
  • Fix a bad export. If the report is wrong, the processor gets the wrong report, on time.
  • Use AI.

Before we build an SFTP transfer, what do we confirm with your partner?

  • Which SFTP clients they accept. Some partners only accept clients on their own list, and not every automation tool can connect to every server. We test the connection from your chosen tool in the prototype.
  • The username format they expect.
  • The key type they accept, and who generates the key pair.
  • The date their test environment will be ready, and who issues test credentials.
  • Whether they confirm receipt. If they don't, the watchdog is what tells you the file arrived.

We already use Power Automate. Do we have to switch?

Not necessarily. We use whichever tool fits each hand-off. Some SFTP servers accept only certain clients, so we test the connection from your chosen tool in the prototype, before you commit. The examples on this site use both, each where it fits.

What would this look like at your lender?

If a partner takes a file from you by SFTP, whether it's a card processor, a bank or anyone else, this is the same build. In the free prototype we'd send a sample file from a test SharePoint folder to your partner's test server with a key pair, and show you the error alert and the watchdog working.

  • Price: SFTP with keys is custom work, fixed in writing after the prototype, from $995.
  • Watching it for you: $99 a month for monitoring, fixes and small changes, month to month.
  • Do this first: ask your partner for test credentials and their list of accepted SFTP clients on day one. Partner test access can take weeks or months.

Which file still waits for someone to log in?

Tell us where it comes from and where it goes. We'll show the transfer working against a test server, free, within 5 business days of receiving sample data and test access.