Integrations: Flowdock Git API closing
GitLab has a Flowdock integration that is using the deprecated Flowdock Git API (https://api.flowdock.com/v1/git/...). We are closing the Git API on September 7th 2015.
To keep the Flowdock integration working, the integration will need to be updated to use our new endpoints. The new endpoints bring some benefits with them: you can control which messages end up in the same thread in Flowdock. A great reference implementation is available in Flowdock's standalone [git post-receive hook] (https://github.com/flowdock/flowdock-git-hook). When the hook is used and new commits come in, Flowdock will map each branch's commit messages into its own thread (master excluded).
Since GitLab already uses flowdock-git-hook, the simplest way to achieve this is to upgrade the gitblit-flowdock-git-hook gem to be [synced] (https://github.com/bladealslayer/flowdock-git-hook/pull/1) with the latest flowdock-git-hook.
To test your integration, you need a flow_token, which you can get by beginning to add a Git integration in a Flowdock flow. Click on the cog wheel next to the current flow's name in the sidebar. Choose Inbox settings, find Git from the list and click Add new. The token will be shown there. If you need a new trial of Flowdock to test, you can [sign up for one] (https://www.flowdock.com/signup).
For general information about how to create a Flowdock integration can be found [here] (https://www.flowdock.com/api/production-integrations#/post-inbox).
If you have any questions on how to get started, we will gladly assist you at support@flowdock.com.