Tines
No-code workflow automation and orchestration platform for security and IT teams
Tines lets admins grant each product area separately without splitting teams.
◆Recent moves
- 15h ago
More granular control over product access
Admins can now grant access to each Tines product area separately while users stay on the same team. It is another step in the enterprise-controls track, after SSO-group app limits and tenant model defaults.
View source ↗ - 1d ago
Condition actions now support multiple paths
One Condition action can now route events down up to 10 ordered paths, replacing chains of separate Conditions. It is a builder-quality change that makes large stories easier to read, in line with the platform's recent focus on maintainability over new surfaces.
View source ↗ - 11d ago
Set default fallback models for your whole tenant
Tenant owners can now set default smart and fast models with an ordered list of up to five fallbacks. It is a reliability control for AI steps in stories, consistent with Tines adding admin-level governance rather than new AI capabilities.
View source ↗ - 29d ago
Keyless cloud credentials with workload identity federation
AWS, Google Cloud, Entra, and Oracle Cloud credentials can authenticate via workload identity federation, removing long-lived keys from the tenant. For a security-automation vendor, this closes an obvious credential-hygiene gap and fits the enterprise-controls track.
View source ↗ - 1mo ago
Full-text search and filter groups in Cases
Cases search and filtering were rebuilt with full-text search and filter groups. It makes Cases more usable as a working queue as volume grows, matching the parallel investment in Records.
View source ↗ - 1mo ago
Create, update, and delete Records via the Tines MCP
AI clients connected to the Tines MCP server can now create, update, and delete records and record types. Moving MCP from read-only to write access makes Records a data layer that external agents can maintain directly.
View source ↗