In addition to the timer, the feed is the central feature of timeghost. Your Outlook appointments, sent mails, Planner and Outlook tasks, changed OneDrive files and DevOps tasks can already be displayed there. Use drag & drop to easily and quickly assign those entries to your projects. 

With the new Microsoft Power Automate (Flow) Connector you can now expand the feed individually. It is possible to create “Custom Feed Events” that integrate other sources such as Jira, Trello, Asana, GitHub and many more into your feed.

Your individual feed could look like this, for example:

The custom feed events work best when they are started with a trigger from another app. We have created numerous templates for various applications. In this example, a feed entry is automatically created for every GitHub issue that gets closed and is also assigned to your user:

With the GitHub trigger When an issue assigned to me is closed(1) you’ll get most of the necessary return values for the custom feed event. You can look up the return values of the individual triggers in the Power Automate documentation (GitHub documentation). The only thing missing here is a timestamp from the closing of the GitHub task. As a solution we add the Current Time(2) action, which provides us with the current time when the flow is triggered. 

This is followed by the timeghost action Add Custom Feed Event(3). There you can enter your desired values in the various fields. You can use the return values of the triggers to create dynamic entries:

  • Workspace: Select your desired workspace (you have to be a member of it) in which the entry should be posted.

  • Name: Enter your desired name for the custom feed event here. In this example it is a mixture of static text ("GitHub Issue closed: ") and a dynamic field from the GitHub trigger. In this situation we have, of course, selected the value Title(4).

  • User: Search for the desired user from the workspace for which the custom feed events should appear. Either you choose yourself or you create the flow for a colleague.

  • Start: Select the start time of the completed issue. This information is usually difficult to determine with flow for timeghost. In timeghost we want to record the time you worked on the issue. Most connectors (like GitHub) do not provide this data, as these programs are not intended to record time. If we now select the timestamp when the issue was created, this point in time is often very far ahead of the end, since work on the issue frequently begins long after it has been created. We therefore simply select the same time as the end and edit the actual time worked in timeghost.

  • End: Enter the time when the issue was closed. Here we also select the auxiliary value Current Time.

  • Description: Enter a description of the custom feed event. We select the Body field, as the description of the GitHub issue is located there.

  • Icon Url: Select a suitable logo for the feed entry from the huge icon library of Icons8. In the next screenshot you can see an example of this with the GitHub logo(1).

  • Url: Here you can insert a url which you can use to call up the issue or perhaps the associated board (see next screenshot -> 2). As an alternative to the dynamic value used here, you can also manually enter a static url.

This is what two GitHub Custom Feed Events look like:

These were created from the following completed tasks on GitHub using the template flow from above:

With the custom feed events you can completely individualize your timeghost feed. These instructions and our other template flows are only intended to introduce you to the world of Microsoft Power Automate. Let your creativity run wild and create your own flows to make your everyday work easier. 

If you need further help, just write us a message to