Can HumDay connect to Apideck File storage?

Yes. HumDay reads Apideck File storage's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 32 operations are documented.

Do I need to write code to automate Apideck File storage?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Apideck File storage account.

What can HumDay do in Apideck File storage?

21 of the 32 documented operations change something in Apideck File storage, and 11 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Apideck File storage account safe?

Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Apideck File storage is held behind that approval.

Automate Apideck File storage

HumDay reads Apideck File storage’s own published API description and derives 32 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

What Apideck File storage is

Welcome to the File Storage API. You can use this API to access all File Storage API endpoints. ## Base URL The base URL for all API requests is `https://unify.apideck.com` We also provide a [Mock API](https://developers.apideck.com/mock-api) that can be used for testing purposes: `https://mock-api.apideck.com` ## Headers Custom headers that are expected as part of the request. Note that [RFC7230]

API host: unify.apideck.com

What HumDay can do in Apideck File storage

21 documented operations change something in Apideck File storage.

POSTUpload file/file-storage/files
POSTCreate Folder/file-storage/folders
POSTSearch Files/file-storage/files/search
POSTCreate Drive/file-storage/drives
POSTCreate DriveGroup/file-storage/drive-groups
POSTCreate Shared Link/file-storage/shared-links
POSTStart Upload Session/file-storage/upload-sessions
DELETEDelete File/file-storage/files/{id}
PATCHRename or move File/file-storage/files/{id}
DELETEDelete Folder/file-storage/folders/{id}
PATCHRename or move Folder/file-storage/folders/{id}
DELETEAbort Upload Session/file-storage/upload-sessions/{id}
PUTUpload part of File to Upload Session/file-storage/upload-sessions/{id}
POSTCopy Folder/file-storage/folders/{id}/copy
POSTFinish Upload Session/file-storage/upload-sessions/{id}/finish
DELETEDelete Drive/file-storage/drives/{id}
PATCHUpdate Drive/file-storage/drives/{id}
DELETEDelete DriveGroup/file-storage/drive-groups/{id}
PATCHUpdate DriveGroup/file-storage/drive-groups/{id}
DELETEDelete Shared Link/file-storage/shared-links/{id}
PATCHUpdate Shared Link/file-storage/shared-links/{id}

What HumDay can read from Apideck File storage

These are the operations a schedule or a trigger can watch.

GETList Files/file-storage/files
GETList Drives/file-storage/drives
GETList DriveGroups/file-storage/drive-groups
GETList SharedLinks/file-storage/shared-links
GETGet File/file-storage/files/{id}
GETGet Folder/file-storage/folders/{id}
GETGet Upload Session/file-storage/upload-sessions/{id}
GETDownload File/file-storage/files/{id}/download
GETGet Drive/file-storage/drives/{id}
GETGet DriveGroup/file-storage/drive-groups/{id}
GETGet Shared Link/file-storage/shared-links/{id}

How automating Apideck File storage works

Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
See it proven. The program runs and shows you the result before it is allowed near your live Apideck File storage account.
Grant access, then go live. You approve the specific Apideck File storage operations it may use — and only those.