Skip to content

Integrations

Your tools.
Closer to the work.

Bring delivery evidence into the project, let your systems contribute and connect the agents you use. Keep useful context with the people doing the work.

Explore the connections Meet your connected agents

A connection
with a purpose.

GitLab

Follow code and delivery evidence beside the work.

Apps and the API

Give another system the projects and permissions it needs.

MCP clients

Bring your agents into shared work and knowledge.

Gmail and SMTP

Review and send an email from the work’s context.

Connection types supported by Tellenze · setup and availability vary by workspace

GitLab delivery evidence

See the code.
Keep the context.

Connect your GitLab.com group and link its repositories to projects. Bring pipelines, merge requests, branches and commits into the conversation about delivery.

The shared connection supports one GitLab.com group or subgroup, including its subgroups, using a read-only token. Self-managed GitLab hosts are not supported yet.

Read the GitLab setup guide

The project’s latest evidence.

Check the default-branch pipeline, browse merge requests and explore branch commits. Follow the original record in GitLab when you need more detail.

A link to the right work item.

Include a work item’s complete identifier in a commit message or merge request. Its Development section finds matching recent activity in the linked repository.

Know how fresh it is.

Freshness labels and refresh controls distinguish current results from cached or unavailable information. Review the evidence against the work’s acceptance criteria.

Apps and the API

Your system can
lend a hand.

Create a named App for a system you want to connect. Choose its projects and permissions, then use the workspace’s API to read or contribute.

Admins can create Apps by default. Workspaces can also allow members to create their own. Each App stays bound to its owner’s current access.

Explore the App API guide
  1. 1

    Choose the access it needs.

    Grant specific projects and separate read and write permissions. Workspace Knowledge has its own optional grant.

  2. 2

    Contribute useful work and context.

    Read projects, work items, Focus groups and documents. With the right grants, create or update supported work-item and document fields, or submit and read Signals on an eligible plan.

  3. 3

    Keep the responsible person visible.

    Contributions record the App and its owner. Rotate or revoke a credential when needed, while retaining the attribution of earlier work.

MCP connections

Your preferred agent.
Your shared context.

Authorize a compatible Model Context Protocol client to work with the projects, tasks and knowledge you can access. Review the workspace and account before granting access.

CodexClaudeCompatible MCP clients
Explore agents in Tellenze

A connection you can recognize.

Use a named machine profile for the client and map repositories when relevant. Review active MCP connections in personal settings and revoke the ones you no longer use.

The same access and guidance.

Connected clients act within the member’s permissions. Supported changes respect Required Context, with contributions attributed to the person and agent behind them.

ChatGPT, in a private pilot.

The Tellenze plugin is being prepared for a private pilot, with work and document cards alongside the conversation. Public installation depends on review and approval.

Gmail and SMTP sending

Write with the context.
Send with confidence.

Prepare an email from a work-item conversation, Spotlight or Looper. Review the recipients, subject and message, choose a permitted sender, then explicitly send it.

Gmail connections authorize email sending. They do not read your inbox or import email into Signals.

See how email connections work

Personal and shared senders.

Connect a personal account or use an available workspace mailbox. Both Gmail and SMTP support personal and shared connections.

Setup stays with the workspace.

Administrators enable each provider and configure the workspace’s Google OAuth application. SMTP connections use the sending details and credentials permitted by your email provider.

A draft you can return to.

Keep your draft while you review the work and choose the next step. Saved history remains available after a connection is disabled or disconnected.

Connections with clear boundaries

Useful access.
A visible owner.

Choose a connection for its purpose, give it appropriate access and keep a clear record of what it contributes.

Keep access specific.

App grants and member permissions determine what connected systems can see and change. A connection does not make private project content public.

Review the workflow.

GitLab webhook events can support configured automation rules. Event delivery and enabled rules require their own setup alongside the read-only connection.

Keep sending deliberate.

Email connections provide a sender. Review the draft and choose Send when you are ready to contact someone.

Explore what’s available

A growing catalogue.
A clear status.

Browse the workspace integration catalogue by purpose, search for a tool and filter by availability. GitLab, Gmail and SMTP have setup pages; configured publishing integrations may also appear for your workspace.

Tools labeled Coming soon are planned and cannot be connected yet. That includes listed providers such as GitHub, Slack, Google Drive and Notion.

  • Check the provider’s status and setup requirements before planning a workflow around it.
  • Use the scoped App API when building a connection for your own system.

Give the work a shared home

Bring the evidence.
Keep the next step close.

Let your connections support the work, its context and the people responsible for the outcome.

Explore work management

COME TAKE A LOOK

A little less busy.
A lot more together.

Curious? Leave your email. We’ll keep you posted on early access and what’s new.