@tpaktop Happy to share, I will try and post them later today.
@YvetteLans I think both of your ideas are possible. I never added a way to start Toggle from Fibery, but you can start/stop Toggle timers from the API so presumably you could add a Make automation to do that. I would start/stop it with another Fibery button to trigger a Make webhook. Then the time entries get sent back to Fibery on a schedule as usual. You can also add your own title to any of the entries instead of using an existing Fibery task. For example, I start a Toggle timer called ”Scheduling” any time I was scheduling projects, just to have a metric of how long I spent on it over all projects.
If you guys are interested I can work on a better documented post of the whole process. I think it would be great if @tpaktop’s team was willing to open source it.
Yes, for this specific integration we would be keen to open source it. I confirmed with the team.
We will provide hosted version and open source version of integration people can self host.
Hosted version will be free for as long as we can use free tier on a hosting platform.
Would be great Let me know if you need help with documenting the process.
This is awesome! My team only has experience in how to create automations via N8N. But if you think we can help somehow then let me know so I can arrange a meeting for you with my N8N developer
We(Reify Academy) got βeta version of the toggl integration ready to rock and roll.
I have tried it on my own toggl account and it successfully imports time entries from toggl using token.
For now it only syncs(toggl → fibery) time entries as MVP. Other things are on the way. The best way to help prioritise which other things you want to sync is to create issues in the github repo:
It’s open source as promised - reify-academy/fibery-toggl-integration: Integration between fibery and toggl (github.com)
You can either host it yourself or use hosted version provided by us.
Hello! Sorry for taking so long with the response.
My current solution is kinda “frozen W.I.P”: I haven’t made it everything I wanted it to be, but it’s kinda ok, and I’m yet still to get myself to make it complete.
E.g. I still can’t stop the entry in Toggl (from my phone, like what you like to do) and have Fibery know about that event and get some data from the entry that was stopped. There are also a bunch of manual steps in the setup that I’m sure could be automated, e.g., the creation of the client and project in Toggl.
We use it with the separate workspaces for different clients’ projects, so I’ve made it a shareable template and wrote a short user manual at some point. You can see all that here and check the scripts out. Also, ask me anything about it, I’d be happy to help.
Thanks for sharing.
That gives me some interesting things to think about.
Would you presume that client and project need to be created in toggl?
I’m working with existing client which already has a project. So I’m doing other way around adding sync of projects and clients to fibery.
Though I feel I can make separate external action which can be linked to a button to create a project.
I love your elegant solution for putting token on existing user entity in fibery. Didn’t think of that is in integration I ask user to input token. Realised now that this wont work for multiple user setup. Or each user would need to create separate integration which is probably cumbersome. @Chr1sG is there a general solution that fibery team itself uses when multiple user tokens are required ?
We are a service agency, so multiple clients & projects is a plus for us, yeah.
The only thing I can’t see as easy to automate is auto-creating workspaces in Fibery. Although technically it’s probably possible, there could be difficult places in the logic.
Other things would better be automated, I guess, and firstly:
I’m logging a story on a project of a client Toggl doesn’t know yet? Create that on Toggl automatically and feed the IDs into Fibery.
Fetching the user API tokens is impossible due to security, I think, but any other things to streamline the setup would be nice too.
By the way, @Chr1sG, can I talk to two Fibery workspaces from one script? Like the script is run on one of the “child” workspaces that might not have certain data – can I go look it up in the “mothership” workspace?
Workspaces have no ‘awareness’ of each other, so basic automation scripts in one workspace cannot access info in another.
I guess it might be possible to do some clever stuff where one workspace uses http calls to access/manipulate another workspace (provided the correct authorisation is used) but this is beyond my skillset, so I’ll see if one of the devs wants to chip in
Yeah, I meant sending requests to Fibery’s API from Fibery’s API. Just authorising into the needed workspace. Logically it feels like it should be doable, but I can’t know all the possible permutations.
Let me know if you need help with documenting the process.