Integrations
Taktoria works where your teams already do. Every app posts to the Slack or Microsoft Teams channels its admins choose, a LaunchCal launch follows its work in Linear, Jira, GitHub, Asana or ClickUp, and its artifacts export to Notion, Confluence or Google Docs. A workspace admin connects Slack, Microsoft Teams and the ticketing systems once; everybody connects their own docs tools. Dory runs inside Zoom, Google Meet and Microsoft Teams calls.
- SlackEach app posts to the channels its admins choose, and people get the direct messages they want.Used by LaunchCal · OKR Hub · Dory · Go Links · Memegen
- Microsoft TeamsThe same posts as Slack, to the channels its admins choose in your teams, and people's notifications in a chat with Taktoria.Used by LaunchCal · OKR Hub · Dory · Go Links · Memegen
- LinearA launch follows its Linear project: status, progress and status updates.Used by LaunchCal
- JiraA launch follows its Jira epic or issue: status, progress and comments.Used by LaunchCal
- GitHubA launch follows a GitHub project or milestone: status, progress and a project's status updates.Used by LaunchCal
- AsanaA launch follows its Asana project: status and progress.Used by LaunchCal
- ClickUpA launch follows its ClickUp list or task: status, progress and comments.Used by LaunchCal
- NotionAn artifact becomes a Notion page, under a page you pick.Used by LaunchCal
- ConfluenceAn artifact becomes a Confluence page, in a space you pick.Used by LaunchCal
- Google DocsAn artifact becomes a new Google Doc in your Drive.Used by LaunchCal
- ZoomDory in a Zoom meeting's side panel: attendees ask and upvote, and hosts run the Q&A.Used by Dory
- Google MeetDory in a Google Meet call's side panel, with the question on screen on the meeting's stage.Used by Dory
Slack: the news, where your teams already talk
A workspace owner or admin connects Slack once. From then on, each app's admins decide where it posts: every kind of post has a channel of its own, or none. People get direct messages too, in their own language.
What each app can post
- LaunchCalA launch added, a reviewer's decision, a new planned date, a launch shipped, and every Monday the launches planned for the next 30 days.
- OKR HubAn objective added, check-ins, where the quarter stands halfway through, and how it was scored once it is over.
- DoryAn event scheduled with its join code, an event opening, and how it went: who came, and the top questions.
- Go LinksA go link going live, and one pointed somewhere else.
- MemegenA new meme, as its picture, described by its captions for screen readers if you want.
Direct messages
A reviewer hears in Slack when a review is assigned to them or they are nudged. Approval reminders, launch updates, OKR reminders and Dory recaps come by Slack, email, both or neither: each person chooses.
Setting it up
- 1A workspace owner or admin selects Connect Slack in Settings → Integrations, and allows it in Slack.
- 2Each app's admins open its Slack page, under Admin in the app's sidebar, and choose a channel for each kind of post.
- 3Everybody chooses their own direct messages in their notification settings.
What it never does
- It never reads your channels or messages: it posts, lists public channels and finds people by email address.
- It never posts a draft, a private objective, a Dory event for certain email domains or an event's passcode.
- It never posts in a private channel, nor sends somebody's direct message to a channel instead.
Microsoft Teams: the same news, for teams that work there
Everything an app can post to Slack can go to Microsoft Teams as well, or instead: each kind of post to a channel of a team you connected, or none. People get their notifications in a chat with Taktoria, and choose which ones in their notification settings.
Setting it up
- 1Somebody adds the Taktoria app to a team in Microsoft Teams, and it posts a code in the team's General channel.
- 2A workspace owner or admin enters it under Code from Teams in Settings → Integrations, and selects Connect team.
- 3Each app's admins open its Microsoft Teams page, under Admin in the app's sidebar, and choose a channel for each kind of post.
What it never does
- It never reads your channels or chats: Teams sends it only the messages that mention it.
- It never posts a draft, a private objective, a Dory event for certain email domains or an event's passcode.
- It never posts to a team until a workspace admin has entered the code it posted there.
Ticketing systems: launches that follow the work
In LaunchCal, a launch can follow its work in a ticketing system: a Linear project, a Jira epic or issue, a GitHub project or milestone, an Asana project, or a ClickUp list or task. Its status, progress and updates come into the launch once a day, and whenever somebody selects Sync now.
Linear
A launch follows its Linear project: status, progress and status updates.
Connected as an app, so it keeps working whoever connected it.
Jira
A launch follows its Jira epic or issue: status, progress and comments.
Connect it with an Atlassian account kept for Taktoria, one that sees only the projects your launches follow.
GitHub
A launch follows a GitHub project or milestone: status, progress and a project's status updates.
Installed as an app on an organization, it reads only the repositories the organization gives it.
Asana
A launch follows its Asana project: status and progress.
It reads as whoever connects it, so connect it with an Asana account kept for Taktoria.
ClickUp
A launch follows its ClickUp list or task: status, progress and comments.
It reads as whoever connects it, so connect it with a ClickUp account kept for Taktoria.
What comes across
- Status: when the work moves, the launch moves with it, to Scoping, In development or On hold. A status chosen in LaunchCal stands until the project's changes again.
- Progress: a Linear project's own, or the share of the work's issues, items or tasks that are done.
- Updates: status updates from Linear and GitHub, and comments from Jira and ClickUp, appear on the launch's Activity tab, each marked with where it came from.
- Completed: when the work is done, the launch's owners are told it is ready.
Setting it up
- 1A workspace owner or admin selects Connect Linear, Connect Jira, Connect GitHub, Connect Asana or Connect ClickUp in Settings → Integrations, and approves it there.
- 2Anybody who can edit a launch pastes the project's address under Ticketing project, on its Details tab.
- 3The launch syncs at once, then every day until it launches.
What it never does
- It never launches anything: once the required reviews are decided, Press to launch is still a person's decision.
- It never changes a launch that has launched.
- It never writes to a ticketing system: Taktoria only reads.
- It never brings in a Jira comment restricted to some people.
Notion, Confluence and Google Docs: artifacts where your docs live
In LaunchCal, a launch's press release, dashboard and learnings can be exported to a docs tool, as a page of your own. Unlike Slack, Linear and Jira, each person connects their own account, and nobody else exports with it.
Notion
An artifact becomes a Notion page, under a page you pick.
Only the pages you shared with Taktoria while connecting are offered, with the pages inside them.
Confluence
An artifact becomes a Confluence page, in a space you pick.
Any space your Atlassian account can see, on the sites you connected.
Google Docs
An artifact becomes a new Google Doc in your Drive.
Taktoria can open only the documents it made, never the rest of your Drive.
What comes across
- The artifact as written, with its tables, lists, links and code as the tool shows them.
- Exporting again brings the same page up to date, unless you choose Make a new page instead.
- A link to the page stays beside the artifact, for everybody who can see the launch.
Setting it up
- 1Anybody who can edit a launch selects Export beside one of its artifacts.
- 2They select Connect Notion, Connect Confluence or Connect Google Docs, and allow it with their own account.
- 3They choose where the page goes, and export it.
What it never does
- It never exports with somebody else's account: each person connects their own.
- It never lets a Viewer of LaunchCal export.
- It never deletes a page: disconnecting leaves what was exported where it is.
Zoom, Google Meet and Teams: Dory inside the call
A Dory event can run inside the call it goes with. Attendees join, ask and upvote in the meeting's side panel, and hosts run the Q&A there, without leaving the call.
Zoom
Dory in a Zoom meeting's side panel: attendees ask and upvote, and hosts run the Q&A.
Zoom tells only hosts and co-hosts which meeting it is, so attendees may need to type the event's code.
Google Meet
Dory in a Google Meet call's side panel, with the question on screen on the meeting's stage.
Dory finds the event by the call's meeting code, so attendees go straight to it.
Microsoft Teams
Dory in a Microsoft Teams meeting's side panel, with the question on screen on the meeting's stage.
The side panel and the stage are in the Teams desktop app.
Setting it up
- 1Add Dory's app in Zoom, Google Meet or Microsoft Teams.
- 2In a Dory event's settings, paste the call's join link into Meeting link.
- 3In the meeting, open Dory from the meeting's apps. Hosts sign in through a window of their own, and confirm it shows the same code as the panel.
What it never does
- It never takes a Zoom start link, which can carry the host's own sign-in: only join links.
- It never lets anybody past the event's rules: a passcode, members only or certain email domains apply in the meeting too.
- It never reads the call's chat, audio or video.
And your own tools
Everything else can reach Taktoria the way these do.
REST API
Everything the apps do, through API keys scoped per resource, with SDKs for TypeScript and Python.
AI assistants
Each app has its own MCP server, so Claude, ChatGPT, Cursor and other assistants work in it as the person who connected them, with their seats and permissions.
Integrations come with every plan
Start a trial, connect Slack, Linear or Jira on the first day, and see your launches and OKRs where your teams already look.