Post local changes, check in in Files.com
A documented Files.com operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Post local changes, check in, and download configuration file (used by some Remote Server integrations, such as the Files.com Agent)
- POSTChanges data · remoteservers
/remote_servers/{id}/configuration_file
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Files.com operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Files.com operations
- Create MessagePOST · changes data
- Create File CommentPOST · changes data
- Create Message CommentPOST · changes data
- Create File Comment ReactionPOST · changes data
- Create Message Comment ReactionPOST · changes data
- Delete file/folderDELETE · changes data
- Update file/folder metadataPATCH · changes data
- Create user session (log in)POST · changes data
Questions
- Can HumDay post local changes, check in in Files.com?
- Yes. This operation is published in Files.com's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Files.com data?
- Yes — this is a POST operation, so it changes something in Files.com. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Files.com account.
Where this came from
Read from a published API description for Files.com at app.files.com/api/rest/v1/swagger_doc.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.