Flat-File Automation in SailPoint IdentityNow

Introduction Of Flat-File Automation in IdentityNow

1. The flat files, especially CSVs, aren’t going away any time soon legacy apps depend on them, and vendors keep sending them. Usually, these files just sit in SFTP or FTP folders, or sometimes get buried in some internal directory. SailPoint needs to grab these files to create, update, and manage identities.

2. In IdentityIQ (IIQ), this whole process is dead simple. IIQ lives inside your network, so it can just reach out and grab files from your internal servers. Drop a file in an SFTP or FTP folder, and IIQ picks it up during its scheduled run. Everything from pulling the file, to processing it, to bringing the data in—all happens right there inside IIQ. You just point IIQ to the folder, hand over the credentials, and it takes care of the rest.

3. Now, IdentityNow (IDN) is a different story. It’s cloud-native, so you get all the benefits of the cloud, but it can’t talk directly to your internal SFTP or FTP servers. The Delimited File Connector reads CSVs, sure, but only if you upload the file yourself in the UI or put it on a Virtual Appliance.

4. That’s where things get tricky. IDN can’t reach those remote file servers by itself. So, even if some app automatically drops a fresh file into SFTP every night, IDN can’t touch it unless someone uploads it manually or a script pushes it up from a local machine.

java -jar sailpoint-file-upload-utility.jar

• --url <tenant-url>

• --clientId <client-id>

• --clientSecret <secret>

• --file <file-path>

What’s Actually Going On

This takes care of uploading files automatically. You can set up the script to run on a schedule using Windows Task Scheduler, cron jobs, PowerShell whatever works for you. As long as the file is sitting on your machine or server, the tool pushes it straight into IDN.

But here’s the thing: the tool only works with files that are already local. It doesn’t talk to SFTP or FTP servers. So if your source system is dropping files onto SFTP, you’re stuck needing another process to grab them before you can upload to IDN. That means you’re missing true end-to-end automation.

Why SQL Loader Matters for Real Automation

When you need a system that runs completely on its own—especially when files start on SFTP or FTP the File Upload Utility just doesn’t cut it. That’s where the SQL Loader Connector steps in. SQL Loader   right into SFTP or FTP; just give it the path and credentials. It grabs the file, loads the data into a staging database, and IDN can pull straight from there. No manual uploads, no copying files around, no fussing with local folders.

With SQL Loader, you get back the same kind of automation you probably had in IIQ, but built for IDN’s cloud-native world.

Which Tool Actually Fits?

If your files are already sitting on your computer and you just want to skip logging into the UI every single time, go with the File Upload Utility. It’s simple and gets the job done. But if your files show up on SFTP or FTP and you want the whole process to run itself no manual steps at all then SQL Loader is what you want. It scoops up the files, stages the data, and hands everything off to IDN for the rest. That’s real end-to-end.

Conclusion

Flat-file integrations seem easy until you dive in and realize IIQ and IDN don’t handle them the same way at all. IIQ deals with files directly, so there’s not much to worry about. IDN’s a bit different it can’t pull files from remote servers on its own. That’s where the File Upload Utility comes in, but it only helps if you’re uploading files yourself. For teams that rely on automated SFTP or FTP feeds, SQL Loader really shines. It grabs the files, loads them into the database, and keeps everything humming along without you having to touch a thing. If you want real automation from start to finish, SQL Loader’s your best bet.