The question comes up twice a week: "Does Sablio integrate with Slack? With Notion? With Jira?"
No. Not now. Here's why.
An integration is a contract
When you add Slack integration to your features page, you promise three things:
- That it works today.
- That it will keep working tomorrow, even if Slack changes its API.
- That it does what the user expects (which varies by team).
All three conflict with the fact that we're three people. Slack changes its permissions twice a year. Notion has evolved its block model three times in two years. Jira is a zoo.
Maintaining an integration is half a full-time role, minimum.
What happens when you promise too early
A competitor I used had 47 integrations. Five actually worked. Twelve half-worked. The rest showed a little greyed-out icon that didn't respond.
When I tried the Asana integration, it hadn't synced since 2023. Nobody had removed it. Nobody warned me. It just hung there like a dead promise.
Worse than no integration. A broken integration erodes trust in the whole product.
What we do instead
Clean CSV export. You can pull your grains into a well-formatted CSV file that loads into pretty much any tool. Not magic. Reliable.
Global keyboard shortcut. ⌘⇧K (or Windows equivalent) starts a session from any app. No Slack integration needed to time a Slack conversation.
Human-readable data. If we disappear tomorrow, your history exports as CSV and you carry on. No lock-in.
When we'll change
Maybe in V2. Maybe. The condition: that we be six, not three. And that an integration answer a need repeatedly raised by at least 30 % of our base, not an isolated request.
Current odds per integration:
- Google Calendar (read-only, to pre-fill sessions): very likely.
- Notion (page title extraction): possible.
- Slack (time spent in a conversation): no, too invasive for our philosophy.
- Jira: probably never.
The list is deliberately short. Every yes has to be defended. The default no is, for now, the honest position.
— Patrick