Skip to content
PagerDuty logoFTP/SFTP logo

Connect PagerDuty to FTP/SFTP

Move data between PagerDuty and FTP/SFTP the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

PagerDuty triggers
3
PagerDuty actions
6
FTP/SFTP triggers
1
FTP/SFTP actions
8

Automation ideas

What you can build with PagerDuty and FTP/SFTP

A few flows teams run between PagerDuty and FTP/SFTP. Use one as a starting point, or build your own from scratch.

  • New Incident in PagerDuty creates Create File from Text in FTP/SFTP

    Triggers when a new incident is created

  • New File in FTP/SFTP creates Create Incident in PagerDuty

    Trigger when a new file is created or modified.

  • New Incident in PagerDuty creates Upload File in FTP/SFTP

    Triggers when a new incident is created

  • New File in FTP/SFTP creates List Incidents in PagerDuty

    Trigger when a new file is created or modified.

  • New Incident in PagerDuty creates Read File Content in FTP/SFTP

    Triggers when a new incident is created

  • New File in FTP/SFTP creates Get Incident in PagerDuty

    Trigger when a new file is created or modified.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in PagerDuty and acts in FTP/SFTP, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.