Chapter 8
Integrations and automation
Push events into Discord and Slack, subscribe to them from your own service, and drive the desktop app from your own tooling.
4 sections · Chapter 8 of 8
No tool is the only tool. Your team already lives in a chat channel, you may already run a dashboard or a pipeline of your own, and sooner or later somebody will want to script something.
This chapter is the four ways out. Chat notifications are the ready-made version for Discord and Slack. Outbound webhooks are for driving your own service. The local agent is how tooling on the same machine drives the desktop app. And the REST API is everything else.
They are ordered by how much work each one is: the first takes two minutes, the last is a programming task.
In this chapter
- 8.1Discord and Slack notificationsPaste an incoming webhook URL into a project and your channel sees every push as it happens.
- 8.2Outbound webhooksSubscribe your own service to what happens in your organization, with signed deliveries and a retry log.
- 8.3The local agentA localhost API inside the desktop app that editor tooling and coding agents can drive.
- 8.4The REST APISync, upload, commit, list versions, and restore, authenticated with a project key.
Summary
Four ways out, in increasing order of effort. Chat notifications take two minutes and are worth doing today. Webhooks drive your own systems, with signed, retried, replayable deliveries. The local agent lets tooling on the machine drive the desktop app without credentials of its own. The REST API is everything else.
That is the end of the book. If you started at the introduction and read to here, you have seen the whole product: the daily loop, the board and the changelog it produces, packaging and publishing, automated builds, editions and release trains, and the administration around all of it.
The reference for every endpoint is next, in Appendix A.