Skip to main content

Cotool + Tines

Connect Tines to Cotool so agents create and update Tines cases and records, escalate alerts to Tines, start Cotool agents from stories, and ingest audit logs.

Automation
Updated

The short answer

Cotool works with Tines in both directions: agents create, update, and query Tines cases and records, alert escalations can open Tines cases, Tines stories can start Cotool agents through the API, and Tines audit logs can be ingested into Cotool.[1][3]

How it connects: Cotool calls the Tines REST API with an API key sent in the X-User-Token header. A team API key is linked to a service account with role-based access to one team, and its actions are recorded as that service account.[2][5]

What Cotool uses from Tines

Cases
Agents read and update Tines cases, which belong to a team, and alert detail pages in Cotool link to the Tines case an escalation created.[1][6]
Records
Agents create, update, and query Tines records, so structured investigation results can feed your Tines reporting.[1]
Audit logs
Cotool's managed log ingestion supports Tines audit logs. Tines audit events include API key creation, edits, and deletions.[1][7]

Detections, hunts, and triage

Escalate into a Tines caseResponse
When an agent escalates an alert, Cotool can open a Tines case and show a link to it on the alert detail page, so the team working in Tines sees the agent's evidence.[1]
Call a Cotool agent from a Tines storyTriage
Cotool's docs show a Tines story calling Cotool's endpoint with an agent ID and a Linear issue ID to start a Linear agent session with that agent.[3]
Detect risky automation changesDetection
With Tines audit logs in Cotool, a detection watches for new or edited API keys and other administrative changes in your automation platform.[1][4][7]

Setup and permissions

Tines recommends generating an API key through its connect flow from the team's Credentials page. The token secret is visible only when the key is created.[5]

PermissionAccess
Team API keyRole-based access to one team, for cases and records in that team.[5]Write
AUDIT_LOG_READTenant permission a tenant owner can grant to a service API key, for reading audit logs.[5][7]Read
  • A key without permission for a resource gets 404: Not Found, not 403, which can look like a missing case rather than a permission problem.[5]

How Cotool works with Tines

  • Cotool added the Tines Cases integration in release 0.36.0, record retrieval in 0.57.0, and record creation and updates in 0.68.0.[1]

FAQ

Does Cotool replace Tines?
Cotool connects to Tines rather than replacing it: agents read and write Tines cases and records, and Tines stories can call Cotool agents.[1][3]

Sources

  1. Changelog (Cotool docs) · accessed November 16, 2026
  2. Integrations (Cotool) · accessed November 16, 2026
  3. Linear integration (Cotool docs) · accessed November 16, 2026
  4. Detections are code (Cotool Detect) · accessed November 16, 2026
  5. Authentication and authorization (Tines API) · accessed November 16, 2026
  6. Cases (Tines API) · accessed November 16, 2026
  7. Audit logs (Tines API) · accessed November 16, 2026

Related integrations

All integrations

Use cases with Tines

Attackers are scaling with tokens

Cotool helps defenders operate at machine speed. See how security teams are scaling Detection & Response.

Book a demo