We regularly receive timesheets from an external IT partner (Excel) and want to import them automatically via API as time entries in awork so they land directly in the correct project. What’s the best-practice approach to do this? Would you implement this with the direct API or another tool like Make/Zapier?
Hi @Jule3 and welcome to the forum. This depends a little bit on the complexity of the import. I think it should be doable with Make and Zapier. You could use a trigger such as a new file in OneDrive/Google Drive, then iterate over the entries and create the time entries in awork. One challenge is probably identifying the correct project and task, but this should be doable as well.
With the API you have more flexibility but usually need to write some code or use AI to generate it. You would use this endpoint to create time entries. Creates a new time entry. | awork API | Documentation
Zapier and Make can also be used to trigger API requests easily so you can combine approaches.
Hi! Thank you, Sebastian, for your reply.
Our developer would like to implement the whole thing in a test environment to ensure that no existing data is overwritten or deleted.
My question now is:
Is it possible to get a separate test account for awork that is API-enabled?
If not, is it possible to create an account that is limited to a test project but still has all API permissions (read, write, delete)?
Is there a recommended procedure for developing such API integrations safely without the risk of damaging live data?
Can we also create a backup to restore data in an emergency?
Thank you in advance for your support—and if you need any additional information, please let me know.
Hi @Jule3, the best way is to create a separate workspace (can be with the same user account) for testing. You should get a 14 day trial. You or the developer can reach out to our support team via chat and we can convert it into a developer workspace. There is no generic way to create a backup, but you can export your data from awork in various ways.