Integrations

Tekk gets more useful when it can see beyond your repository, into the tools where your software actually runs and where problems actually show up. You connect those tools through Composio, and Tekk uses them in two ways: as signals that can wake a loop, and as read-only tools a loop can query while it investigates.

Only one loop needs a connector. Customer feedback reads what your customers report, so it runs only when a connected feedback tool delivers a new report, and never runs if none is connected. Every other loop runs on your repository alone; a connected tool makes the loops that use it sharper.

The connectors

Your repository comes from GitHub or GitLab. On top of that, these tools can be connected to a project:

Tool	What a loop can read	Wakes a loop	Used by
Sentry	Your org, projects, issues, events and releases	A new error, a slow transaction	Reliability, Performance, Backend, Observability, Alerts, Payments, AI engineering, React, Testing, Compliance, Customer feedback
Datadog	Monitors, metrics, logs, traces and incidents	A monitor alert, a latency alert, a monitor with no data, an incident	Backend, Performance, Reliability, Observability, Alerts, Compliance
PostHog	Trends, funnels, retention, events and experiments	A drop in retention	Product analytics, Performance, Observability, AI engineering, Compliance, Customer feedback
Stripe	Payment intents, charges, refunds and balance	A failed payment	Payments
Supabase	Database errors, advisors, health and schema	—	Security, Reliability, Backend, Performance, Compliance
PagerDuty	Incidents, alerts, schedules and escalation policies	—	Reliability, Alerts
incident.io	Incidents, alerts, follow-ups and schedules	—	Reliability, Alerts
Mixpanel	Segmentation, funnels, retention and profiles	—	Product analytics, Compliance
Jam	Bug reports with their console logs, network requests, user steps and transcript	A new bug report	Customer feedback
Intercom	Conversations, tickets and help-center articles	A new or updated conversation	Customer feedback
Canny	Feature requests, votes and comments	A new request, or new votes on an old one	Customer feedback
Gmail	Support mail under one label or sent to one address, never the rest of the inbox	New support mail	Customer feedback
Zendesk	Tickets, their comments and satisfaction ratings	A new or changed open ticket	Customer feedback
Freshdesk	Tickets, their conversations and your knowledge base	A new ticket	Customer feedback
Plain	Support threads and the issues they are linked to	An open thread with new activity	Customer feedback
X	Recent public posts that mention your product, found by search terms you choose	A new post matching your terms	Customer feedback
Slack	Channels and threads	—	Status updates from loops (see writes)
Notion	Pages, databases and comments	—	Context for the agent while it works
Confluence	Spaces, pages and content	—	Context for the agent while it works
Bitbucket	Repositories, pull requests and files	—	Context for the agent while it works

Code changes wake loops too: pushes, deployments and code-scanning alerts arrive from GitHub and GitLab by webhook. Bitbucket can be read as a connector, but a project’s repository has to come from GitHub or GitLab for now.

How a connected tool wakes a loop

Tekk checks Sentry, Datadog, PostHog and Stripe as part of each loop’s survey of your project. When one shows something the loop cares about (an error spike, a monitor that fired, a retention drop, a failed payment), that signal wakes the loop and goes into its brief. The loop treats it as a starting point, then reads the code behind it before it drafts a proposal. An issue in production can become a reviewed fix on your board.

Feedback tools work the same way for Customer feedback. Tekk checks each connected one for new reports (a Jam, a support conversation or ticket, a request or a vote, a post) and wakes the loop with them. It stores only a short excerpt of each report, with email addresses and phone numbers masked; the loop reads the full report from the tool while it works. Connecting your first feedback tool switches Customer feedback on, unless you have switched it off.

A signal never stops a loop from running. Without the tool connected, the loop still works from your code; with it, the loop knows where production is hurting. Customer feedback is the one exception: with no feedback tool connected, it has nothing to read and does not run.

Connecting a tool

1. Open Settings → Integrations in the app. You can also connect tools during onboarding.
2. Choose Connect next to the tool.
3. Sign in with the tool’s own login flow. Datadog, PostHog, Mixpanel, incident.io, Jam, Canny, Freshdesk and Plain ask for an API key instead. For Gmail you also choose the one label or address that holds your support mail, and for X the search terms that find posts about your product; until you do, Tekk reads neither.
4. That’s it. The loops of that project can use the connection from their next run.

Connections belong to a project: the tools you connect for one codebase are the ones its loops use. You can reconnect or disconnect a tool at any time from the same page.

Reads by default, writes only when you allow them

Everything a loop does with a connected tool is read-only. Stripe in particular is read-only: a loop can look at charges and refunds, never create or change them.

Two connectors have a write action, and both stay off until you switch them on for your workspace:

• Slack can post and update a loop’s own status messages in a channel.
• Sentry can add an alert rule that an accepted Alerts proposal asks for.

Even then, the write is never in the model’s hands. It runs as a fixed action, and only after you accept the proposal that calls for it. As with everything in Tekk, what your tools reveal becomes a proposal you review, never a silent change.

More tools over time

Because integrations ride on Composio, adding a tool is a small, deliberate step rather than a custom project each time. If there’s a tool you want the loops to see, let us know.