Hey @jamie.robson.89 , with that number of columns - here’s a high level example using scheduled workflows on a list for an update flow:
1 - the 1TCSV uploader will give you a list of JSON from your data, something like this:
[
{
“id”: 1,
“first_name”: “John”,
“last_name”: “Doe”,
“email”: “john.doe@example.com”,
“ip_address”: “192.168.1.1”
},
{
“id”: 2,
“first_name”: “Jane”,
“last_name”: “Smith”,
“email”: “jane.smith@example.com”,
“ip_address”: “192.168.1.2”
}
]
2 - Create an endpoint in your app, and get it ready for initialization:
3 - Initialize this endpoint with Dummy data:
4 - Set up your workflow that will actually use this data (Backend Workflow)
5 - on the original endpoint, fire the info that’s received to this Backend workflow (scheduled on list) - the request data is a list of JSON objects (from the 1TCSV)
6 - on each of these workflows - do what you will with the information
7 - on the front end, once the 1TCSV information has been processed, send this to your app endpoint.
8 - test and validate that everything is working 
That’s an example using scheduled workflows on a list. My preference is recursive workflows but it’s a bit more complex.
Good luck with that!
What’s the scale of your CSV uploads? 100s, 1000s, 10,000s?