Tines

No entries match these filters. Clear filters

1. Set default fallback models for your whole tenant (2026-11-02) Nov 2, 2026 · issue 128

   Tines adds tenant-wide fallback model configuration, letting owners set an ordered list of up to five backup smart and fast models⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   ⤢
2. 1.0.0 Oct 30, 2026 · issue 125

   API surface changed: +161 endpoints, −141 endpoints⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: +161 endpoints, −141 endpoints⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • + DELETE /api/v1/case_sub_statuses/{id}
   • + DELETE /api/v1/case_templates/{id}
   • + DELETE /api/v1/case_webhooks/{id}
   • + DELETE /api/v1/cases/{case_case_id}/buttons/{id}
   • + DELETE /api/v1/cases/{case_case_id}/comments/{id}
   • + DELETE /api/v1/cases/{case_case_id}/files/{id}
   • + DELETE /api/v1/cases/{case_case_id}/linked_cases/{id}
   • + DELETE /api/v1/cases/{case_case_id}/metadata
   • + DELETE /api/v1/cases/{case_case_id}/records/{id}
   • + DELETE /api/v1/cases/{case_case_id}/subscribers/{id}
   • + DELETE /api/v1/cases/{case_id}
   • + DELETE /api/v1/cases/{case_id}/unsubscribe
   • + DELETE /api/v2/case_inputs/{field_id}
   • + DELETE /api/v2/cases/{case_id}/actions/{id}
   • + DELETE /api/v2/cases/{case_id}/blocks/{id}
   • + DELETE /api/v2/cases/{case_id}/comments/{id}
   • + DELETE /api/v2/cases/{case_id}/comments/{id}/reactions
   • + DELETE /api/v2/cases/{case_id}/fields/{id}
   • + DELETE /api/v2/cases/{case_id}/files/{id}
   • + DELETE /api/v2/cases/{case_id}/linked_cases/{id}
   • + DELETE /api/v2/cases/{case_id}/metadata
   • + DELETE /api/v2/cases/{case_id}/notes/{id}
   • + DELETE /api/v2/cases/{case_id}/records/{id}
   • + DELETE /api/v2/cases/{case_id}/subscribers/{id}
   • + DELETE /api/v2/cases/{case_id}/tasks/{id}
   • + DELETE /api/v2/cases/{id}
   • + DELETE /api/v2/record_types/{id}
   • + DELETE /api/v2/records/{id}
   • + DELETE /api/v2/records/{id}/cases/{case_id}
   • + GET /api/v1/case_files/{guid}
   • + GET /api/v1/case_inputs
   • + GET /api/v1/case_inputs/{case_input_id}/fields
   • + GET /api/v1/case_inputs/{id}
   • + GET /api/v1/case_sub_statuses
   • + GET /api/v1/case_sub_statuses/{id}
   • + GET /api/v1/case_templates
   • + GET /api/v1/case_templates/{id}
   • + GET /api/v1/case_templates/{id}/export
   • + GET /api/v1/case_templates/{id}/preview
   • + GET /api/v1/case_webhooks
   • + GET /api/v1/case_webhooks/{id}
   • + GET /api/v1/cases
   • + GET /api/v1/cases/{case_case_id}/assignees
   • + GET /api/v1/cases/{case_case_id}/buttons
   • + GET /api/v1/cases/{case_case_id}/buttons/{id}
   • + GET /api/v1/cases/{case_case_id}/linked_cases
   • + GET /api/v1/cases/{case_case_id}/metadata
   • + GET /api/v1/cases/{case_case_id}/metadata/{id}
   • + GET /api/v1/cases/{case_case_id}/records
   • + GET /api/v1/cases/{case_case_id}/records/{id}
   • + GET /api/v1/cases/{case_case_id}/subscribers
   • + GET /api/v1/cases/{case_id}
   • + GET /api/v1/cases/{case_id}/pdf
   • + GET /api/v2/cases
   • + GET /api/v2/cases/{case_id}/actions
   • + GET /api/v2/cases/{case_id}/actions/{id}
   • + GET /api/v2/cases/{case_id}/activities
   • + GET /api/v2/cases/{case_id}/activities/{id}
   • + GET /api/v2/cases/{case_id}/assignees
   • + GET /api/v2/cases/{case_id}/blocks
   • + GET /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}
   • + GET /api/v2/cases/{case_id}/blocks/{id}
   • + GET /api/v2/cases/{case_id}/comments
   • + GET /api/v2/cases/{case_id}/comments/{id}
   • + GET /api/v2/cases/{case_id}/fields
   • + GET /api/v2/cases/{case_id}/fields/{id}
   • + GET /api/v2/cases/{case_id}/files
   • + GET /api/v2/cases/{case_id}/files/{file_id}/download
   • + GET /api/v2/cases/{case_id}/files/{file_id}/info
   • + GET /api/v2/cases/{case_id}/files/{id}
   • + GET /api/v2/cases/{case_id}/linked_cases
   • + GET /api/v2/cases/{case_id}/metadata
   • + GET /api/v2/cases/{case_id}/metadata/{id}
   • + GET /api/v2/cases/{case_id}/notes
   • + GET /api/v2/cases/{case_id}/notes/{id}
   • + GET /api/v2/cases/{case_id}/pdf
   • + GET /api/v2/cases/{case_id}/records
   • + GET /api/v2/cases/{case_id}/records/{id}
   • + GET /api/v2/cases/{case_id}/subscribers
   • + GET /api/v2/cases/{case_id}/tasks
   • + GET /api/v2/cases/{case_id}/tasks/{id}
   • + GET /api/v2/cases/{id}
   • + GET /api/v2/records/{id}/cases
   • + PATCH /api/v1/case_sub_statuses/{id}
   • + PATCH /api/v1/case_templates/{id}
   • + PATCH /api/v1/case_webhooks/{id}
   • + PATCH /api/v1/cases/{case_case_id}/buttons/{id}
   • + PATCH /api/v1/cases/{case_case_id}/comments/{id}
   • + PATCH /api/v1/cases/{case_id}
   • + PATCH /api/v2/case_inputs/{field_id}
   • + PATCH /api/v2/cases/{case_id}/actions/{id}
   • + PATCH /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}
   • + PATCH /api/v2/cases/{case_id}/blocks/{id}
   • + PATCH /api/v2/cases/{case_id}/comments/{id}
   • + PATCH /api/v2/cases/{case_id}/fields/{id}
   • + PATCH /api/v2/cases/{case_id}/notes/{id}
   • + PATCH /api/v2/cases/{case_id}/tasks/{id}
   • + PATCH /api/v2/cases/{id}
   • + PATCH /api/v2/record_types/{id}
   • + PATCH /api/v2/records/{id}
   • + POST /api/v1/case_inputs
   • + POST /api/v1/case_sub_statuses
   • + POST /api/v1/case_templates
   • + POST /api/v1/case_templates/import
   • + POST /api/v1/case_webhooks
   • + POST /api/v1/cases
   • + POST /api/v1/cases/{case_case_id}/buttons
   • + POST /api/v1/cases/{case_case_id}/comments
   • + POST /api/v1/cases/{case_case_id}/comments/{id}/add_reaction
   • + POST /api/v1/cases/{case_case_id}/comments/{id}/remove_reaction
   • + POST /api/v1/cases/{case_case_id}/files
   • + POST /api/v1/cases/{case_case_id}/linked_cases
   • + POST /api/v1/cases/{case_case_id}/metadata
   • + POST /api/v1/cases/{case_case_id}/records
   • + POST /api/v1/cases/{case_case_id}/subscribers
   • + POST /api/v1/cases/{case_id}/attach_file
   • + POST /api/v1/cases/{case_id}/comment
   • + POST /api/v1/cases/{case_id}/subscribe
   • + POST /api/v2/cases
   • + POST /api/v2/cases/bulk/fields
   • + POST /api/v2/cases/{case_id}/actions
   • + POST /api/v2/cases/{case_id}/blocks
   • + POST /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}/content
   • + POST /api/v2/cases/{case_id}/comments
   • + POST /api/v2/cases/{case_id}/comments/{id}/reactions
   • + POST /api/v2/cases/{case_id}/fields
   • + POST /api/v2/cases/{case_id}/files
   • + POST /api/v2/cases/{case_id}/linked_cases
   • + POST /api/v2/cases/{case_id}/linked_cases/batch
   • + POST /api/v2/cases/{case_id}/metadata
   • + POST /api/v2/cases/{case_id}/notes
   • + POST /api/v2/cases/{case_id}/notes/{id}/content
   • + POST /api/v2/cases/{case_id}/records
   • + POST /api/v2/cases/{case_id}/subscribers
   • + POST /api/v2/cases/{case_id}/subscribers/batch
   • + POST /api/v2/cases/{case_id}/tasks
   • + POST /api/v2/cases/{case_id}/tasks/batch
   • + POST /api/v2/cases/{id}/description
   • + POST /api/v2/record_types
   • + POST /api/v2/records
   • + POST /api/v2/records/{id}/cases
   • + PUT /api/v1/case_sub_statuses/{id}
   • + PUT /api/v1/case_templates/{id}
   • + PUT /api/v1/case_webhooks/{id}
   • + PUT /api/v1/cases/{case_case_id}/buttons/{id}
   • + PUT /api/v1/cases/{case_case_id}/comments/{id}
   • + PUT /api/v1/cases/{case_case_id}/metadata
   • + PUT /api/v1/cases/{case_id}
   • + PUT /api/v2/case_inputs/{field_id}
   • + PUT /api/v2/cases/{case_id}/actions/batch
   • + PUT /api/v2/cases/{case_id}/actions/{id}
   • + PUT /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}
   • + PUT /api/v2/cases/{case_id}/blocks/{id}
   • + PUT /api/v2/cases/{case_id}/comments/{id}
   • + PUT /api/v2/cases/{case_id}/fields/{id}
   • + PUT /api/v2/cases/{case_id}/metadata
   • + PUT /api/v2/cases/{case_id}/notes/{id}
   • + PUT /api/v2/cases/{case_id}/tasks/{id}
   • + PUT /api/v2/cases/{id}
   • + PUT /api/v2/record_types/{id}
   • + PUT /api/v2/records/{id}
   • − DELETE /api/v1/actions/{id} (breaking)
   • − DELETE /api/v1/actions/{id}/clear_memory (breaking)
   • − DELETE /api/v1/actions/{id}/remove_events (breaking)
   • − DELETE /api/v1/actions/{id}/remove_logs (breaking)
   • − DELETE /api/v1/admin/sync_destinations/{id} (breaking)
   • − DELETE /api/v1/admin/templates/{id} (breaking)
   • − DELETE /api/v1/agents/{id} (breaking)
   • − DELETE /api/v1/agents/{id}/clear_memory (breaking)
   • − DELETE /api/v1/agents/{id}/remove_events (breaking)
   • − DELETE /api/v1/agents/{id}/remove_logs (breaking)
   • − DELETE /api/v1/annotations/{id} (breaking)
   • − DELETE /api/v1/apps/{id} (breaking)
   • − DELETE /api/v1/dashboards/{id} (breaking)
   • − DELETE /api/v1/folders/{id} (breaking)
   • − DELETE /api/v1/global_resources/{id} (breaking)
   • − DELETE /api/v1/links (breaking)
   • − DELETE /api/v1/notes/{id} (breaking)
   • − DELETE /api/v1/run_script_environments/{id} (breaking)
   • − DELETE /api/v1/skills/{skill_name} (breaking)
   • − DELETE /api/v1/stories/batch (breaking)
   • − DELETE /api/v1/stories/{id} (breaking)
   • − DELETE /api/v1/stories/{id}/drafts/{draft_id} (breaking)
   • − DELETE /api/v1/stories/{id}/owners (breaking)
   • − DELETE /api/v1/stories/{id}/recipients (breaking)
   • − DELETE /api/v1/stories/{id}/versions/{version_id} (breaking)
   • − DELETE /api/v1/user_credentials/{id} (breaking)
   • − GET /api/v1/actions (breaking)
   • − GET /api/v1/actions/{agent_id}/events (breaking)
   • − GET /api/v1/actions/{id} (breaking)
   • − GET /api/v1/actions/{id}/logs (breaking)
   • − GET /api/v1/admin/sync_destinations (breaking)
   • − GET /api/v1/admin/sync_destinations/{id} (breaking)
   • − GET /api/v1/admin/templates (breaking)
   • − GET /api/v1/admin/templates/{id} (breaking)
   • − GET /api/v1/admin/tunnel/{tunnel_name}/health (breaking)
   • − GET /api/v1/agents (breaking)
   • − GET /api/v1/agents/{agent_id}/events (breaking)
   • − GET /api/v1/agents/{id} (breaking)
   • − GET /api/v1/agents/{id}/logs (breaking)
   • − GET /api/v1/ai_providers (breaking)
   • − GET /api/v1/ai_usage (breaking)
   • − GET /api/v1/annotations (breaking)
   • − GET /api/v1/annotations/{id} (breaking)
   • − GET /api/v1/apps (breaking)
   • − GET /api/v1/apps/{id} (breaking)
   • − GET /api/v1/dashboards (breaking)
   • − GET /api/v1/dashboards/{id}/export (breaking)
   • − GET /api/v1/events (breaking)
   • − GET /api/v1/events/{id} (breaking)
   • − GET /api/v1/folders (breaking)
   • − GET /api/v1/folders/{id} (breaking)
   • − GET /api/v1/global_resources (breaking)
   • − GET /api/v1/global_resources/{id} (breaking)
   • − GET /api/v1/groups/{id}/runs (breaking)
   • − GET /api/v1/groups/{id}/runs/{group_run_guid} (breaking)
   • − GET /api/v1/notes (breaking)
   • − GET /api/v1/notes/{id} (breaking)
   • − GET /api/v1/reporting/flow_usage (breaking)
   • − GET /api/v1/reporting/time_saved (breaking)
   • − GET /api/v1/run_script_environments (breaking)
   • − GET /api/v1/run_script_environments/{id} (breaking)
   • − GET /api/v1/run_script_environments/{id}/download (breaking)
   • − GET /api/v1/skills (breaking)
   • − GET /api/v1/skills/{skill_name} (breaking)
   • − GET /api/v1/stories (breaking)
   • − GET /api/v1/stories/{id} (breaking)
   • − GET /api/v1/stories/{id}/change_request/ai_description (breaking)
   • − GET /api/v1/stories/{id}/change_request/view (breaking)
   • − GET /api/v1/stories/{id}/drafts (breaking)
   • − GET /api/v1/stories/{id}/export (breaking)
   • − GET /api/v1/stories/{id}/pending_actions (breaking)
   • − GET /api/v1/stories/{id}/runs (breaking)
   • − GET /api/v1/stories/{id}/runs/{story_run_guid} (breaking)
   • − GET /api/v1/stories/{id}/runs/{story_run_guid}/summary (breaking)
   • − GET /api/v1/stories/{id}/versions (breaking)
   • − GET /api/v1/stories/{id}/versions/{version_id} (breaking)
   • − GET /api/v1/user_credentials (breaking)
   • − GET /api/v1/user_credentials/{id} (breaking)
   • − GET /api/v1/workbench (breaking)
   • − GET /api/v1/workbench/{guid} (breaking)
   • − PATCH /api/v1/actions/{id} (breaking)
   • − PATCH /api/v1/admin/sync_destinations/{id} (breaking)
   • − PATCH /api/v1/admin/templates/{id} (breaking)
   • − PATCH /api/v1/agents/{id} (breaking)
   • − PATCH /api/v1/annotations/{id} (breaking)
   • − PATCH /api/v1/folders/{id} (breaking)
   • − PATCH /api/v1/global_resources/{id} (breaking)
   • − PATCH /api/v1/notes/{id} (breaking)
   • − PATCH /api/v1/skills/{skill_name} (breaking)
   • − PATCH /api/v1/stories/{id} (breaking)
   • − PATCH /api/v1/user_credentials/{id} (breaking)
   • − POST /api/v1/actions (breaking)
   • − POST /api/v1/actions/{id}/run (breaking)
   • − POST /api/v1/admin/sync_destinations (breaking)
   • − POST /api/v1/admin/sync_destinations/{id}/manual_sync (breaking)
   • − POST /api/v1/admin/sync_destinations/{id}/story/{story_id}/sync (breaking)
   • − POST /api/v1/admin/templates (breaking)
   • − POST /api/v1/admin/templates/{id}/move (breaking)
   • − POST /api/v1/agents (breaking)
   • − POST /api/v1/agents/{id}/run (breaking)
   • − POST /api/v1/annotations (breaking)
   • − POST /api/v1/apps (breaking)
   • − POST /api/v1/apps/{id}/publish (breaking)
   • − POST /api/v1/dashboards/import (breaking)
   • − POST /api/v1/events/{id}/reemit (breaking)
   • − POST /api/v1/folders (breaking)
   • − POST /api/v1/global_resources (breaking)
   • − POST /api/v1/global_resources/{id}/append (breaking)
   • − POST /api/v1/global_resources/{id}/remove (breaking)
   • − POST /api/v1/global_resources/{id}/replace (breaking)
   • − POST /api/v1/notes (breaking)
   • − POST /api/v1/run_script_environments (breaking)
   • − POST /api/v1/run_script_environments/direct_upload_url (breaking)
   • − POST /api/v1/skills (breaking)
   • − POST /api/v1/stories (breaking)
   • − POST /api/v1/stories/import (breaking)
   • − POST /api/v1/stories/{id}/change_request (breaking)
   • − POST /api/v1/stories/{id}/change_request/approve (breaking)
   • − POST /api/v1/stories/{id}/change_request/cancel (breaking)
   • − POST /api/v1/stories/{id}/change_request/promote (breaking)
   • − POST /api/v1/stories/{id}/change_request/reject (breaking)
   • − POST /api/v1/stories/{id}/disable (breaking)
   • − POST /api/v1/stories/{id}/drafts (breaking)
   • − POST /api/v1/stories/{id}/owners (breaking)
   • − POST /api/v1/stories/{id}/recipients (breaking)
   • − POST /api/v1/stories/{id}/versions (breaking)
   • − POST /api/v1/stories/{id}/versions/{version_id} (breaking)
   • − POST /api/v1/user_credentials (breaking)
   • − PUT /api/v1/actions/{id} (breaking)
   • − PUT /api/v1/admin/sync_destinations/{id} (breaking)
   • − PUT /api/v1/admin/templates/{id} (breaking)
   • − PUT /api/v1/agents/{id} (breaking)
   • − PUT /api/v1/annotations/{id} (breaking)
   • − PUT /api/v1/apps/{id}/files (breaking)
   • − PUT /api/v1/folders/{id} (breaking)
   • − PUT /api/v1/global_resources/{id} (breaking)
   • − PUT /api/v1/global_resources/{id}/locked (breaking)
   • − PUT /api/v1/notes/{id} (breaking)
   • − PUT /api/v1/skills/{skill_name} (breaking)
   • − PUT /api/v1/stories/{id} (breaking)
   • − PUT /api/v1/user_credentials/{id} (breaking)
   • New endpoint DELETE /api/v1/case_sub_statuses/{id}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • New endpoint DELETE /api/v1/case_templates/{id}
   • New endpoint DELETE /api/v1/case_webhooks/{id}
   • New endpoint DELETE /api/v1/cases/{case_case_id}/buttons/{id}
   • New endpoint DELETE /api/v1/cases/{case_case_id}/comments/{id}

   +5 more show less

   • New endpoint DELETE /api/v1/cases/{case_case_id}/files/{id}
   • New endpoint DELETE /api/v1/cases/{case_case_id}/linked_cases/{id}
   • New endpoint DELETE /api/v1/cases/{case_case_id}/metadata
   • New endpoint DELETE /api/v1/cases/{case_case_id}/records/{id}
   • New endpoint DELETE /api/v1/cases/{case_case_id}/subscribers/{id}

   10 details in Everything

   └──▷ BREAKING ON UPGRADE

   • !Removed endpoint DELETE /api/v1/actions/{id}
   • !Removed endpoint DELETE /api/v1/actions/{id}/clear_memory
   • !Removed endpoint DELETE /api/v1/actions/{id}/remove_events
   • !Removed endpoint DELETE /api/v1/actions/{id}/remove_logs
   • !Removed endpoint DELETE /api/v1/admin/sync_destinations/{id}
   • !Removed endpoint DELETE /api/v1/admin/templates/{id}
   • !Removed endpoint DELETE /api/v1/agents/{id}
   • !Removed endpoint DELETE /api/v1/agents/{id}/clear_memory
   • !Removed endpoint DELETE /api/v1/agents/{id}/remove_events
   • !Removed endpoint DELETE /api/v1/agents/{id}/remove_logs
   • !Removed endpoint DELETE /api/v1/annotations/{id}
   • !Removed endpoint DELETE /api/v1/apps/{id}
   • !Removed endpoint DELETE /api/v1/dashboards/{id}
   • !Removed endpoint DELETE /api/v1/folders/{id}
   • !Removed endpoint DELETE /api/v1/global_resources/{id}
   • !Removed endpoint DELETE /api/v1/links
   • !Removed endpoint DELETE /api/v1/notes/{id}
   • !Removed endpoint DELETE /api/v1/run_script_environments/{id}
   • !Removed endpoint DELETE /api/v1/skills/{skill_name}
   • !Removed endpoint DELETE /api/v1/stories/batch
   • !Removed endpoint DELETE /api/v1/stories/{id}
   • !Removed endpoint DELETE /api/v1/stories/{id}/drafts/{draft_id}
   • !Removed endpoint DELETE /api/v1/stories/{id}/owners
   • !Removed endpoint DELETE /api/v1/stories/{id}/recipients
   • !Removed endpoint DELETE /api/v1/stories/{id}/versions/{version_id}
   • !Removed endpoint DELETE /api/v1/user_credentials/{id}
   • !Removed endpoint GET /api/v1/actions
   • !Removed endpoint GET /api/v1/actions/{agent_id}/events
   • !Removed endpoint GET /api/v1/actions/{id}
   • !Removed endpoint GET /api/v1/actions/{id}/logs
   • !Removed endpoint GET /api/v1/admin/sync_destinations
   • !Removed endpoint GET /api/v1/admin/sync_destinations/{id}
   • !Removed endpoint GET /api/v1/admin/templates
   • !Removed endpoint GET /api/v1/admin/templates/{id}
   • !Removed endpoint GET /api/v1/admin/tunnel/{tunnel_name}/health
   • !Removed endpoint GET /api/v1/agents
   • !Removed endpoint GET /api/v1/agents/{agent_id}/events
   • !Removed endpoint GET /api/v1/agents/{id}
   • !Removed endpoint GET /api/v1/agents/{id}/logs
   • !Removed endpoint GET /api/v1/ai_providers
   • !Removed endpoint GET /api/v1/ai_usage
   • !Removed endpoint GET /api/v1/annotations
   • !Removed endpoint GET /api/v1/annotations/{id}
   • !Removed endpoint GET /api/v1/apps
   • !Removed endpoint GET /api/v1/apps/{id}
   • !Removed endpoint GET /api/v1/dashboards
   • !Removed endpoint GET /api/v1/dashboards/{id}/export
   • !Removed endpoint GET /api/v1/events
   • !Removed endpoint GET /api/v1/events/{id}
   • !Removed endpoint GET /api/v1/folders
   • !Removed endpoint GET /api/v1/folders/{id}
   • !Removed endpoint GET /api/v1/global_resources
   • !Removed endpoint GET /api/v1/global_resources/{id}
   • !Removed endpoint GET /api/v1/groups/{id}/runs
   • !Removed endpoint GET /api/v1/groups/{id}/runs/{group_run_guid}
   • !Removed endpoint GET /api/v1/notes
   • !Removed endpoint GET /api/v1/notes/{id}
   • !Removed endpoint GET /api/v1/reporting/flow_usage
   • !Removed endpoint GET /api/v1/reporting/time_saved
   • !Removed endpoint GET /api/v1/run_script_environments
   • !Removed endpoint GET /api/v1/run_script_environments/{id}
   • !Removed endpoint GET /api/v1/run_script_environments/{id}/download
   • !Removed endpoint GET /api/v1/skills
   • !Removed endpoint GET /api/v1/skills/{skill_name}
   • !Removed endpoint GET /api/v1/stories
   • !Removed endpoint GET /api/v1/stories/{id}
   • !Removed endpoint GET /api/v1/stories/{id}/change_request/ai_description
   • !Removed endpoint GET /api/v1/stories/{id}/change_request/view
   • !Removed endpoint GET /api/v1/stories/{id}/drafts
   • !Removed endpoint GET /api/v1/stories/{id}/export
   • !Removed endpoint GET /api/v1/stories/{id}/pending_actions
   • !Removed endpoint GET /api/v1/stories/{id}/runs
   • !Removed endpoint GET /api/v1/stories/{id}/runs/{story_run_guid}
   • !Removed endpoint GET /api/v1/stories/{id}/runs/{story_run_guid}/summary
   • !Removed endpoint GET /api/v1/stories/{id}/versions
   • !Removed endpoint GET /api/v1/stories/{id}/versions/{version_id}
   • !Removed endpoint GET /api/v1/user_credentials
   • !Removed endpoint GET /api/v1/user_credentials/{id}
   • !Removed endpoint GET /api/v1/workbench
   • !Removed endpoint GET /api/v1/workbench/{guid}
   • !Removed endpoint PATCH /api/v1/actions/{id}
   • !Removed endpoint PATCH /api/v1/admin/sync_destinations/{id}
   • !Removed endpoint PATCH /api/v1/admin/templates/{id}
   • !Removed endpoint PATCH /api/v1/agents/{id}
   • !Removed endpoint PATCH /api/v1/annotations/{id}
   • !Removed endpoint PATCH /api/v1/folders/{id}
   • !Removed endpoint PATCH /api/v1/global_resources/{id}
   • !Removed endpoint PATCH /api/v1/notes/{id}
   • !Removed endpoint PATCH /api/v1/skills/{skill_name}
   • !Removed endpoint PATCH /api/v1/stories/{id}
   • !Removed endpoint PATCH /api/v1/user_credentials/{id}
   • !Removed endpoint POST /api/v1/actions
   • !Removed endpoint POST /api/v1/actions/{id}/run
   • !Removed endpoint POST /api/v1/admin/sync_destinations
   • !Removed endpoint POST /api/v1/admin/sync_destinations/{id}/manual_sync
   • !Removed endpoint POST /api/v1/admin/sync_destinations/{id}/story/{story_id}/sync
   • !Removed endpoint POST /api/v1/admin/templates
   • !Removed endpoint POST /api/v1/admin/templates/{id}/move
   • !Removed endpoint POST /api/v1/agents
   • !Removed endpoint POST /api/v1/agents/{id}/run
   • !Removed endpoint POST /api/v1/annotations
   • !Removed endpoint POST /api/v1/apps
   • !Removed endpoint POST /api/v1/apps/{id}/publish
   • !Removed endpoint POST /api/v1/dashboards/import
   • !Removed endpoint POST /api/v1/events/{id}/reemit
   • !Removed endpoint POST /api/v1/folders
   • !Removed endpoint POST /api/v1/global_resources
   • !Removed endpoint POST /api/v1/global_resources/{id}/append
   • !Removed endpoint POST /api/v1/global_resources/{id}/remove
   • !Removed endpoint POST /api/v1/global_resources/{id}/replace
   • !Removed endpoint POST /api/v1/notes
   • !Removed endpoint POST /api/v1/run_script_environments
   • !Removed endpoint POST /api/v1/run_script_environments/direct_upload_url
   • !Removed endpoint POST /api/v1/skills
   • !Removed endpoint POST /api/v1/stories
   • !Removed endpoint POST /api/v1/stories/import
   • !Removed endpoint POST /api/v1/stories/{id}/change_request
   • !Removed endpoint POST /api/v1/stories/{id}/change_request/approve
   • !Removed endpoint POST /api/v1/stories/{id}/change_request/cancel
   • !Removed endpoint POST /api/v1/stories/{id}/change_request/promote
   • !Removed endpoint POST /api/v1/stories/{id}/change_request/reject
   • !Removed endpoint POST /api/v1/stories/{id}/disable
   • !Removed endpoint POST /api/v1/stories/{id}/drafts
   • !Removed endpoint POST /api/v1/stories/{id}/owners
   • !Removed endpoint POST /api/v1/stories/{id}/recipients
   • !Removed endpoint POST /api/v1/stories/{id}/versions
   • !Removed endpoint POST /api/v1/stories/{id}/versions/{version_id}
   • !Removed endpoint POST /api/v1/user_credentials
   • !Removed endpoint PUT /api/v1/actions/{id}
   • !Removed endpoint PUT /api/v1/admin/sync_destinations/{id}
   • !Removed endpoint PUT /api/v1/admin/templates/{id}
   • !Removed endpoint PUT /api/v1/agents/{id}
   • !Removed endpoint PUT /api/v1/annotations/{id}
   • !Removed endpoint PUT /api/v1/apps/{id}/files
   • !Removed endpoint PUT /api/v1/folders/{id}
   • !Removed endpoint PUT /api/v1/global_resources/{id}
   • !Removed endpoint PUT /api/v1/global_resources/{id}/locked
   • !Removed endpoint PUT /api/v1/notes/{id}
   • !Removed endpoint PUT /api/v1/skills/{skill_name}
   • !Removed endpoint PUT /api/v1/stories/{id}
   • !Removed endpoint PUT /api/v1/user_credentials/{id}
3. changelog Oct 28, 2026 · issue 123

   Tines 44.0.0 adds keyless cloud credentials, fallback AI models, cursor pagination for Record Lists, and new record field types.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   ⤢

   ⤢

   ⤢

   ⤢
   └──▷ TRY IT
   Verify records migration is complete before upgrading from 41.x to 44.0.0 — run this from a worker and wait for SAFE TO UPGRADE before proceeding.
   copy

   $ tines:verify_records_migration

   • Removes RECORD_RESULT_SET_TABLE_NAME and RECORDS_MIGRATION_DISABLED configuration keys — both must be removed from your configuration before upgrading to 44.0.0.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds keyless cloud credentials via workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. federation.
   • Adds fallback models for AI Agent actions so a secondary model is used when the primary is unavailable, adds custom model settings for AI providers, and adds Claude Haiku 5.5 as an available model for AI actions.
   • Adds a visual builder to configure user group mappings.
   • Adds new field types for records, and adds cursor pagination, multi-field sorting, and lighter queries to Record List actions.

   +1 more show less

   • Extends story change control requirements to cover action attributes.
   • Removes RECORD_RESULT_SET_TABLE_NAME and RECORDS_MIGRATION_DISABLED configuration keys — both must be removed from your configuration before upgrading to 44.0.0.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds keyless cloud credentials via workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. federation.
   • Adds a visual builder to configure user group mappings.

   3 more in Everything

   └──▷ BREAKING ON UPGRADE

   • !RECORD_RESULT_SET_TABLE_NAME and RECORDS_MIGRATION_DISABLED are removed and must be deleted from your configuration — they no longer have any effect on records.
   • !44.0.0 removes all legacy records migration code including repair tools, status banners, upgrade checks, dual writing, and partition maintenance. Upgrading with unmigrated records makes those records invisible; the old table is retained only until 45.0.0, after which it will be dropped. Do not upgrade if admin banners show 'Data migration in progress,' 'Verifying data integrity…,' discrepancies, or 'Some records are unavailable.'
4. 1.0.0 Oct 23, 2026 · issue 117

   API surface changed: −1 endpoint⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: −1 endpoint⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • − GET /api/v2/records/{id}/cases (breaking)
   └──▷ BREAKING ON UPGRADE

   • !Removed endpoint GET /api/v2/records/{id}/cases
5. announced Oct 22, 2026 · issue 120

   Tines September 2026 adds a v2 Records API, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server, new AI models, API-managed agent skills, and eight new markdown formulas.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   ⤢

   ⤢
   • Introduces the v2 Records API, enabling single-call retrieval of related cases and child record data, with record searches running twice as fast.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds the Tines Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. (MCP) server, letting compatible AI clients search and summarize records and manage cases.
   • Supports updating case fields and triggering notifications on comment changes through the Tines API.
   • Adds AI model selection, supporting OpenAI GPT-6 Astra, Sol, and Luna, and Anthropic Claude Opus 5.5.
   • Enables managing agent skills through the Tines API, including renaming a skill without reconnecting AI Agent actions that reference it.

   +4 more show less

   • Adds eight new markdown formulas for formatting story data into headings, lists, and other structures without writing markdown syntax manually.
   • Adds column controls and priority labels to case queues to keep important details visible.
   • Adds the ability to download all files from a case block together for faster evidence handoff.
   • Gives admins controls over how long audit data is retained and a clearer view of AI usage.
   • Introduces the v2 Records API, enabling single-call retrieval of related cases and child record data, with record searches running twice as fast.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds the Tines Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. (MCP) server, letting compatible AI clients search and summarize records and manage cases.
   • Adds AI model selection, supporting OpenAI GPT-6 Astra, Sol, and Luna, and Anthropic Claude Opus 5.5.
   • Enables managing agent skills through the Tines API, including renaming a skill without reconnecting AI Agent actions that reference it.
   • Adds eight new markdown formulas for formatting story data into headings, lists, and other structures without writing markdown syntax manually.

   +2 more show less

   • Adds the ability to download all files from a case block together for faster evidence handoff.
   • Gives admins controls over how long audit data is retained and a clearer view of AI usage.

   2 more in Everything

6. changelog Oct 20, 2026 · issue 114

   Tines 43.7.0 adds MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.-based Records CRUDCRUDThe four basic database operations — Create, Read, Update, Delete — used as shorthand for any system that manages persistent data records, giving cyber tools a standard model for interacting with stored information., Claude Sonnet 5.5, Records API v2, and SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. group app restrictions.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   ⤢

   ⤢

   ⤢

   ⤢
   • Adds Records API v2 with fewer calls per read and faster searches.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds Tines MCP support for Records, enabling creating, updating, and deleting Records as well as discovering, reading, and searching Records.
   • Adds Claude Sonnet 5.5 as an available model in Tines.
   • Restricts apps to specific SSO groups.
   • Adds several Cases improvements: sets background colors for file and group blocks, downloads all files in a case block at once, shows when a case block was last updated, and adds Tines 3B workflows as case actions.

   +1 more show less

   • Adds a self-hosted database overview page.
   • Adds Records API v2 with fewer calls per read and faster searches.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
   • Adds Tines MCP support for Records, enabling creating, updating, and deleting Records as well as discovering, reading, and searching Records.
   • Restricts apps to specific SSO groups.
   • Adds several Cases improvements: sets background colors for file and group blocks, downloads all files in a case block at once, shows when a case block was last updated, and adds Tines 3B workflows as case actions.
   • Adds a self-hosted database overview page.

   1 more in Everything

   └──▷ BREAKING ON UPGRADE

   • !PostgreSQL 14 reaches end of life on November 12, 2026 — self-hosted deployments must migrate to PostgreSQL 18.
   • !New Tines images will only be released to oci.tines.com beginning January 15, 2027 — no new images will be pushed to Docker Hub after that date.
   • !Access to Tines images on Docker Hub ends March 1, 2027 — Docker deployments must migrate to the OCIOCIOpen Container Initiative standard, maintained by the Linux Foundation, defining the image format and runtime spec that container tools share so images built once run anywhere OCI-compliant. registry before this date.
7. Keyless cloud credentials with workload identity federation (2026-10-15) Oct 15, 2026 · issue 110

   Tines adds keyless cloud credential authentication via workload identityworkload identityAn identity assigned to software, such as a service or container, rather than a person. It lets the workload authenticate and receive permissions without sharing a user's credentials. federation for AWS, Google Cloud, Microsoft Entra, and Oracle Cloud.

   • New integration Workload identity federation support for cloud credential providers
8. 1.0.0 Oct 12, 2026 · issue 105

   API surface changed: −162 endpoints⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   API change

   API surface changed: −162 endpoints⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

   • − DELETE /api/scim/v2/Groups/{id} (breaking)
   • − DELETE /api/scim/v2/Users/{id} (breaking)
   • − DELETE /api/v1/case_sub_statuses/{id} (breaking)
   • − DELETE /api/v1/case_templates/{id} (breaking)
   • − DELETE /api/v1/case_webhooks/{id} (breaking)
   • − DELETE /api/v1/cases/{case_case_id}/buttons/{id} (breaking)
   • − DELETE /api/v1/cases/{case_case_id}/comments/{id} (breaking)
   • − DELETE /api/v1/cases/{case_case_id}/files/{id} (breaking)
   • − DELETE /api/v1/cases/{case_case_id}/linked_cases/{id} (breaking)
   • − DELETE /api/v1/cases/{case_case_id}/metadata (breaking)
   • − DELETE /api/v1/cases/{case_case_id}/records/{id} (breaking)
   • − DELETE /api/v1/cases/{case_case_id}/subscribers/{id} (breaking)
   • − DELETE /api/v1/cases/{case_id} (breaking)
   • − DELETE /api/v1/cases/{case_id}/unsubscribe (breaking)
   • − DELETE /api/v2/case_inputs/{field_id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/actions/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/blocks/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/comments/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/comments/{id}/reactions (breaking)
   • − DELETE /api/v2/cases/{case_id}/fields/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/files/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/linked_cases/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/metadata (breaking)
   • − DELETE /api/v2/cases/{case_id}/notes/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/records/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/subscribers/{id} (breaking)
   • − DELETE /api/v2/cases/{case_id}/tasks/{id} (breaking)
   • − DELETE /api/v2/cases/{id} (breaking)
   • − GET /api/scim/v2/Groups (breaking)
   • − GET /api/scim/v2/Groups/{id} (breaking)
   • − GET /api/scim/v2/Users (breaking)
   • − GET /api/scim/v2/Users/{id} (breaking)
   • − GET /api/v1/case_files/{guid} (breaking)
   • − GET /api/v1/case_inputs (breaking)
   • − GET /api/v1/case_inputs/{case_input_id}/fields (breaking)
   • − GET /api/v1/case_inputs/{id} (breaking)
   • − GET /api/v1/case_sub_statuses (breaking)
   • − GET /api/v1/case_sub_statuses/{id} (breaking)
   • − GET /api/v1/case_templates (breaking)
   • − GET /api/v1/case_templates/{id} (breaking)
   • − GET /api/v1/case_templates/{id}/export (breaking)
   • − GET /api/v1/case_templates/{id}/preview (breaking)
   • − GET /api/v1/case_webhooks (breaking)
   • − GET /api/v1/case_webhooks/{id} (breaking)
   • − GET /api/v1/cases (breaking)
   • − GET /api/v1/cases/{case_case_id}/assignees (breaking)
   • − GET /api/v1/cases/{case_case_id}/buttons (breaking)
   • − GET /api/v1/cases/{case_case_id}/buttons/{id} (breaking)
   • − GET /api/v1/cases/{case_case_id}/linked_cases (breaking)
   • − GET /api/v1/cases/{case_case_id}/metadata (breaking)
   • − GET /api/v1/cases/{case_case_id}/metadata/{id} (breaking)
   • − GET /api/v1/cases/{case_case_id}/records (breaking)
   • − GET /api/v1/cases/{case_case_id}/records/{id} (breaking)
   • − GET /api/v1/cases/{case_case_id}/subscribers (breaking)
   • − GET /api/v1/cases/{case_id} (breaking)
   • − GET /api/v1/cases/{case_id}/pdf (breaking)
   • − GET /api/v2/cases (breaking)
   • − GET /api/v2/cases/{case_id}/actions (breaking)
   • − GET /api/v2/cases/{case_id}/actions/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/activities (breaking)
   • − GET /api/v2/cases/{case_id}/activities/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/assignees (breaking)
   • − GET /api/v2/cases/{case_id}/blocks (breaking)
   • − GET /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/blocks/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/comments (breaking)
   • − GET /api/v2/cases/{case_id}/comments/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/fields (breaking)
   • − GET /api/v2/cases/{case_id}/fields/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/files (breaking)
   • − GET /api/v2/cases/{case_id}/files/{file_id}/download (breaking)
   • − GET /api/v2/cases/{case_id}/files/{file_id}/info (breaking)
   • − GET /api/v2/cases/{case_id}/files/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/linked_cases (breaking)
   • − GET /api/v2/cases/{case_id}/metadata (breaking)
   • − GET /api/v2/cases/{case_id}/metadata/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/notes (breaking)
   • − GET /api/v2/cases/{case_id}/notes/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/pdf (breaking)
   • − GET /api/v2/cases/{case_id}/records (breaking)
   • − GET /api/v2/cases/{case_id}/records/{id} (breaking)
   • − GET /api/v2/cases/{case_id}/subscribers (breaking)
   • − GET /api/v2/cases/{case_id}/tasks (breaking)
   • − GET /api/v2/cases/{case_id}/tasks/{id} (breaking)
   • − GET /api/v2/cases/{id} (breaking)
   • − PATCH /api/scim/v2/Groups/{id} (breaking)
   • − PATCH /api/scim/v2/Users/{id} (breaking)
   • − PATCH /api/v1/case_sub_statuses/{id} (breaking)
   • − PATCH /api/v1/case_templates/{id} (breaking)
   • − PATCH /api/v1/case_webhooks/{id} (breaking)
   • − PATCH /api/v1/cases/{case_case_id}/buttons/{id} (breaking)
   • − PATCH /api/v1/cases/{case_case_id}/comments/{id} (breaking)
   • − PATCH /api/v1/cases/{case_id} (breaking)
   • − PATCH /api/v2/case_inputs/{field_id} (breaking)
   • − PATCH /api/v2/cases/{case_id}/actions/{id} (breaking)
   • − PATCH /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id} (breaking)
   • − PATCH /api/v2/cases/{case_id}/blocks/{id} (breaking)
   • − PATCH /api/v2/cases/{case_id}/comments/{id} (breaking)
   • − PATCH /api/v2/cases/{case_id}/fields/{id} (breaking)
   • − PATCH /api/v2/cases/{case_id}/notes/{id} (breaking)
   • − PATCH /api/v2/cases/{case_id}/tasks/{id} (breaking)
   • − PATCH /api/v2/cases/{id} (breaking)
   • − POST /api/scim/v2/Groups (breaking)
   • − POST /api/scim/v2/Users (breaking)
   • − POST /api/v1/case_inputs (breaking)
   • − POST /api/v1/case_sub_statuses (breaking)
   • − POST /api/v1/case_templates (breaking)
   • − POST /api/v1/case_templates/import (breaking)
   • − POST /api/v1/case_webhooks (breaking)
   • − POST /api/v1/cases (breaking)
   • − POST /api/v1/cases/{case_case_id}/buttons (breaking)
   • − POST /api/v1/cases/{case_case_id}/comments (breaking)
   • − POST /api/v1/cases/{case_case_id}/comments/{id}/add_reaction (breaking)
   • − POST /api/v1/cases/{case_case_id}/comments/{id}/remove_reaction (breaking)
   • − POST /api/v1/cases/{case_case_id}/files (breaking)
   • − POST /api/v1/cases/{case_case_id}/linked_cases (breaking)
   • − POST /api/v1/cases/{case_case_id}/metadata (breaking)
   • − POST /api/v1/cases/{case_case_id}/records (breaking)
   • − POST /api/v1/cases/{case_case_id}/subscribers (breaking)
   • − POST /api/v1/cases/{case_id}/attach_file (breaking)
   • − POST /api/v1/cases/{case_id}/comment (breaking)
   • − POST /api/v1/cases/{case_id}/subscribe (breaking)
   • − POST /api/v2/cases (breaking)
   • − POST /api/v2/cases/bulk/fields (breaking)
   • − POST /api/v2/cases/{case_id}/actions (breaking)
   • − POST /api/v2/cases/{case_id}/blocks (breaking)
   • − POST /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}/content (breaking)
   • − POST /api/v2/cases/{case_id}/comments (breaking)
   • − POST /api/v2/cases/{case_id}/comments/{id}/reactions (breaking)
   • − POST /api/v2/cases/{case_id}/fields (breaking)
   • − POST /api/v2/cases/{case_id}/files (breaking)
   • − POST /api/v2/cases/{case_id}/linked_cases (breaking)
   • − POST /api/v2/cases/{case_id}/linked_cases/batch (breaking)
   • − POST /api/v2/cases/{case_id}/metadata (breaking)
   • − POST /api/v2/cases/{case_id}/notes (breaking)
   • − POST /api/v2/cases/{case_id}/notes/{id}/content (breaking)
   • − POST /api/v2/cases/{case_id}/records (breaking)
   • − POST /api/v2/cases/{case_id}/subscribers (breaking)
   • − POST /api/v2/cases/{case_id}/subscribers/batch (breaking)
   • − POST /api/v2/cases/{case_id}/tasks (breaking)
   • − POST /api/v2/cases/{case_id}/tasks/batch (breaking)
   • − POST /api/v2/cases/{id}/description (breaking)
   • − PUT /api/scim/v2/Groups/{id} (breaking)
   • − PUT /api/scim/v2/Users/{id} (breaking)
   • − PUT /api/v1/case_sub_statuses/{id} (breaking)
   • − PUT /api/v1/case_templates/{id} (breaking)
   • − PUT /api/v1/case_webhooks/{id} (breaking)
   • − PUT /api/v1/cases/{case_case_id}/buttons/{id} (breaking)
   • − PUT /api/v1/cases/{case_case_id}/comments/{id} (breaking)
   • − PUT /api/v1/cases/{case_case_id}/metadata (breaking)
   • − PUT /api/v1/cases/{case_id} (breaking)
   • − PUT /api/v2/case_inputs/{field_id} (breaking)
   • − PUT /api/v2/cases/{case_id}/actions/batch (breaking)
   • − PUT /api/v2/cases/{case_id}/actions/{id} (breaking)
   • − PUT /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id} (breaking)
   • − PUT /api/v2/cases/{case_id}/blocks/{id} (breaking)
   • − PUT /api/v2/cases/{case_id}/comments/{id} (breaking)
   • − PUT /api/v2/cases/{case_id}/fields/{id} (breaking)
   • − PUT /api/v2/cases/{case_id}/metadata (breaking)
   • − PUT /api/v2/cases/{case_id}/notes/{id} (breaking)
   • − PUT /api/v2/cases/{case_id}/tasks/{id} (breaking)
   • − PUT /api/v2/cases/{id} (breaking)
   └──▷ BREAKING ON UPGRADE

   • !Removed endpoint DELETE /api/scim/v2/Groups/{id}
   • !Removed endpoint DELETE /api/scim/v2/Users/{id}
   • !Removed endpoint DELETE /api/v1/case_sub_statuses/{id}
   • !Removed endpoint DELETE /api/v1/case_templates/{id}
   • !Removed endpoint DELETE /api/v1/case_webhooks/{id}
   • !Removed endpoint DELETE /api/v1/cases/{case_case_id}/buttons/{id}
   • !Removed endpoint DELETE /api/v1/cases/{case_case_id}/comments/{id}
   • !Removed endpoint DELETE /api/v1/cases/{case_case_id}/files/{id}
   • !Removed endpoint DELETE /api/v1/cases/{case_case_id}/linked_cases/{id}
   • !Removed endpoint DELETE /api/v1/cases/{case_case_id}/metadata
   • !Removed endpoint DELETE /api/v1/cases/{case_case_id}/records/{id}
   • !Removed endpoint DELETE /api/v1/cases/{case_case_id}/subscribers/{id}
   • !Removed endpoint DELETE /api/v1/cases/{case_id}
   • !Removed endpoint DELETE /api/v1/cases/{case_id}/unsubscribe
   • !Removed endpoint DELETE /api/v2/case_inputs/{field_id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/actions/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/blocks/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/comments/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/comments/{id}/reactions
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/fields/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/files/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/linked_cases/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/metadata
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/notes/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/records/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/subscribers/{id}
   • !Removed endpoint DELETE /api/v2/cases/{case_id}/tasks/{id}
   • !Removed endpoint DELETE /api/v2/cases/{id}
   • !Removed endpoint GET /api/scim/v2/Groups
   • !Removed endpoint GET /api/scim/v2/Groups/{id}
   • !Removed endpoint GET /api/scim/v2/Users
   • !Removed endpoint GET /api/scim/v2/Users/{id}
   • !Removed endpoint GET /api/v1/case_files/{guid}
   • !Removed endpoint GET /api/v1/case_inputs
   • !Removed endpoint GET /api/v1/case_inputs/{case_input_id}/fields
   • !Removed endpoint GET /api/v1/case_inputs/{id}
   • !Removed endpoint GET /api/v1/case_sub_statuses
   • !Removed endpoint GET /api/v1/case_sub_statuses/{id}
   • !Removed endpoint GET /api/v1/case_templates
   • !Removed endpoint GET /api/v1/case_templates/{id}
   • !Removed endpoint GET /api/v1/case_templates/{id}/export
   • !Removed endpoint GET /api/v1/case_templates/{id}/preview
   • !Removed endpoint GET /api/v1/case_webhooks
   • !Removed endpoint GET /api/v1/case_webhooks/{id}
   • !Removed endpoint GET /api/v1/cases
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/assignees
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/buttons
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/buttons/{id}
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/linked_cases
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/metadata
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/metadata/{id}
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/records
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/records/{id}
   • !Removed endpoint GET /api/v1/cases/{case_case_id}/subscribers
   • !Removed endpoint GET /api/v1/cases/{case_id}
   • !Removed endpoint GET /api/v1/cases/{case_id}/pdf
   • !Removed endpoint GET /api/v2/cases
   • !Removed endpoint GET /api/v2/cases/{case_id}/actions
   • !Removed endpoint GET /api/v2/cases/{case_id}/actions/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/activities
   • !Removed endpoint GET /api/v2/cases/{case_id}/activities/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/assignees
   • !Removed endpoint GET /api/v2/cases/{case_id}/blocks
   • !Removed endpoint GET /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/blocks/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/comments
   • !Removed endpoint GET /api/v2/cases/{case_id}/comments/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/fields
   • !Removed endpoint GET /api/v2/cases/{case_id}/fields/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/files
   • !Removed endpoint GET /api/v2/cases/{case_id}/files/{file_id}/download
   • !Removed endpoint GET /api/v2/cases/{case_id}/files/{file_id}/info
   • !Removed endpoint GET /api/v2/cases/{case_id}/files/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/linked_cases
   • !Removed endpoint GET /api/v2/cases/{case_id}/metadata
   • !Removed endpoint GET /api/v2/cases/{case_id}/metadata/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/notes
   • !Removed endpoint GET /api/v2/cases/{case_id}/notes/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/pdf
   • !Removed endpoint GET /api/v2/cases/{case_id}/records
   • !Removed endpoint GET /api/v2/cases/{case_id}/records/{id}
   • !Removed endpoint GET /api/v2/cases/{case_id}/subscribers
   • !Removed endpoint GET /api/v2/cases/{case_id}/tasks
   • !Removed endpoint GET /api/v2/cases/{case_id}/tasks/{id}
   • !Removed endpoint GET /api/v2/cases/{id}
   • !Removed endpoint PATCH /api/scim/v2/Groups/{id}
   • !Removed endpoint PATCH /api/scim/v2/Users/{id}
   • !Removed endpoint PATCH /api/v1/case_sub_statuses/{id}
   • !Removed endpoint PATCH /api/v1/case_templates/{id}
   • !Removed endpoint PATCH /api/v1/case_webhooks/{id}
   • !Removed endpoint PATCH /api/v1/cases/{case_case_id}/buttons/{id}
   • !Removed endpoint PATCH /api/v1/cases/{case_case_id}/comments/{id}
   • !Removed endpoint PATCH /api/v1/cases/{case_id}
   • !Removed endpoint PATCH /api/v2/case_inputs/{field_id}
   • !Removed endpoint PATCH /api/v2/cases/{case_id}/actions/{id}
   • !Removed endpoint PATCH /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}
   • !Removed endpoint PATCH /api/v2/cases/{case_id}/blocks/{id}
   • !Removed endpoint PATCH /api/v2/cases/{case_id}/comments/{id}
   • !Removed endpoint PATCH /api/v2/cases/{case_id}/fields/{id}
   • !Removed endpoint PATCH /api/v2/cases/{case_id}/notes/{id}
   • !Removed endpoint PATCH /api/v2/cases/{case_id}/tasks/{id}
   • !Removed endpoint PATCH /api/v2/cases/{id}
   • !Removed endpoint POST /api/scim/v2/Groups
   • !Removed endpoint POST /api/scim/v2/Users
   • !Removed endpoint POST /api/v1/case_inputs
   • !Removed endpoint POST /api/v1/case_sub_statuses
   • !Removed endpoint POST /api/v1/case_templates
   • !Removed endpoint POST /api/v1/case_templates/import
   • !Removed endpoint POST /api/v1/case_webhooks
   • !Removed endpoint POST /api/v1/cases
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/buttons
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/comments
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/comments/{id}/add_reaction
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/comments/{id}/remove_reaction
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/files
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/linked_cases
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/metadata
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/records
   • !Removed endpoint POST /api/v1/cases/{case_case_id}/subscribers
   • !Removed endpoint POST /api/v1/cases/{case_id}/attach_file
   • !Removed endpoint POST /api/v1/cases/{case_id}/comment
   • !Removed endpoint POST /api/v1/cases/{case_id}/subscribe
   • !Removed endpoint POST /api/v2/cases
   • !Removed endpoint POST /api/v2/cases/bulk/fields
   • !Removed endpoint POST /api/v2/cases/{case_id}/actions
   • !Removed endpoint POST /api/v2/cases/{case_id}/blocks
   • !Removed endpoint POST /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}/content
   • !Removed endpoint POST /api/v2/cases/{case_id}/comments
   • !Removed endpoint POST /api/v2/cases/{case_id}/comments/{id}/reactions
   • !Removed endpoint POST /api/v2/cases/{case_id}/fields
   • !Removed endpoint POST /api/v2/cases/{case_id}/files
   • !Removed endpoint POST /api/v2/cases/{case_id}/linked_cases
   • !Removed endpoint POST /api/v2/cases/{case_id}/linked_cases/batch
   • !Removed endpoint POST /api/v2/cases/{case_id}/metadata
   • !Removed endpoint POST /api/v2/cases/{case_id}/notes
   • !Removed endpoint POST /api/v2/cases/{case_id}/notes/{id}/content
   • !Removed endpoint POST /api/v2/cases/{case_id}/records
   • !Removed endpoint POST /api/v2/cases/{case_id}/subscribers
   • !Removed endpoint POST /api/v2/cases/{case_id}/subscribers/batch
   • !Removed endpoint POST /api/v2/cases/{case_id}/tasks
   • !Removed endpoint POST /api/v2/cases/{case_id}/tasks/batch
   • !Removed endpoint POST /api/v2/cases/{id}/description
   • !Removed endpoint PUT /api/scim/v2/Groups/{id}
   • !Removed endpoint PUT /api/scim/v2/Users/{id}
   • !Removed endpoint PUT /api/v1/case_sub_statuses/{id}
   • !Removed endpoint PUT /api/v1/case_templates/{id}
   • !Removed endpoint PUT /api/v1/case_webhooks/{id}
   • !Removed endpoint PUT /api/v1/cases/{case_case_id}/buttons/{id}
   • !Removed endpoint PUT /api/v1/cases/{case_case_id}/comments/{id}
   • !Removed endpoint PUT /api/v1/cases/{case_case_id}/metadata
   • !Removed endpoint PUT /api/v1/cases/{case_id}
   • !Removed endpoint PUT /api/v2/case_inputs/{field_id}
   • !Removed endpoint PUT /api/v2/cases/{case_id}/actions/batch
   • !Removed endpoint PUT /api/v2/cases/{case_id}/actions/{id}
   • !Removed endpoint PUT /api/v2/cases/{case_id}/blocks/{block_id}/elements/{id}
   • !Removed endpoint PUT /api/v2/cases/{case_id}/blocks/{id}
   • !Removed endpoint PUT /api/v2/cases/{case_id}/comments/{id}
   • !Removed endpoint PUT /api/v2/cases/{case_id}/fields/{id}
   • !Removed endpoint PUT /api/v2/cases/{case_id}/metadata
   • !Removed endpoint PUT /api/v2/cases/{case_id}/notes/{id}
   • !Removed endpoint PUT /api/v2/cases/{case_id}/tasks/{id}
   • !Removed endpoint PUT /api/v2/cases/{id}
9. Create, update, and delete Records via the Tines MCP (2026-10-09) Oct 9, 2026 · issue 099

   Tines MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server now supports create, update, and delete operations for records and record types.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

10. 1.0.0 Oct 6, 2026 · issue 096

    API surface changed: +2 endpoints, 3 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: +2 endpoints, 3 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + DELETE /api/v1/apps/{id}
    • + POST /api/v1/apps/{id}/publish
    • ~ PATCH /api/v1/record_types/{id}: request body changed
    • ~ POST /api/v1/record_types: request body changed
    • ~ PUT /api/v1/record_types/{id}: request body changed
    • New endpoint DELETE /api/v1/apps/{id}⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • New endpoint POST /api/v1/apps/{id}/publish

    2 details in Everything

11. changelog Oct 4, 2026 · issue 094

    Tines 43.5.0 adds GPT-6 Astra, Sol, and Luna models plus Claude Opus 5.5 to its AI capabilities.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds GPT-6 Astra, Sol, and Luna AI models as available options.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds Claude Opus 5.5 as an available AI model.
    • Adds GPT-6 Astra, Sol, and Luna AI models as available options.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    1 more in Everything

12. changelog Sep 26, 2026 · issue 086

    Tines: Adds new dimensions to the AI usage API, enabling more granular reporting on AI consumption.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds new functions for converting content to markdown.
    • Cases and dashboards now stay up to date when viewed in background browser tabs.
    • Enables tracking cases with change control directly in the storyboard.
    • Adds new functions for converting content to markdown.
    • Enables tracking cases with change control directly in the storyboard.

    1 more in Everything

13. 1.0.0 Sep 25, 2026 · issue 085

    API surface changed: +2 endpoints, 39 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: +2 endpoints, 39 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + POST /api/v1/apps
    • + PUT /api/v1/apps/{id}/files
    • ~ DELETE /api/scim/v2/Users/{id}: response schema changed
    • ~ DELETE /api/v1/links: response schema changed
    • ~ DELETE /api/v1/run_script_environments/{id}: response schema changed
    • ~ DELETE /api/v1/stories/{id}/drafts/{draft_id}: response schema changed
    • ~ GET /api/v1/actions/{agent_id}/events: response schema changed
    • ~ GET /api/v1/admin/license: response schema changed
    • ~ GET /api/v1/agents/{agent_id}/events: response schema changed
    • ~ GET /api/v1/ai_usage: response schema changed
    • ~ GET /api/v1/apps: response schema changed
    • ~ GET /api/v1/apps/{id}: response schema changed
    • ~ GET /api/v1/cases: response schema changed
    • ~ GET /api/v1/events: response schema changed
    • ~ GET /api/v1/info/web_stats: response schema changed
    • ~ GET /api/v1/reporting/time_saved: response schema changed
    • ~ GET /api/v1/run_script_environments: response schema changed
    • ~ GET /api/v1/run_script_environments/{id}: response schema changed
    • ~ GET /api/v1/run_script_environments/{id}/download: response schema changed
    • ~ GET /api/v2/cases: response schema changed
    • ~ GET /api/v2/cases/{case_id}/files/{file_id}/info: response schema changed
    • ~ PATCH /api/v1/admin/license: response schema changed
    • ~ PATCH /api/v1/record_types/{id}: request body changed
    • ~ PATCH /api/v1/tags/{id}: response schema changed
    • ~ POST /api/scim/v2/Users: response schema changed
    • ~ POST /api/v1/admin/license: response schema changed
    • ~ POST /api/v1/admin/user_provisioning/mapping: response schema changed
    • ~ POST /api/v1/cases/{case_case_id}/metadata: response schema changed
    • ~ POST /api/v1/global_resources/{id}/remove: response schema changed
    • ~ POST /api/v1/global_resources/{id}/replace: response schema changed
    • ~ POST /api/v1/record_types: request body changed
    • ~ POST /api/v1/records/query: response schema changed
    • ~ POST /api/v1/run_script_environments: response schema changed
    • ~ POST /api/v1/run_script_environments/direct_upload_url: response schema changed
    • ~ POST /api/v1/stories/{id}/change_request/approve: response schema changed
    • ~ POST /api/v1/tags: response schema changed
    • ~ POST /api/v2/cases/{case_id}/metadata: response schema changed
    • ~ POST /api/v2/cases/{case_id}/tasks: response schema changed
    • ~ PUT /api/v1/admin/license: response schema changed
    • ~ PUT /api/v1/record_types/{id}: request body changed
    • ~ PUT /api/v1/tags/{id}: response schema changed
    • New endpoint POST /api/v1/apps⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • New endpoint PUT /api/v1/apps/{id}/files

    2 details in Everything

14. changelog Sep 25, 2026 · issue 085

    Tines: Enables tracking cases with change control directly in the storyboard.

    ⤢ ⤢ ⤢ ⤢
    • Adds formula support for case details.
    • Enables visual case creation in the storyboard.

    2 details in Everything

15. changelog Sep 24, 2026 · issue 084

    Tines 43.4.0–43.3.0: AI usage API gains new dimensions, markdown conversion functions, and storyboard case management with formula support⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds new dimensions to the AI usage API, expanding what usage data can be queried.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    1 detail in Everything

16. changelog Sep 23, 2026 · issue 083

    Tines: Adds new dimensions to the AI usage API, expanding what usage data can be queried and reported on.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds new built-in functions for converting content to markdown format.
    • Cases and dashboards now stay up to date when viewed in background browser tabs.
    • Adds new built-in functions for converting content to markdown format.

    1 more in Everything

17. changelog Sep 22, 2026 · issue 082

    Tines 43.3.0 adds change control tracking and formula support for cases, plus visual case creation in the storyboard.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds change control tracking for cases directly within the storyboard.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds formula support for case details fields.
    • Enables visual case creation from within the storyboard.
    • Adds change control tracking for cases directly within the storyboard.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Enables visual case creation from within the storyboard.

    1 more in Everything

18. 43.4.0 Sep 22, 2026 · release notes

    Tines 43.4.0 adds new dimensions to the AI usage API and new markdown conversion functions

    • Adds new dimensions to the AI usage API for deeper analytics on AI interactions.
    • Introduces new functions for converting content to markdown within workflows.

    2 details in Everything

19. 1.0.0 Sep 21, 2026 · issue 081

    API surface changed: +1 endpoint, 1 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: +1 endpoint, 1 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • + GET /api/v1/reporting/flow_usage
    • ~ GET /api/v1/ai_usage: param action_id (query) added; param story_id (query) added; param user_id (query) added; response schema changed
    • New endpoint GET /api/v1/reporting/flow_usage⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • GET /api/v1/ai_usage: param action_id (query) added; param story_id (query) added; param user_id (query) added

    2 details in Everything

20. 43.3.0 Sep 15, 2026 · release notes

    Tines 43.3.0 adds Story block support with Formula-based case details and change control tracking.

    └──▷ HOW TO FIND IT
    Track an incident with dynamic severity and status using a Formula in the UI.
    📍1. Add a new block to your storyboard. 2. Select Story from the block type dropdown. 3. In the case details, enable Formula mode. 4. Enter: ="Severity: " + $severity_level, then set Status to $current_status.
    • Adds the Story block to the storyboard for creating visually distinct cases
    • Enables use of the Formula language within Story block case details for dynamic content

    2 details in Everything

21. 1.0.0 Sep 14, 2026 · issue 074
    API change

    • ~ DELETE /api/v1/links: request body changed
    • ~ GET /api/v1/audit_logs: response schema changed
    • ~ GET /api/v1/cases: response schema changed
    • ~ GET /api/v1/cases/{case_id}: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records/{id}: response schema changed
    • ~ PATCH /api/v1/admin/templates/{id}: request body changed
    • ~ PATCH /api/v1/cases/{case_id}: response schema changed
    • ~ PATCH /api/v1/record_types/{id}: request body changed
    • ~ POST /api/v1/admin/templates: request body changed
    • ~ POST /api/v1/cases: response schema changed
    • ~ POST /api/v1/record_types: request body changed
    • ~ POST /api/v2/cases/{case_id}/records: response schema changed
    • ~ PUT /api/v1/admin/templates/{id}: request body changed
    • ~ PUT /api/v1/cases/{case_id}: response schema changed
    • ~ PUT /api/v1/record_types/{id}: request body changed
    • − GET /api/v1/admin/users/{email} (breaking)
    └──▷ BREAKING ON UPGRADE

    • !Removed endpoint GET /api/v1/admin/users/{email}
22. docs update Sep 14, 2026 · issue 074

    Tines: Adds optional automatic syncing for skills imported from git.

    └──▷ HOW TO FIND IT
    Navigate to the new MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. settings page to configure or restrict Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server integrations for your space.
    📍In the Tines 3B console, go to Settings › MCP and configure server endpoints and authentication options.
    • Adds Hold Shift shortcut to open connector details from connector pick list.
    • Adds branch rename capability.

    2 details in Everything

23. changelog Sep 14, 2026 · issue 074

    Tines: Enables use of formulas in AI provider URLs for dynamic endpoint configuration.

    ⤢ ⤢ ⤢ ⤢
24. 1.0.0 Sep 13, 2026 · issue 073

    API surface changed: −1 endpoint, 16 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: −1 endpoint, 16 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • ~ DELETE /api/v1/links: request body changed
    • ~ GET /api/v1/audit_logs: response schema changed
    • ~ GET /api/v1/cases: response schema changed
    • ~ GET /api/v1/cases/{case_id}: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records/{id}: response schema changed
    • ~ PATCH /api/v1/admin/templates/{id}: request body changed
    • ~ PATCH /api/v1/cases/{case_id}: response schema changed
    • ~ PATCH /api/v1/record_types/{id}: request body changed
    • ~ POST /api/v1/admin/templates: request body changed
    • ~ POST /api/v1/cases: response schema changed
    • ~ POST /api/v1/record_types: request body changed
    • ~ POST /api/v2/cases/{case_id}/records: response schema changed
    • ~ PUT /api/v1/admin/templates/{id}: request body changed
    • ~ PUT /api/v1/cases/{case_id}: response schema changed
    • ~ PUT /api/v1/record_types/{id}: request body changed
    • − GET /api/v1/admin/users/{email} (breaking)
    └──▷ BREAKING ON UPGRADE

    • !Removed endpoint GET /api/v1/admin/users/{email}
25. changelog Sep 13, 2026 · issue 073

    Tines 43.2.0 adds case API field updates, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tools, formula-driven AI provider URLs, audit log retention config, and dashboard draft mode.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds Update case fields via the API capability, enabling programmatic updates to case fields through the Tines API.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds Audit log retention period configuration, allowing teams to set how long audit log data is retained.
    • Adds Cases tools in the Tines MCP (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.), exposing case management surfaces to AI-driven workflows.
    • Adds change control comments, allowing reviewers to annotate change control submissions.
    • Adds priority labels to the cases list view, surfacing case urgency at a glance.

    +1 more show less

    • Adds case notifications when updating comments, alerting relevant users to comment changes.
    • Adds Update case fields via the API capability, enabling programmatic updates to case fields through the Tines API.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds Audit log retention period configuration, allowing teams to set how long audit log data is retained.
    • Adds Cases tools in the Tines MCP (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.), exposing case management surfaces to AI-driven workflows.
    • Adds change control comments, allowing reviewers to annotate change control submissions.

    2 more in Everything

26. 1.0.0 Sep 12, 2026 · issue 072
    API change

    • ~ DELETE /api/v1/links: request body changed
    • ~ GET /api/v1/audit_logs: response schema changed
    • ~ GET /api/v1/cases: response schema changed
    • ~ GET /api/v1/cases/{case_id}: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records/{id}: response schema changed
    • ~ PATCH /api/v1/admin/templates/{id}: request body changed
    • ~ PATCH /api/v1/cases/{case_id}: response schema changed
    • ~ PATCH /api/v1/record_types/{id}: request body changed
    • ~ POST /api/v1/admin/templates: request body changed
    • ~ POST /api/v1/cases: response schema changed
    • ~ POST /api/v1/record_types: request body changed
    • ~ POST /api/v2/cases/{case_id}/records: response schema changed
    • ~ PUT /api/v1/admin/templates/{id}: request body changed
    • ~ PUT /api/v1/cases/{case_id}: response schema changed
    • ~ PUT /api/v1/record_types/{id}: request body changed
    • − GET /api/v1/admin/users/{email} (breaking)
    └──▷ BREAKING ON UPGRADE

    • !Removed endpoint GET /api/v1/admin/users/{email}
27. docs update Sep 12, 2026 · issue 072

    Tines 3B ships MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. settings, Git sync, workflow monitoring tools, new OAuth connectors, and a ZIP download API endpoint.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    └──▷ HOW TO FIND IT
    Navigate to the new MCP settings page to configure Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server connections and toggle authentication requirements.
    📍In the Tines console, go to Settings › MCP and configure your MCP server connectors, enabling skip authentication for internal servers as needed.
    Review and filter audit log entries by event type to investigate access scope changes before pushing a workflow live.
    📍In the Tines console, go to Settings › Audit Logs, then use the Search and filter option to narrow results by event type or user.
    • Adds API endpoint to download workflow as ZIP for programmatic workflow export.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds a new MCP settings page for configuring Model Context Protocol integrations.
    • Adds Security settings page with public access and session controls.
    • Adds New Connectors tab in Monitoring for connector observability.
    • Adds Search and filter option to audit logs.

    +39 more show less

    • Adds Set unit tests for workflow steps capability.
    • Adds New 'Fix failures' button on workflow-level monitoring.
    • Adds New 'Add tests' button on workflow-level monitoring.
    • Adds Jump through step execution failures navigation in workflow monitoring.
    • Adds New Links page to browse links across all spaces.
    • Adds Tines Units drill down to Monitoring so teams can inspect individual units.
    • Adds Set currency option in the Savings tab within Monitoring.
    • Adds Set user preference for default chat AI model.
    • Adds Space level block self-approval setting for change control.
    • Adds Warn before pushing live when a link's access scope changed.
    • Adds Support SSO route auth for MCP servers.
    • Adds MCP support for spaces using git sync.
    • Adds Preview any file in storage, including audio, video, and markdown.
    • Adds View storage from workflow UI.
    • Adds Hover to view a workflow README in list.
    • Adds Tidy up option for stale branches on a workflow.
    • Adds Branches can be renamed.
    • Adds Request to share a connector in 3B.
    • Adds Built-in skills living in the public repo for discoverability.
    • Adds Workflow step map redesigned view.
    • Adds Discoverable spaces section that collapses in sidebar.
    • Adds 3B can now access main branch step executions and past conversations in a workflow context.
    • Adds Google Gemini as an AI provider.
    • Adds OpenAI-compatible AI provider with support for all auth methods.
    • Adds new OAuth 2.0 connector for ServiceNow.
    • Adds new OAuth 2.0 JWT bearer connector.
    • Adds support for JSON token request format in custom OAuth connectors.
    • Adds connector status display for OAuth errors with tooltip surfacing.
    • Adds new SendSafely connector.
    • Adds new Greenhouse Harvest v3 OAuth connector.
    • Adds new DatoCMS connector.
    • Adds new Zscaler OneAPI OAuth connector.
    • Adds new Jira Service Management connector.
    • Adds new Gainsight connector with OAuth support.
    • Adds new Productiv connector.
    • Adds AWS RDS IAM authentication for database connectors.
    • Adds Microsoft Foundry connector for Claude and OpenAI models.
    • Adds GitHub connector support for GitHub Enterprise Server.
    • Adds option for MCP server connectors to skip authentication.
    • Adds API endpoint to download workflow as ZIP for programmatic workflow export.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds a new MCP settings page for configuring Model Context Protocol integrations.
    • Adds Security settings page with public access and session controls.
    • Adds New Connectors tab in Monitoring for connector observability.
    • Adds Set unit tests for workflow steps capability.

    +27 more show less

    • Adds New 'Fix failures' button on workflow-level monitoring.
    • Adds New 'Add tests' button on workflow-level monitoring.
    • Adds Jump through step execution failures navigation in workflow monitoring.
    • Adds New Links page to browse links across all spaces.
    • Adds Set user preference for default chat AI model.
    • Adds Space level block self-approval setting for change control.
    • Adds Warn before pushing live when a link's access scope changed.
    • Adds Support SSO route auth for MCP servers.
    • Adds View storage from workflow UI.
    • Adds Hover to view a workflow README in list.
    • Adds Tidy up option for stale branches on a workflow.
    • Adds Branches can be renamed.
    • Adds Request to share a connector in 3B.
    • Adds Built-in skills living in the public repo for discoverability.
    • Adds Google Gemini as an AI provider.
    • Adds new OAuth 2.0 connector for ServiceNow.
    • Adds new OAuth 2.0 JWT bearer connector.
    • Adds new SendSafely connector.
    • Adds new Greenhouse Harvest v3 OAuth connector.
    • Adds new DatoCMS connector.
    • Adds new Zscaler OneAPI OAuth connector.
    • Adds new Jira Service Management connector.
    • Adds new Gainsight connector with OAuth support.
    • Adds new Productiv connector.
    • Adds AWS RDS IAM authentication for database connectors.
    • Adds Microsoft Foundry connector for Claude and OpenAI models.
    • Adds option for MCP server connectors to skip authentication.

    12 more in Everything

28. docs update Sep 12, 2026 · issue 072

    Tines adds Amazon Bedrock Mantle as a custom OpenAI-compatible provider, enabling OpenAI models via AWS infrastructure.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    └──▷ HOW TO FIND IT
    Route Tines AI actions through AWS-hosted OpenAI models via Bedrock Mantle — useful when your org requires all LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. traffic to stay within AWS infrastructure.
    📍In Tines, go to Admin › AI › Custom providers › Add provider, set: API endpoint: https://bedrock-mantle.<region>.api.aws/openai/v1 API type: OpenAI Responses (under Extra options) Then open the Models tab and manually add a model ID, e.g. openai.gpt-5.6-luna
29. docs update Sep 12, 2026 · issue 072

    Tines adds live background-tab refresh for Cases/dashboards, a dockable events panel, and pinnable/hideable case table columns.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • Cases, Records, and dashboards now stay up to date automatically when open in background browser tabs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Dock the events panel to keep it persistently visible within the Cases interface.
    • Pin and hide any column in the cases table to customize the view.
    • Cases, Records, and dashboards now stay up to date automatically when open in background browser tabs.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Dock the events panel to keep it persistently visible within the Cases interface.

    1 more in Everything

30. changelog Sep 12, 2026 · issue 072

    Tines: Enables updating case fields via the API, expanding programmatic case management.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds configurable audit log retention period, giving teams control over how long audit records are kept.
    • Adds dashboard draft and edit mode, allowing dashboards to be staged before publishing.
    • Allows renaming new stories under change control without requiring approval.
    • Sends case notifications when comments are updated.
    • Adds change control comments, enabling annotated approval workflows.
    • Adds configurable audit log retention period, giving teams control over how long audit records are kept.
    • Adds dashboard draft and edit mode, allowing dashboards to be staged before publishing.
    • Adds change control comments, enabling annotated approval workflows.

    2 more in Everything

31. 1.0.0 Sep 11, 2026 · issue 071
    API change

    • ~ DELETE /api/v1/links: request body changed
    • ~ GET /api/v1/cases: response schema changed
    • ~ GET /api/v1/cases/{case_id}: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records/{id}: response schema changed
    • ~ PATCH /api/v1/admin/templates/{id}: request body changed
    • ~ PATCH /api/v1/cases/{case_id}: response schema changed
    • ~ PATCH /api/v1/record_types/{id}: request body changed
    • ~ POST /api/v1/admin/templates: request body changed
    • ~ POST /api/v1/cases: response schema changed
    • ~ POST /api/v1/record_types: request body changed
    • ~ POST /api/v2/cases/{case_id}/records: response schema changed
    • ~ PUT /api/v1/admin/templates/{id}: request body changed
    • ~ PUT /api/v1/cases/{case_id}: response schema changed
    • ~ PUT /api/v1/record_types/{id}: request body changed
    • − GET /api/v1/admin/users/{email} (breaking)
    └──▷ BREAKING ON UPGRADE

    • !Removed endpoint GET /api/v1/admin/users/{email}
32. changelog Sep 11, 2026 · issue 071

    Tines 43.2.0 adds MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. case tools, API case-field updates, formula support in AI provider URLs, and audit log retention config.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Supports formulas in AI provider URLs, enabling dynamic endpoint construction for AI actions.
    • Adds Change control comments, letting teams annotate change-control requests directly.
    • Shows priority labels on the cases list for at-a-glance triage.
    • Adds Change control comments, letting teams annotate change-control requests directly.

    2 more in Everything

33. 1.0.0 Sep 10, 2026 · issue 070

    API surface changed: −1 endpoint, 15 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    API change

    API surface changed: −1 endpoint, 15 modified⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    • ~ DELETE /api/v1/links: request body changed
    • ~ GET /api/v1/cases: response schema changed
    • ~ GET /api/v1/cases/{case_id}: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records: response schema changed
    • ~ GET /api/v2/cases/{case_id}/records/{id}: response schema changed
    • ~ PATCH /api/v1/admin/templates/{id}: request body changed
    • ~ PATCH /api/v1/cases/{case_id}: response schema changed
    • ~ PATCH /api/v1/record_types/{id}: request body changed
    • ~ POST /api/v1/admin/templates: request body changed
    • ~ POST /api/v1/cases: response schema changed
    • ~ POST /api/v1/record_types: request body changed
    • ~ POST /api/v2/cases/{case_id}/records: response schema changed
    • ~ PUT /api/v1/admin/templates/{id}: request body changed
    • ~ PUT /api/v1/cases/{case_id}: response schema changed
    • ~ PUT /api/v1/record_types/{id}: request body changed
    • − GET /api/v1/admin/users/{email} (breaking)
    └──▷ BREAKING ON UPGRADE

    • !Removed endpoint GET /api/v1/admin/users/{email}
34. changelog Sep 10, 2026 · issue 070

    Tines 43.2.0 adds case-field API updates, audit-log retention config, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. integration, and dashboard draft mode.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠

    ⤢ ⤢ ⤢ ⤢
    • Adds the ability to update case fields via the API.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds audit log retention period configuration.
    • Adds Cases tools in the Tines MCP (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.) integration.
    • Adds support for using formulas in AI provider URLs.
    • Adds dashboard draft and edit mode.

    +1 more show less

    • Adds change control comments.
    • Adds the ability to update case fields via the API.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠
    • Adds audit log retention period configuration.
    • Adds Cases tools in the Tines MCP (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.) integration.
    • Adds dashboard draft and edit mode.
    • Adds change control comments.

    1 more in Everything

35. changelog Sep 9, 2026 · issue 069

    Tines 43.2.0 adds case management via API, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tools, formula support in AI URLs, and change-control tracking in the storyboard.

    ⤢ ⤢ ⤢ ⤢
    • Adds Update case fields via the API — case fields can now be modified programmatically through the Tines API.
    • Adds Audit log retention period configuration — operators can now configure how long audit logs are retained.
    • Adds Cases tools in the Tines MCP, exposing case management operations to the Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. surface.
    • Adds formula support for AI provider URLs, enabling dynamic construction of provider endpoints at runtime.
    • Adds formula support for case details fields in the storyboard.

    +6 more show less

    • Adds visual case creation directly in the storyboard.
    • Adds change control comments to the change control workflow.
    • Adds dashboard draft and edit mode, letting users stage dashboard changes before publishing.
    • Adds case notifications when updating comments on a case.
    • Adds priority labels to the cases list view.
    • Enables renaming new stories under change control without requiring approval.
    • Adds Update case fields via the API — case fields can now be modified programmatically through the Tines API.
    • Adds Audit log retention period configuration — operators can now configure how long audit logs are retained.
    • Adds Cases tools in the Tines MCP, exposing case management operations to the Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. surface.
    • Adds visual case creation directly in the storyboard.
    • Adds dashboard draft and edit mode, letting users stage dashboard changes before publishing.

    6 more in Everything

36. 1.0.0 Sep 7, 2026 · issue 067

    API surface changed: +1 endpoint, 46 modified

    API change

    API surface changed: +1 endpoint, 46 modified

    • + DELETE /api/v2/case_inputs/{field_id}
    • ~ DELETE /api/v1/admin/roles/{id}: param id (path) added [required]; param role_id (path) removed
    • ~ DELETE /api/v1/admin/users/{id}: param id (path) added [required]; param user_id (path) removed
    • ~ DELETE /api/v1/cases/{case_id}/unsubscribe: param case_id (path) added [required]; param case_case_id (path) removed; param id (path) removed
    • ~ DELETE /api/v1/stories/{id}: param id (path) added [required]; param story_id (path) removed
    • ~ DELETE /api/v1/stories/{id}/drafts/{draft_id}: param id (path) added [required]; param story_id (path) removed
    • ~ DELETE /api/v1/stories/{id}/owners: param id (path) added [required]; param story_id (path) removed
    • ~ DELETE /api/v1/stories/{id}/recipients: param id (path) added [required]; param story_id (path) removed
    • ~ DELETE /api/v1/stories/{id}/versions/{version_id}: param id (path) added [required]; param story_id (path) removed
    • ~ DELETE /api/v2/cases/{case_id}/comments/{id}/reactions: param id (path) added [required]; param comment_id (path) removed
    • ~ GET /api/v1/actions/{agent_id}/events: param agent_id (path) added [required]
    • ~ GET /api/v1/admin/roles/{id}: param id (path) added [required]; param role_id (path) removed
    • ~ GET /api/v1/admin/users/{email}: param email (path) added [required]; param user_id (path) removed
    • ~ GET /api/v1/admin/users/{id}: param id (path) added [required]; param user_id (path) removed
    • ~ GET /api/v1/agents/{agent_id}/events: param agent_id (path) added [required]
    • ~ GET /api/v1/audit_logs: param team_id (query) added; response schema changed
    • ~ GET /api/v1/stories/{id}: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/change_request/ai_description: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/change_request/view: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/drafts: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/export: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/pending_actions: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/runs: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/runs/{story_run_guid}: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/runs/{story_run_guid}/summary: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/versions: param id (path) added [required]; param story_id (path) removed
    • ~ GET /api/v1/stories/{id}/versions/{version_id}: param id (path) added [required]; param story_id (path) removed
    • ~ PATCH /api/v1/admin/roles/{id}: param id (path) added [required]; param role_id (path) removed
    • ~ PATCH /api/v1/admin/users/{id}: param id (path) added [required]; param user_id (path) removed
    • ~ PATCH /api/v1/stories/{id}: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/cases/{case_id}/attach_file: param case_id (path) added [required]; param case_case_id (path) removed
    • ~ POST /api/v1/cases/{case_id}/comment: param case_id (path) added [required]; param case_case_id (path) removed
    • ~ POST /api/v1/cases/{case_id}/subscribe: param case_id (path) added [required]; param case_case_id (path) removed
    • ~ POST /api/v1/stories/{id}/change_request: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/change_request/approve: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/change_request/cancel: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/change_request/promote: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/change_request/reject: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/drafts: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/owners: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/recipients: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/versions: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v1/stories/{id}/versions/{version_id}: param id (path) added [required]; param story_id (path) removed
    • ~ POST /api/v2/cases/{case_id}/comments/{id}/reactions: param id (path) added [required]; param comment_id (path) removed
    • ~ PUT /api/v1/admin/roles/{id}: param id (path) added [required]; param role_id (path) removed
    • ~ PUT /api/v1/admin/users/{id}: param id (path) added [required]; param user_id (path) removed
    • ~ PUT /api/v1/stories/{id}: param id (path) added [required]; param story_id (path) removed
    • New endpoint DELETE /api/v2/case_inputs/{field_id}
    • GET /api/v1/audit_logs: param team_id (query) added; response schema changed

    2 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !DELETE /api/v1/admin/roles/{id}: param id (path) added [required]; param role_id (path) removed
    • !DELETE /api/v1/admin/users/{id}: param id (path) added [required]; param user_id (path) removed
    • !DELETE /api/v1/cases/{case_id}/unsubscribe: param case_id (path) added [required]; param case_case_id (path) removed; param id (path) removed
    • !DELETE /api/v1/stories/{id}: param id (path) added [required]; param story_id (path) removed
    • !DELETE /api/v1/stories/{id}/drafts/{draft_id}: param id (path) added [required]; param story_id (path) removed
    • !DELETE /api/v1/stories/{id}/owners: param id (path) added [required]; param story_id (path) removed
    • !DELETE /api/v1/stories/{id}/recipients: param id (path) added [required]; param story_id (path) removed
    • !DELETE /api/v1/stories/{id}/versions/{version_id}: param id (path) added [required]; param story_id (path) removed
    • !DELETE /api/v2/cases/{case_id}/comments/{id}/reactions: param id (path) added [required]; param comment_id (path) removed
    • !GET /api/v1/actions/{agent_id}/events: param agent_id (path) added [required]
    • !GET /api/v1/admin/roles/{id}: param id (path) added [required]; param role_id (path) removed
    • !GET /api/v1/admin/users/{email}: param email (path) added [required]; param user_id (path) removed
    • !GET /api/v1/admin/users/{id}: param id (path) added [required]; param user_id (path) removed
    • !GET /api/v1/agents/{agent_id}/events: param agent_id (path) added [required]
    • !GET /api/v1/stories/{id}: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/change_request/ai_description: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/change_request/view: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/drafts: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/export: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/pending_actions: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/runs: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/runs/{story_run_guid}: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/runs/{story_run_guid}/summary: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/versions: param id (path) added [required]; param story_id (path) removed
    • !GET /api/v1/stories/{id}/versions/{version_id}: param id (path) added [required]; param story_id (path) removed
    • !PATCH /api/v1/admin/roles/{id}: param id (path) added [required]; param role_id (path) removed
    • !PATCH /api/v1/admin/users/{id}: param id (path) added [required]; param user_id (path) removed
    • !PATCH /api/v1/stories/{id}: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/cases/{case_id}/attach_file: param case_id (path) added [required]; param case_case_id (path) removed
    • !POST /api/v1/cases/{case_id}/comment: param case_id (path) added [required]; param case_case_id (path) removed
    • !POST /api/v1/cases/{case_id}/subscribe: param case_id (path) added [required]; param case_case_id (path) removed
    • !POST /api/v1/stories/{id}/change_request: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/change_request/approve: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/change_request/cancel: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/change_request/promote: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/change_request/reject: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/drafts: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/owners: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/recipients: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/versions: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v1/stories/{id}/versions/{version_id}: param id (path) added [required]; param story_id (path) removed
    • !POST /api/v2/cases/{case_id}/comments/{id}/reactions: param id (path) added [required]; param comment_id (path) removed
    • !PUT /api/v1/admin/roles/{id}: param id (path) added [required]; param role_id (path) removed
    • !PUT /api/v1/admin/users/{id}: param id (path) added [required]; param user_id (path) removed
    • !PUT /api/v1/stories/{id}: param id (path) added [required]; param story_id (path) removed
37. docs update Sep 5, 2026 · issue 065

    Tines adds case API updates, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. cases tools, audit log retention config, and formula-driven AI provider URLs

    • Adds the ability to update case fields via the API, enabling programmatic case management.
    • Exposes Cases tools in the Tines MCP (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.), bringing case operations into AI-driven workflows.
    • Adds audit log retention period configuration for admins, giving control over how long audit logs are kept.
    • Supports formulas in AI provider URLs, allowing dynamic construction of AI endpoint addresses.
    • Shows priority labels on the cases list, surfacing case urgency at a glance.

    +2 more show less

    • Allows renaming new stories under change control without requiring approval.
    • Sends case notifications when comments are updated, keeping stakeholders informed of comment changes.
    • Exposes Cases tools in the Tines MCP (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.), bringing case operations into AI-driven workflows.
    • Adds audit log retention period configuration for admins, giving control over how long audit logs are kept.

    5 more in Everything

38. 1.0.0 Sep 4, 2026 · issue 064

    API surface changed: +2 endpoints

    API change

    API surface changed: +2 endpoints

    • + PATCH /api/v2/case_inputs/{field_id}
    • + PUT /api/v2/case_inputs/{field_id}
    • New endpoint PATCH /api/v2/case_inputs/{field_id}
    • New endpoint PUT /api/v2/case_inputs/{field_id}

    2 details in Everything

39. 1.0.0 Aug 28, 2026 · issue 058

    API surface changed: +6 endpoints, 11 modified

    API change

    API surface changed: +6 endpoints, 11 modified

    • + DELETE /api/v1/skills/{skill_name}
    • + GET /api/v1/skills
    • + GET /api/v1/skills/{skill_name}
    • + PATCH /api/v1/skills/{skill_name}
    • + POST /api/v1/skills
    • + PUT /api/v1/skills/{skill_name}
    • ~ GET /api/v1/stories: response schema changed
    • ~ GET /api/v1/stories/{id}: response schema changed
    • ~ GET /api/v1/stories/{id}/drafts: response schema changed
    • ~ PATCH /api/v1/stories/{id}: response schema changed
    • ~ POST /api/v1/stories: response schema changed
    • ~ POST /api/v1/stories/import: response schema changed
    • ~ POST /api/v1/stories/{id}/change_request/promote: response schema changed
    • ~ POST /api/v1/stories/{id}/drafts: response schema changed
    • ~ POST /api/v1/stories/{id}/owners: response schema changed
    • ~ POST /api/v1/stories/{id}/recipients: response schema changed
    • ~ PUT /api/v1/stories/{id}: response schema changed
    • New endpoint DELETE /api/v1/skills/{skill_name}
    • New endpoint GET /api/v1/skills
    • New endpoint GET /api/v1/skills/{skill_name}
    • New endpoint PATCH /api/v1/skills/{skill_name}
    • New endpoint POST /api/v1/skills

    +12 more show less

    • New endpoint PUT /api/v1/skills/{skill_name}
    • GET /api/v1/stories: response schema changed
    • GET /api/v1/stories/{id}: response schema changed
    • GET /api/v1/stories/{id}/drafts: response schema changed
    • PATCH /api/v1/stories/{id}: response schema changed
    • POST /api/v1/stories: response schema changed
    • POST /api/v1/stories/import: response schema changed
    • POST /api/v1/stories/{id}/change_request/promote: response schema changed
    • POST /api/v1/stories/{id}/drafts: response schema changed
    • POST /api/v1/stories/{id}/owners: response schema changed
    • POST /api/v1/stories/{id}/recipients: response schema changed
    • PUT /api/v1/stories/{id}: response schema changed

    17 details in Everything

40. changelog Aug 26, 2026 · issue 057

    Tines 43.0.0 adds Tines primitives support in Apps and introduces Workbench for Cases.

    ⤢ ⤢ ⤢ ⤢
    • Adds support for Tines primitives in Apps, enabling use of native Tines building blocks within app configurations.
    • Introduces Workbench for Cases, a new environment for working with case data.

    2 details in Everything

41. docs update Aug 19, 2026 · issue 050

    Tines Stories gains a first-party MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server endpoint, letting AI clients like Claude, Cursor, and ChatGPT author stories via plain language.

    • Adds a first-party MCP server endpoint built into Tines Stories tenants, enabling AI clients (ChatGPT, Codex, Cursor, Claude Code, Claude Desktop) to create and modify stories through natural-language instructions against the same story-authoring capabilities as the storyboard UI.
    • Distinguishes the built-in Tines Stories MCP server (for AI clients to author stories externally) from custom MCP servers built inside Tines Stories (for running production integrations), with both surfaces usable simultaneously.

    2 details in Everything

42. docs update Aug 19, 2026 · issue 050

    Tines adds Workbench, an AI chat interface that can execute Stories actions and access proprietary data within your tenant.

    ⤢ ⤢ ⤢

    ⤢
    • New Workbench AI chat interface lets practitioners ask questions and take action in real-time using Tines Stories-powered tools, with data staying private within the tenant.
    • Workbench supports per-user scoping — tool configurations, chats, and custom instructions are individual to each user.
    • Users can enable credentials or stories they have access to run directly within Workbench.
    • Template actions (singular Tines Stories actions) can be individually enabled for use inside Workbench.
    • Built-in Tines Stories formula documentation tool answers questions about formula usage and goal-oriented formula construction in real-time.

    5 details in Everything

43. docs update Aug 19, 2026 · issue 050

    Tines Stories gains sample dashboard templates and scheduled email snapshots for stakeholder reporting.

    ⤢ ⤢ ⤢

    ⤢
    • Adds sample dashboard templates so practitioners can create a pre-built dashboard ready to rename or edit immediately.
    • Adds dashboard Snapshots to email a copy of a dashboard on a configurable schedule, including control over recipients, frequency, and which charts to include — enabling recurring reports for stakeholders without Tines Stories access.

    2 details in Everything

44. docs update Aug 19, 2026 · issue 050

    Tines adds primitive support in Apps, a Workbench for Cases, and a redesigned events panel.

    • Adds support for Tines primitives inside Apps.
    • Introduces Workbench for Cases, integrating Cases with AI in Tines.
    • Delivers a more flexible events panel.

    3 details in Everything

45. Support for Tines primitives in Apps (2026-08-19) Aug 19, 2026 · issue 050

    Tines Apps can now read cases, records, and resources via built-in functions without requiring an endpoint.

46. changelog Aug 19, 2026 · issue 050

    Tines 42.7.0 adds customizable AI credit alerts, SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. access for Apps and Collections, and new case list layouts.

    ⤢ ⤢ ⤢ ⤢
    • Enables customization of AI credit usage alerts so teams can tune notification thresholds for their consumption.
    • Adds SSO-based sharing and access for Apps, allowing practitioners to gate automation apps behind their identity provideridentity providerA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems..
    • Adds SSO-based sharing and access for Collections, extending identity-provider-controlled access to grouped resources.
    • Introduces new layout options for the case list view, giving analysts more flexibility in how they triage and review cases.

    4 details in Everything

47. 42.7.0 Aug 18, 2026 · release notes

    Tines 42.7.0 adds AI credit usage alerts, SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management. for Apps/Collections, and new case list layout options

    • Share and access Collections via SSO integration capability

    1 detail in Everything

48. 0.0.1 Aug 14, 2026 · issue 045

    Tines now publishes an API — 369 endpoints across 71 areas: Actions, Stories > Notes, Stories, …

    • Actions (22 endpoints) — create, read, update, delete
    • Stories > Notes (12 endpoints) — create, read, update, delete
    • Stories (11 endpoints) — create, read, update, delete
    • Teams (v1) (11 endpoints) — create, read, update, delete
    • Admin > Users (10 endpoints) — create, read, update, delete

    +4 more show less

    • Global Resources (v1) (10 endpoints) — create, read, update, delete
    • Cases (v1) > Case Templates (9 endpoints) — create, read, update, delete
    • Admin > Sync Destinations (8 endpoints) — create, read, update, delete
    • 63 more areas: Cases, Records, Admin > Templates, Cases (v1), Cases > Actions, Cases > Fields, Cases > Notes, Cases > Tasks, Stories > Change Control, Admin > Action Egress Control Rules, Admin > Ip Access Control Rules, Admin > Roles, Cases (v1) > Actions, Cases (v1) > Case Statuses, Cases (v1) > Webhooks, Cases > Blocks, Cases > Comments, Cases > Files, Folders (v1), Records > Record Types, Run Script Environments, Scim > Groups, Scim > Users, Tags, User Credentials (v1), Cases (v1) > Comments, Cases (v1) > Metadata, Cases (v1) > Subscribers, Cases > Metadata, Events (v1), Stories > Versions, Admin > License, Admin > Smtp Configuration, Cases (v1) > Fields, Cases (v1) > Files, Cases (v1) > Records, Cases > Blocks > Elements, Cases > Linked Cases, Cases > Records, Cases > Subscribers, Records > Dashboards, Records > Record Views, Admin > User Provisioning, Cases (v1) > Linked Cases, Info, Stories > Drafts, Stories > Story Runs, Ai (v1), Admin > Custom Certificate Authority, Apps (v1), Cases (v1) > Comments > Reactions, Cases > Activities, Cases > Comments > Reactions, Stories > Groups, Stories > Owners, Stories > Recipients, Workbench (v1), Admin > Tunnels, Audit Logs, Cases (v1) > Assignees, Cases > Assignees, Reporting, Stories > Links

    9 details in Everything

49. docs update Aug 14, 2026 · issue 045

    Tines adds per-workflow savings estimation configuration.

    ⤢
    • Enables configuring detailed savings estimates on a per-workflow basis to quantify the value of each automated workflow.

    1 detail in Everything

50. docs update Aug 14, 2026 · issue 045

    Tines adds AI credit alerts, case template API, LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. config UI, and AI Agent skills in a busy August rollout.

    • Adds Manage case templates via API capability under Cases and API surfaces, enabling programmatic control of case templates.
    • Adds Extend AI Agents with skills — new skill extension surface for AI Agents via Actions and Storyboard.
    • Adds Self-hosted LDAP configuration UI for self-hosted deployments, providing an admin UI for LDAP setup.
    • Adds Control which credentials can be used in Workbench — new admin control restricting credential availability in the Workbench AI environment.
    • Adds Customize AI credit usage alerts to let teams set thresholds for AI credit consumption notifications.

    +2 more show less

    • Adds Tines 3B workflows as case actions in Cases, allowing 3B workflows to be triggered directly as case actions.
    • Introduces Improved group change reviews under Change Control for reviewing group-level changes.

    7 details in Everything

51. Add Tines 3B workflows as case actions in Cases (2026-08-13) Aug 13, 2026 · issue 045

    Tines Cases can now trigger 3B workflows as case actions via a 3B service account connection.

    ⤢

    ⤢
52. changelog Aug 11, 2026 · issue 042

    Tines 42.6.0 adds LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. config UI, dashboard time granularity, time zone support in Cases, and Plan mode for Apps.

    ⤢ ⤢ ⤢ ⤢
    • Adds a self-hosted LDAP configuration UI, enabling on-premises deployments to configure LDAP directly from the Tines interface.
    • Introduces Plan mode for Apps, giving practitioners a way to model or preview app behavior before execution.
    • Adds time granularity controls to dashboard charts, allowing finer or coarser resolution when visualizing workflow data.
    • Enables setting a working time zone in Cases Records and dashboards for consistent time-aware case management.
    • Improves group change reviews, enhancing visibility and control over permission group modifications.

    5 details in Everything

53. 42.6.0 Aug 11, 2026 · release notes

    Tines 42.6 introduces self-hosted LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. UI, App mode switching, timezone support for Cases, and finer dashboard chart granularity.

    └──▷ HOW TO FIND IT
    Review LDAP group changes before they sync to ensure no unauthorized access is granted.
    📍In the Self-hosted LDAP configuration UI, inspect the Group change reviews section after saving updates.
    Set the correct local time for Case Records to align with regional teams.
    text copy

    In the Cases configuration, set the working time zone field to your region (e.g., 'America/New_York').

    Visualize dashboard data with finer granularity for short-lived incidents.
    📍Edit a dashboard chart widget and select the new time granularity options (e.g., 5m, 15m) from the axis settings.
    • improved Added group change reviews capability in the self-hosted LDAP configuration UI to verify group modifications before applying them
    • new Introduced App mode for Apps allowing users to switch between Plan and other modes via the App settings interface
    • new Added support to set a working time zone in Cases Records so dashboards and logs reflect the correct local time
    • improved Enhanced dashboard charts with improved time granularity control options for more precise data visualization

    4 details in Everything

54. New layout options for the case list (2026-08-05) Aug 5, 2026 · issue 036

    Tines adds reworked case list layout with more control over display options.

    ⤢

    ⤢
    • New layout options for the case list give users more control over what information is shown and how it is displayed.

    1 detail in Everything

55. changelog Aug 4, 2026 · issue 035

    Tines 42.3.0 adds dynamic SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure. management, JSON in records, find-and-replace in stories, and AI-generated story names.

    ⤢ ⤢ ⤢ ⤢
    • Manage SMTP settings dynamically without requiring static configuration changes.
    • Store and work with JSON natively inside Tines records.
    • Find and replace content across stories for bulk editing workflows.
    • AI-generated story names and descriptions to accelerate documentation.

    4 details in Everything

56. docs update Jul 31, 2026 · issue 031

    Tines introduces AI Agents: drag-and-drop reasoning agents for task execution and user interaction on the Storyboard

    • New AI Agents capability lets practitioners build autonomous agents directly on the Tines Storyboard without writing code, supporting both task-execution and chat/interaction modes.
    • Agents can reason over inputs, communicate with users via chat, and invoke tools (e.g., reset passwords, create cases, escalate to managers) as part of automated workflows.
    • Pre-built agent templates available in the Tines Library, including GitHub PR code review automation and employee offboarding access revocation across Gmail, Okta, and Slack.

    3 details in Everything

57. docs update Jul 31, 2026 · issue 031

    Tines launches Workbench: an AI chat interface that executes real-time actions and queries proprietary data via Tines Stories workflows.

    └──▷ HOW TO FIND IT
    Triage and remediate an identity incident by resetting a user's Okta password through a natural-language prompt — no manual console switching required.
    📍In Workbench, open a New chat and type: Reset Jennifer Browne's Okta password — Workbench looks up the user across connected platforms, runs the Reset password in Okta action, and returns a secure password reset link.
    • New Workbench AI chat interface lets practitioners issue natural-language commands (e.g., reset an Okta password, triage an incident) that execute live against connected systems via Tines Stories workflows.
    • Supports real-time access to proprietary data across the tech stack without data leaving the private architecture, being logged, or used for model training.
    • Enables security use cases including incident triage, threat enrichment, anomaly detection, compliance monitoring, and malicious IP blocking — all from a single chat interface.
    • Functions as a vendor-agnostic copilot that integrates with any tool in the tech stack, replacing siloed per-product copilots.

    4 details in Everything

58. docs update Jul 31, 2026 · issue 031

    Tines Stories adds Cases: automation-first incident case management with SLASLAA formal agreement between a service provider and customer that defines expected uptime, response times, and remedies for failures, giving cyber tools a contractual baseline for availability and support commitments. tracking, runbooks, and collaborative workspaces.

    └──▷ HOW TO FIND IT
    Use AI to automatically create a Tines Case and trigger remediation when a high-severity CrowdStrike alert is received.
    📍In the Tines story editor, use the 'Use AI to create cases and act on CrowdStrike alerts' template: connect CrowdStrike → Tines AI (normalize alert) → Cases (create case with AI-built ticket) → Okta/Zscaler/PagerDuty (remediation actions).
    Normalize alerts from multiple sources and automatically open a Case only when threat level is determined to be high.
    📍In the Tines story editor, use the 'Normalize alerts with Tines AI and create Cases' template: connect alert sources → Tines AI (analyze threat level) → Cases (create case if threat level == high).
    • Adds Cases, a collaborative incident case management workspace integrated directly into Tines Stories workflows.
    • Enables automated case creation from within existing workflows, with automatic tagging, priority setting, and assignment via a Cases bot.
    • Supports structured runbooks within cases, tracking step completion by assigned team members with a full audit trail.
    • Tracks case metrics including TTD and TTR against configurable SLA thresholds, aggregatable into dashboards.
    • Integrates with CrowdStrike, Okta, PagerDuty, and Zscaler to create and act on cases from third-party alerts.

    +2 more show less

    • Supports AI-powered case creation: uses Tines AI to normalize multi-source alerts, auto-build tickets, and initiate remediation steps for high-severity threats.
    • Allows cases to correlate with Tines Records, Pages, and any external API, enabling cross-team collaboration with DevOps, IT, and HROps workflows.

    7 details in Everything

59. docs update Jul 31, 2026 · issue 031

    Tines 3B launches as an AI-native platform with agents, sandboxed execution, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. support, and built-in governance.

    └──▷ HOW TO FIND IT
    Review and apply AI-suggested workflow improvements without deploying untested changes directly to production.
    📍In the console, open a workflow and navigate to the Autotune panel. Review the proposed changes on the generated branch, then merge or dismiss each suggestion before it reaches production.
    • New Tines 3B platform provides a single environment for building and running AI agents, apps, and automation workflows.
    • Supports natural-language prompt-based workflow creation, letting builders describe processes in plain English to start building.
    • Adds Chat mode for interactive work with a connected LLMLLMA large language model, a neural network trained on large amounts of text to recognize patterns and generate language. Applications use it for tasks such as answering, summarizing and writing code. to brainstorm projects and interact across systems.
    • Supports code-first workflow building with native Git integration and branching for development-process compatibility.
    • Introduces Spaces — isolated environments with dedicated connectors, skills, and permissions for safe team-level building.

    +17 more show less

    • Introduces Skills — reusable LLM-steered build patterns that enforce consistency across spaces at scale.
    • Adds Branches for change tracking and control over all edits made by teams or by Tines 3B itself.
    • Sandboxed execution isolates every workflow step as an independent compute unit, preventing lateral data exposure.
    • Connector credential injection via transparent proxy ensures secrets are never visible to builders, AI, or stored in code.
    • Adds Autofix, which identifies anomalies and potential workflow breaks and suggests targeted fixes.
    • Adds Autotune, which continuously monitors live workflows and proposes reliability, performance, and clarity improvements on a reviewable branch.
    • AI Spend dashboard provides governance and visibility over LLM provider and model spend across the organization.
    • Duplicates detection identifies redundant workflows to reduce token spend and environment sprawl.
    • Value configuration allows teams to attach detailed financial estimates to each workflow for ROI tracking.
    • Routes control gives administrators authority over how workflow frontends are accessed inside or outside the organization.
    • Dependencies view surfaces package dependencies to minimize disruption from changes.
    • Supports Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. (MCP) alongside standard APIs for vendor-agnostic, lock-in-free integrations.
    • Supports connection to external coding assistants such as Claude Code or Codex, using Tines 3B to run and monitor those sessions.
    • Deployment options include self-hosted, on-premises, and hybrid configurations with user-defined controls.
    • Includes Role-Based Access ControlRole-Based Access ControlRole-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists. (RBACRBACRole-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists.) and version control as built-in product security features.
    • Free Explore plan provides access to Tines 3B as the successor to the Community Edition on Tines Stories.
    • Test-as-you-build capability proposes tests during construction, generating dummy data and prompting before touching live data or apps.

    22 details in Everything

60. docs update Jul 31, 2026 · issue 031

    Tines adds a first-party MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server letting AI clients like Claude and Cursor author and modify stories via plain-language prompts.

    └──▷ HOW TO FIND IT
    Connect Claude Desktop to your Tines tenant so you can author stories from within your AI client using plain-language prompts.
    📍Add https://<your-tenant>.tines.com/mcp as an MCP server in your Claude Desktop or Cursor settings, then complete the OAuth consent screen titled Tines MCP server. Once connected, prompt your client: "Create a new story that polls CrowdStrike and posts alerts to Teams."
    • New built-in MCP server endpoint (https://<tenant>.tines.com/mcp) lets AI clients such as ChatGPT, Codex, Cursor, Claude Code, and Claude Desktop create and modify Tines stories via natural-language instructions.
    • OAuth-based authentication flow for MCP connections, replacing API-key access — with a consent screen that lists granted story-authoring capabilities.
    • All MCP tool usetool useA model's ability to answer with a structured request to run a named function or API, which the application executes and returns. It is how agents take actions. is recorded in Tines audit logs as MCP activity, giving security teams a full trail of AI-driven story changes.
    • Visiting https://<tenant>.tines.com/mcp in a browser surfaces a setup page with copy-ready configuration snippets for common AI clients.
    • Exposes Workbench story-building capabilities over MCP: reading and changing stories, creating and updating actions, validation, running actions, research helpers, and private template operations.

    5 details in Everything

61. docs update Jul 31, 2026 · issue 031

    Tines adds multi-provider AI configuration with team scoping, BYOA support, credit allocations, and Tunnel connectivity for on-prem AI services.

    └──▷ HOW TO FIND IT
    Restrict an expensive model (e.g., a Claude 3.5 Sonnet Bedrock deployment) to a specific team to control costs and compliance.
    📍In the Tines Settings Center, go to AI settings › AI providers, select your AWS Bedrock provider, and under Team scoping add only the teams that should have access. Leave other teams unscoped to block access.
    Connect a cloud Tines tenant to an internal private AI service without exposing it to the internet.
    📍In the Tines Settings Center, go to AI settings › AI providers › Add provider, configure your OpenAI-compatible endpoint, then expand Extra options and select a Tines Tunnel accessible by all teams.
    Prevent teams from exhausting shared AI credits by setting per-team spending limits for Workbench for Storyboard.
    📍In the Tines Settings Center, go to AI settings › AI credit allocations & limits › Workbench for Storyboard limits, then set a spending limit per team and a single limit to apply to each personal team.
    • Supports bring-your-own AI provider (OpenAI, Anthropic, Azure OpenAI, AWS Bedrock, xAI, Ollama, OpenRouterOpenRouterA unified API gateway that routes requests to dozens of LLM providers under one endpoint, letting cyber tools swap or compare models without rewriting provider-specific integration code., Helicone, and any OpenAI-compatible proxy) to power all Tines AI features.
    • Enables multiple AI providers within a single tenant, letting teams choose models per AI Agent action, Workbench conversation, and tenant-wide smart/fast model defaults.
    • Scopes AI providers to specific teams for cost control, compliance enforcement, and staged model rollouts.
    • Allows credentials and formula references in AI provider API key and header fields, avoiding raw secrets in provider configuration.
    • Supports custom certificate authorities when connecting to private AI services.

    +5 more show less

    • Enables AI provider connectivity through a Tines Tunnel, allowing cloud tenants to reach AI services on internal networks.
    • Adds per-team AI credit allocations and spending limits for AI actions, Workbench conversations, and Workbench for Storyboard usage.
    • Automatically applies prompt caching for Tines AI, OpenAI, Anthropic, and custom AWS Bedrock providers to reduce cost and latency.
    • Supports Azure OpenAI deployments via Azure AI Foundry with per-deployment URL model configuration and Azure API type selection.
    • Provides granular AI feature toggles per capability, including control over whether newly released AI features are enabled by default.

    10 details in Everything

62. docs update Jul 31, 2026 · issue 031

    Tines Workbench launches as an AI chat interface with tool execution, file attachments, case/event context, and team presets.

    └──▷ HOW TO FIND IT
    Surface a specific security event in Workbench for immediate AI-assisted triage, with live event data available in the chat.
    📍Use the WORKBENCH_LINK() formula in a Tines action to generate a link; when opened, Workbench launches a new chat pre-loaded with that event's real-time context.
    Pre-populate a Workbench chat with a ready-to-run prompt via a browser shortcut, useful for repetitive analyst queries.
    copy

    $ https://[your-subdomain].tines.com/workbench/?initialMessage=Show+me+all+open+critical+alerts

    Pre-configure a set of tools and credentials for a SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. team so all members get a consistent, ready-to-use Workbench environment.
    📍In Workbench, configure the desired templates, credentials, and stories in All tools view → click Create preset → select the team, assign a name, and optionally add custom instructions.
    • Introduces Workbench, a Tines-powered AI chat interface for running actions and querying live data across connected systems without data leaving the tenant.
    • Supports three tool types in Workbench conversations: Tines-provided Templates, custom Story workflows, and built-in Internal tools.
    • Adds built-in Internal tools including a Think scratchpad, a Code Analyst that generates and runs Python with inline visualizations, Formulas documentation Q&A, and web search with zero-data-retention processing.
    • Enables file attachments in chat (up to 3 files per message, 4.5 MB each) supporting PNG, JPEG, GIF, WEBP, PDF, CSV, MD, TXT, DOC, DOCX, XLS, XLSX, and YAML.
    • Allows any Workbench tool to return file outputs (images or documents) as base64-encoded inline content via a structured JSON response schema.

    +7 more show less

    • Adds chat history with search, rename, delete, and conversation reload.
    • Supports Custom Instructions that persist across all conversations and are applied per-message.
    • Enables sending a Case to Workbench via Load in Workbench with real-time case sync, and sending an Event via the WORKBENCH_LINK() formula function.
    • Adds one-click conversion of a Workbench chat into a reusable Story via the lightning icon in chat history.
    • Introduces Presets, allowing team admins to pre-configure a set of templates, credentials, stories, and custom instructions for consistent team-wide use.
    • Supports pre-populating the Workbench chat input via an initialMessage URL query parameter, enabling Chrome Site Search shortcuts.
    • Provides mobile chat support for iPhone and Android via tenant URL in a mobile browser, including Add to Home Screen for a native app-like experience.

    12 details in Everything

63. docs update Jul 31, 2026 · issue 031

    Tines adds Dashboards with charts, case views, MTTR/MTTA metrics, templates, and scheduled email snapshots.

    └──▷ HOW TO FIND IT
    Automatically send a weekly dashboard report to stakeholders who don't log in to Tines.
    📍In the dashboard toolbar, click Snapshots › Create new snapshot. Name it (e.g. Weekly dashboard report), add recipient email addresses, set frequency to every Monday with your timezone, choose which charts to include, then Save and enable the active toggle.
    Spin up a pre-built dashboard to monitor case metrics without starting from scratch.
    📍On the Dashboards page, open the help panel on the right-hand side, find the Templates section, and click Start with template on the desired template. Rename or edit the new dashboard as needed.
    • New Dashboards feature lets teams visualize records and case data in a single configurable view with chart, case view, and note components.
    • Records chart visualizations can be embedded in dashboards to display data captured via Records.
    • Dashboard templates are available from the help panel so teams can get started without building from scratch.
    • Dashboard Snapshots enable scheduled email delivery of dashboard charts to stakeholders on a configurable frequency and timezone, with per-snapshot recipient lists and chart selection.

    4 details in Everything

64. docs update Jul 31, 2026 · issue 031

    Tines introduces Records: structured, queryable tables that capture story data for trend analysis, dashboards, and audit trails.

    └──▷ HOW TO FIND IT
    Capture structured alert triage data from a story action so you can filter and chart alert volume, severity, and analyst verdicts over time.
    📍In the story editor, drag the Record tool from the tools menu onto the storyboard and connect it between the enrichment action and the downstream notification action. In the build pane, click Create new record, name the record type (e.g. Alert Triage), and add fields: source (text), severity (text fixed values: low/medium/high/critical), verdict (text fixed values: true_positive/false_positive), analyst (text), triaged_at (timestamp). Map each field to the relevant data from the incoming action, then click Save and Run.
    Reuse enrichment results for the same IOCIOCAn indicator of compromise, an observable clue that may point to malicious activity, such as a suspicious file hash or domain. It is evidence to investigate, rather than proof by itself. to avoid redundant URLScan/VirusTotal lookups and track which sources produce the most true positives.
    📍In the build pane of the Record tool, create a record type IOC Enrichment with fields: indicator (text), score (number), flagged_malicious (true/false), source (text fixed values: urlscan/virustotal). Connect the Record tool downstream of the enrichment action, map fields from the enrichment action output, and click Run. Navigate to Records in the top navigation to query and filter by source or flagged_malicious.
    Link child incident records to a parent alert record to model a one-to-many relationship between an alert and its sub-tasks.
    📍In the build pane of the child Record tool, toggle on parent record and use the formula field to reference the upstream parent record (e.g. the alert record captured earlier in the story). Ensure the parent Record tool is connected upstream of the child Record tool on the storyboard.
    • Adds Records, a new structured data capture tool that stores fields from story events into a queryable table — supporting text, number, true/false, timestamp, and fixed-value field types.
    • Supports Record artifacts for storing large raw data dumps (up to 15,000 characters each) directly within the Records table, visible in the UI and via API.
    • Enables parent-child record relationships to model dependencies between captured data sets across stories.
    • Provides a Records table with filtering by story, field values, date range, and test/live environment (with change control enabled).
    • Adds charting for Records reports with line, bar, pie, and stacked area chart types, plus rearrangeable/resizable chart grids with count, sum, or average aggregations.

    +2 more show less

    • Supports CSV export of any filtered Records table view.
    • Timestamps are normalized to %Y-%m-%d %H:%M:%S (strftime) regardless of input format at capture time.

    7 details in Everything

65. docs update Jul 31, 2026 · issue 031

    Tines adds Cases: a collaborative interface for incident triage, investigation, and reporting with records and dashboards.

    • Adds Cases, a collaborative workspace for organizing information, commenting, taking action, and reporting on security incidents and operational tasks in real-time.
    • Supports manual case creation via the UI or automatic case opening triggered by story automations.
    • Introduces case templates and an action template library for structured, repeatable workflows.
    • Adds Records for capturing, transforming, and referencing structured data within stories, linkable to specific cases for context.
    • Adds Dashboards to visualize data from records and cases in a unified view for cross-workflow monitoring.

    +2 more show less

    • Supports case notifications for real-time interaction with case content.
    • Enables use cases such as IOCIOCAn indicator of compromise, an observable clue that may point to malicious activity, such as a suspicious file hash or domain. It is evidence to investigate, rather than proof by itself. evaluation, observable management, AWS CLI-based investigation, and Azure VM deallocation workflows.

    7 details in Everything

66. docs update Jul 31, 2026 · issue 031

    Tines Resources gain locking, cross-team sharing, compare-and-swap updates, and per-element endpoints to prevent lost writes

    └──▷ HOW TO FIND IT
    Lock a critical shared Resource so no one can accidentally edit it mid-incident.
    📍In the Tines console, open the Resource modal and select Lock resource (top-right). To allow a one-time edit, click Unlock to edit; to release for all users, choose Permanently unlock from the dropdown.
    • Adds Resource locking so team admins can prevent edits to high-priority shared data, with temporary per-user unlock and permanent unlock options.
    • Enables cross-team Resource sharing — share with all teams in a tenant or with specific named teams, with same-name resolution favoring the story's own team.
    • Introduces append, replace, and remove element endpoints that update a single array element or object key server-side, avoiding lost updates from concurrent story runs.
    • Adds an optional if_value parameter to replace and remove endpoints for compare-and-swap (conditional) updates; returns a 422 with the current value if the condition is not met.
    • Supports Test Resource data via a Test Details tab, so stories with change control enabled can use draft-specific Resource values before promoting to live.

    +1 more show less

    • Exposes Resource access control through roles (Viewer, Editor, Team admin) and custom roles with granular Resources → Update and Resources → Manage permissions.

    6 details in Everything

67. docs update Jul 31, 2026 · issue 031

    Tines introduces Apps: AI-generated React front ends built on Workbench that connect directly to Tines workflows.

    └──▷ HOW TO FIND IT
    Reach the Apps builder to start generating a new React front end connected to your Tines workflows.
    📍In the Tines console, go to the main navigation › Apps, then click New to open the prompt-driven App builder.
    • New Apps feature lets practitioners build custom React applications in minutes using natural language prompts via Workbench, powered by one or more Tines story endpoints.
    • Apps expose full React codebase access, allowing customization of styling and package dependencies beyond what prompts generate.
    • Apps integrate directly with existing Tines workflows, data, and automations through configurable UI surfaces and app endpoints.
    • Apps section added to main Tines navigation with a gallery of previously created Apps and a New creation flow.

    4 details in Everything

68. docs update Jul 31, 2026 · issue 031

    Tines Pages lets you expose web forms and output views connected directly to your automation Stories.

    └──▷ HOW TO FIND IT
    Expose a form to kick off a workflow with user input — drag a Page onto the Story diagram and wire it to a downstream action.
    📍In the Tines story editor, open the Tools menu, drag a Page onto the diagram, then connect it to a downstream action to receive form submissions.
    • New Pages feature lets you create web pages connected to Stories so end users can submit forms, provide mid-workflow input, or view workflow output.
    • Supports requester/approver flows and end-to-end app building by chaining multiple Pages with existing actions.
    • Pages are added via drag-and-drop from the Tools menu and customized through a built-in page editor with selectable templates and configurable page elements.

    3 details in Everything

69. docs update Jul 31, 2026 · issue 031

    Tines adds MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. support for Apps, AI web search, user-level App access control, dashboard draft/edit mode, and chart time granularity controls.

    • Adds MCP (Model Context ProtocolModel Context ProtocolModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface.) support for Apps, enabling AI agent integration with Tines-powered workflows.
    • New AI web search capability lets workflows leverage live web results within Tines AI actions.
    • User-level access control for Apps allows fine-grained permissions management per user on individual Apps.
    • Dashboard draft and edit mode lets practitioners build and stage dashboard changes before publishing.
    • Control time granularity in dashboard charts for more precise visibility into workflow performance trends.

    +2 more show less

    • Apps analytics in chat surfaces App usage and performance data directly in the chat interface.
    • Hardened foundation for the tines-app self-hosted image improves the security baseline for self-hosted deployments.

    7 details in Everything

70. MCP support for Apps (2026-07-31) Jul 31, 2026 · issue 031

    Tines MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server now supports Apps, enabling clients to modify, preview, and publish Apps programmatically.

71. 42.3.0 Jul 28, 2026 · release notes

    Tines 42.3.0 adds dynamic SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure. configuration, record field find-and-replace, AI metadata generation, and JSON-in-records exploration.

    • Manage SMTP settings dynamically at runtime without restarting the service
    • Perform find-and-replace operations on fields within JSON in records nodes directly in the story editor
    • Generate AI-assisted story names and descriptions during creation to accelerate workflow drafting

    3 details in Everything

72. changelog Jul 27, 2026 · issue 027

    Tines 42.2.0 adds API key creation restrictions and template-based case creation via API.

    • Adds the ability to restrict which users can create API keys.
    • Enables creating cases from a template via the API.

    2 details in Everything

73. docs update Jul 27, 2026 · docs issue 004

    Tines 42.2.0 adds API key creation restrictions and template-based case creation via API.

    • Adds the ability to restrict which users can create API keys.
    • Enables creating cases from a template via the API.

    2 details in Everything

74. AI web search (2026-07-24) Jul 24, 2026 · issue 025

    Tines AI Agent actions and Workbench can now search the web, powered by Parallel.ai.

75. JSON in records (2026-07-21) Jul 21, 2026 · issue 022

    Tines Records now supports a JSON field type for storing structured data alongside other record fields.

    • Adds a JSON field type to Records, enabling structured data to be stored directly within a record.

    1 detail in Everything

76. Track cases with change control in the storyboard (2026-07-20) Jul 20, 2026 · issue 021

    Tines extends change control to cover all case elements defined in the storyboard.

77. Formula support for case details (2026-07-20) Jul 20, 2026 · issue 021

    Tines cases now support formulas across every case property, primitive, and case content field from the storyboard.

    • Enables formula expressions across all case properties, primitives, and case content when defining cases from the storyboard.

    1 detail in Everything

78. Visually create cases in the storyboard (2026-07-20) Jul 20, 2026 · issue 021

    Tines lets you visually configure case creation and write rich-text descriptions directly in the storyboard editor.

    └──▷ HOW TO FIND IT
    When building a case-creation workflow, configure all case fields and format the description visually without leaving the storyboard.
    📍In the storyboard, add a Create Case tile, then use the visual editor to define case fields and apply rich-text formatting to the description and block content.
    • Enables visual definition of all case fields when building with the create case tile in the storyboard.
    • Supports rich-text formatting for case descriptions and block content within the storyboard editor.

    2 details in Everything

79. Visually create cases in the storyboard (2026-07-20) Jul 20, 2026 · release notes

    Tines adds a storyboard editor to visually define cases with rich-text support.

    └──▷ HOW TO FIND IT
    Use the visual editor to define case parameters and format content without writing code.
    📍In the storyboard, add a create case tile and open its configuration to visually set fields and use the rich-text editor for the description.
    • Adds visual case definition capability directly in the storyboard using the create case tile
    • Enables rich-text formatting for case descriptions and block content within the visual builder

    2 details in Everything

80. Restrict who can create API keys (2026-07-16) Jul 16, 2026 · issue 017

    Tines lets tenant owners restrict which users can create API keys via a new tenant-level setting.

    └──▷ HOW TO FIND IT
    Lock down API key creation to prevent non-owner users from generating credentials.
    📍In the Tines console, go to Settings › API keys and enable the restriction option under the tenant settings section.
81. Reuse recent App endpoint responses (2026-07-14) Jul 14, 2026 · issue 015

    Tines App endpoints can now cache and reuse recent responses for identical requests, cutting latency and redundant story runs.

    • Enables response reuse on App endpoints so identical incoming requests return a cached result without re-executing the story.

    1 detail in Everything

82. Find and replace in stories (2026-07-14) Jul 14, 2026 · issue 015

    Tines adds find-and-replace across entire stories for faster bulk edits.

    └──▷ HOW TO FIND IT
    Bulk-update a hostname, credential name, or URL that appears across many actions in a story without editing each one individually.
    📍In the story editor, open Find and Replace, enter the text to find and the replacement text, then apply to update all matching instances across the story.
    • Adds find-and-replace functionality to search and update text throughout an entire story at once.

    1 detail in Everything

83. Interact with apps directly from a case (2026-07-07) Jul 7, 2026 · issue 014

    Tines now lets you trigger app actions directly from within a case, without leaving the case view.

    └──▷ HOW TO FIND IT
    Trigger an app (e.g., send a Slack message or create a Jira ticket) without leaving an active case.
    📍In the case view, open the Case Actions menu and select the app you want to interact with.
    • Enables running apps directly from a case via case actions, keeping response workflows in context.

    1 detail in Everything

84. Filter and sort by Record ID (2026-07-06) Jul 6, 2026 · issue 014

    Tines adds Record ID filtering and sorting to records tables and charts.

    └──▷ HOW TO FIND IT
    Quickly locate a specific record or range of records by ID when triaging a large records table.
    📍In the Tines console, open your Records table or chart, select the Filter option, choose Record ID as the filter field, enter your target ID or range, then apply Sort by Record ID to order results.
85. User read and manage tenant permissions (2026-07-01) Jul 1, 2026 · issue 014

    Tines adds two new tenant permissions for finer-grained user management control.

86. 41.6.0 Jun 30, 2026 · release notes

    Tines 41.6.0 adds search text field contents, story duplication, Dashboard other grouping, and Tines MCP ServerMCP ServerA process that exposes tools, resources, and prompts over Anthropic's Model Context Protocol, letting an AI agent call external APIs or local services through a standardised interface. support.

    • Adds the ability to perform search text field contents of a record
    • Adds Story duplication capability
    • Adds Dashboard series limit and other grouping feature
    • Adds Tines MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. Server integration

    4 details in Everything

87. Query and aggregate records from the storyboard (2026-06-23) Jun 23, 2026 · issue 014

    Tines storyboard record action gains a Query mode for running aggregations directly on record types.

    └──▷ HOW TO FIND IT
    Aggregate record data inline during a workflow — e.g. count open alerts by severity — without a separate lookup step.
    📍In the storyboard, add or open a Record action, select the target record type, then switch the mode to Query and configure your aggregation expression.
88. 41.5.0 Jun 23, 2026 · release notes

    Tines 41.5.0 adds story syncing API improvements and manual sync mode

    • Introduces improved Story syncing API endpoints for greater control over record type synchronization.
    • Adds manual sync mode for Story Syncing, allowing operators to trigger data transfers on demand rather than relying solely on automatic intervals.

    2 details in Everything

89. 41.4.0 Jun 16, 2026 · release notes

    41.4.0 introduces tunnel support for AI providers, Cases API resolve mentions, Case status API, and lock sections in Storyboard.

    • Adds Tunnel configuration option to support proxy connectivity for Anthropic and Bedrock integrations
    • New resolve_mentions capability in the Cases API allowing users to mark case mentions as resolved
    • New GET /api/v1/case/{id}/status endpoint exposed by the Case status API
    • Adds visual lock sections in the Storyboard Workbench UI to prevent unintended modifications
    • Supports Claude Fable 5 models through custom Bedrock and Anthropic provider configurations

    5 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !Version 41.4.0 is deprecated in favor of 41.6.6 and will no longer receive support.
90. 41.3.0 Jun 9, 2026 · release notes

    Tines 41.3.0 adds AI usage tracking via API, chart legend control, and cross-team record types.

    • Track AI usage and costs via the API
    • Charting improvements include control chart legend visibility and accessible color styles
    • Record type schema explorer in Workbench
    • Templates are now available in quick search
    • Share record types across teams

    5 details in Everything

91. 41.0.0 May 19, 2026 · release notes

    41.0.0 deprecated; introduces global date filter for dashboards and changes records API response format

    └──▷ HOW TO FIND IT
    Restrict dashboard data to a specific time range using the new global filter
    📍In Workbench, open your Dashboard and select Global date filter from the top bar to set your desired range.
92. 40.7.2 May 15, 2026 · release notes

    Case group members can now use case templates from their parent team

    └──▷ HOW TO FIND IT
    Allow a junior analyst (case group member) to initiate an incident using the organization's standard playbook (parent team template) without manual setup.
    📍In the Tines console, navigate to the Case Group you belong to, click Create Case, and select a template from your parent team's list.
93. 40.7.0 May 12, 2026 · release notes

    Tines 40.7.0 adds nested folders, Case permissions, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. support, and new record export/filtering capabilities.

    • Introduces nested folders to organize workspace content hierarchically
    • Adds block remote images in case content to prevent external resource loading
    • Enables fine-grained permissions for Cases to control access at a granular level
    • Adds MCP tool support for Workbench to integrate with MCP-compatible clients
    • Implements multiplayer editing for Cases allowing concurrent user interaction

    +2 more show less

    • Adds the ability to match saved views when exporting CSVs from Cases
    • Enables ordering and filtering records by Updated at timestamp

    7 details in Everything

94. 40.6.0 May 5, 2026 · release notes

    Tines 40.6.0 replaces child_record_ids with child_records in Record GET tile responses.

    • GET /api/v1/records/:id now returns the child_records field instead of child_record_ids.

    1 detail in Everything

    └──▷ BREAKING ON UPGRADE

    • !The GET /api/v1/records/:id endpoint no longer returns child_record_ids; callers must switch to reading the new child_records field.
95. 40.5.1 Apr 29, 2026 · release notes

    Tines 40.5.1 adds custom AI provider support with full API URLs, story filtering updates, and new integrations like case linking from mentions.

    └──▷ HOW TO FIND IT
    Attach a file to a Story copilot interaction directly from the story notes interface.
    📍Open Story Notes › Attach File
    • Supports full API endpoint URLs for custom AI providers via Anthropic through Google Vertex GPT
    • Adds Story copilot file attachments to allow attaching files within story notes

    2 details in Everything

96. 40.4.0 Apr 21, 2026 · release notes

    Tines 40.4.0 adds AI output truncation controls, OBJECTS_TO_MARKDOWN_TABLE, YAML support in Workbench Claude Opus, and live logs in drafts

    └──▷ USE IT
    Convert complex nested data structures into readable Markdown tables within your workflows.
    text copy

    {% set result = OBJECTS_TO_MARKDOWN_TABLE(data_object) %}

    • Claude Opus 4.7 now available in Tines AI tool
    • Adds output truncation controls to the AI tool
    • New OBJECTS_TO_MARKDOWN_TABLE function
    • Live logs now available in drafts

    4 details in Everything

    └──▷ BREAKING ON UPGRADE

    • !This version is deprecated in favor of 40.4.1 and should not be used for new deployments.
97. 40.1.0 Mar 31, 2026 · release notes

    Tines 40.1.0 introduces PAD_LEFT and PAD_RIGHT string functions, remote MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server OAuth integration, and a tenant health dashboard.

    • Adds PAD_LEFT function to pad strings on the left side
    • Adds PAD_RIGHT function to pad strings on the right side
    • Enables connecting AI Agent actions to remote MCP Servers using OAuth authentication
    • Adds a Tenant health dashboard view for monitoring system status

    4 details in Everything

98. 40.0.0 Mar 24, 2026 · release notes

    Tines 40.0.0 renames Trigger action to Condition action, adds dashboard import/export API and records action improvements

99. 39.5.0 Mar 17, 2026 · release notes

    Tines 39.5.0 adds AI story copilot, private template support, record report time filters, and resources API locking.

    • Adds Custom time range filters for record reports
    • Enhances Resources API with locking and conditional updates

    2 details in Everything

100. 39.4.0 Mar 10, 2026 · release notes

     Tines 39.4.0 adds META header access and a DELETE /story-links API endpoint

     • Adds the META object to context variables for easily referencing HTTP headers in story steps

     1 detail in Everything

101. 39.3.0 Mar 3, 2026 · release notes

     Tines 39.3.0 adds case field groups, storyboard sections, team-scoped templates, and multi-team API keys.

     └──▷ HOW TO FIND IT
     Organize complex workflows by adding sections to the storyboard for better visual grouping.
     📍steps: In the Tines Storyboard, click Add Section on the left panel and drag nodes into the new section group.
     • Adds Case field groups to organize fields in the web UI.
     • Adds Storyboard sections to group nodes in the workflow editor.
     • Enables Team scoped private templates for restricting template visibility by team.
     • Supports Multi-team API keys for cross-tenant authentication.

     4 details in Everything

102. 39.2.0 Feb 24, 2026 · release notes

     Tines 39.2 adds Mistral AI integration and allows passing parameters to private templates via the API.

     • Adds Mistral AI as a supported model provider for AI capabilities within Tines workflows.
     • Enables passing parameters to private templates through the API, allowing dynamic configuration of restricted templates programmatically.

     2 details in Everything

103. 38.5.0 Feb 17, 2026 · release notes

     Tines 38.5.0 introduces story copilot and configurable case sidebar.

     • Introducing story copilot
     • Append to existing content using the Cases API

     2 details in Everything

104. 38.4.0 Jan 27, 2026 · release notes

     Tines 38.4 introduces individual event path tracking and enhanced case saved view sharing.

     • Enables tracking of individual event paths within workflows
     • Improves the mechanism for sharing saved views of cases

     2 details in Everything

105. 38.3.0 Jan 20, 2026 · release notes

     Tines 38.3.0 adds new transition_status permission, GROUP_BY array support, action shortcuts, and selective webhook notifications.

     • Adds Transition case status as a new granular permission for controlling who can change case workflows
     • Enhances GROUP_BY block to return an array of presence indicators for grouped items
     • Adds keyboard shortcut (d) to disable or enable actions directly within the workflow editor
     • Introduces support for multiple webhooks in a Case with selective notification settings

     4 details in Everything

106. 38.1.0 Jan 6, 2026 · release notes

     Tines 38.1.0 adds max segments for Mermaid charts, auto-ignored fields in Test Runs, and no-match event emission in Extract mode.

     • Supports setting a maximum number of segments for Mermaid bar and pie diagrams to control visual density
     • Automatically excludes specified fields from Test Run output to reduce noise
     • Emits system events when an Extract node matches no records, enabling downstream handling of empty results

     3 details in Everything

107. 38.0.0 Dec 16, 2025 · release notes

     Tines 38.0 introduces MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. tool integration for AI Agents, Multi Request secret formatting, and new dashboard UI features.

     └──▷ HOW TO FIND IT
     Connect an AI Agent to a local MCP server via tunnel for secure tool invocation.
     📍In the Workflow builder, add an AI Agent action and set its protocol to MCP. Enable the tunnel option to connect to the target agent.
     Use Multi Request actions where secret values contain newlines without data corruption.
     📍Create a Multi Request node. Configure the credential secrets field; the system now preserves embedded newlines in the stored Workbench memory value.
     Investigate tenant health metrics by interacting with dashboard charts directly.
     📍Open the Tenant health page in the Tines console. Click on any metric within a Dashboard chart to drill down into the underlying data points.
     • tunnel support added for AI Agent action when invoking MCP tools
     • Multi Request credential secrets now preserve newlines in the Workbench memory
     • Dashboard chart drill-down capability added to the Tenant health page

     3 details in Everything

108. 37.2.0 Dec 2, 2025 · release notes

     Tines 37.2.0 adds rich text callouts to cases, improved case search/saved views, and image digests for self-hosted builds

     • Adds Rich Text callouts in Cases allowing formatted informational or warning blocks within case items.
     • Improves case search with enhanced filtering options for faster retrieval of specific incidents.
     • Allows saved views for case search results to be persisted and reused across sessions.
     • Publishes image digests for self-hosted build bb3a75b7_v37_2_0 in the tines/tines-app, tines-command-runner, and tines-nginx repositories.

     4 details in Everything

109. 37.1.0 Nov 25, 2025 · release notes

     Tines 37.1.0 adds MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server tools to AI Agent actions, Slack integration for those actions, and Story record limit increases.

     • Increases Story record limits to 50 fields and 100 validation options.
     • Enables testing story runs with a dynamic Use tunnel field.
     • Adds support for using tools from MCP servers in AI Agent actions.
     • Enables use of AI Agent actions within Slack workflows.

     4 details in Everything

110. 37.0.0 Nov 18, 2025 · release notes

     Tines 37.0.0 introduces build image digests, Postgres bigint support via built-in btree_gin, and filter/toggle UI controls

     • Adds tines/tines-app, tines/tines-command-runner, and tines/tines-nginx images tagged with specific sha256 digests (e.g. sha256:bb370f47de906ba027fbb7994d9fe7c13ff3945c52732cc13b9726052c22a0c4) for reproducible builds

     1 detail in Everything

111. 36.2.0 Nov 11, 2025 · release notes

     Tines 36.2 adds MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server support for AI Agent actions.

112. 36.1.0 Nov 4, 2025 · release notes

     Tines 36.1 introduces manual record creation, page branding headers, and AWS Bedrock provider configuration.

     └──▷ USE IT
     Manually populate a specific Record Type instance via the API without triggering a flow.
     api copy

     PATCH /api/v1/record-types/{record_type_id}/records
     Content-Type: application/json
     
     {
       "data": {
         "field_key": "value"
       }
     }

     Add custom headers to Page branding in the Tines console.
     📍In the Pages editor, go to Branding › Custom Headers and enter your key-value pairs.
     Configure the AWS Bedrock AI provider for use in automated connect flows.
     📍In Connect Flows, select AWS Bedrock as the provider type and configure the region and credentials in the connection settings.
     • Update Record Type API adds a method to manually create a record within a Record Type

     1 detail in Everything

113. 36.0.0 Oct 28, 2025 · release notes

     Tines 36.0 adds Anthropic header/Base URL config and Story metadata in Send to Story input; moves tines-app-fips to distroless.

     • Adds configuration fields for headers and base URL to the Anthropic AI provider integration
     • Send to story input action now includes metadata about the calling Story

     2 details in Everything

114. 34.8.0 Oct 13, 2025 · release notes

     Tines 34.8.0 enables uploading files directly within AI Agent chat pages.

     └──▷ HOW TO FIND IT
     Upload a document to an AI Agent for analysis directly from the chat interface.
     📍In the AI Agent chat page, use the file upload control to attach your document.
     • Adds the ability to upload files into AI Agent chat pages

     1 detail in Everything

115. 34.7.0 Oct 8, 2025 · release notes

     Tines 34.7 adds diagram navigation, live activity tracking, Run/Event Transform access control, and OTelOTelAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. traces for self-hosted deployments

     └──▷ HOW TO FIND IT
     Navigate instantly from a specific story run instance to its corresponding flow diagram node for debugging.
     📍Open Story Run › Click the Jump to Route link in the action header
     Monitor real-time execution of pending actions across multiple story runs without refreshing pages.
     📍Navigate to Stories › Select Story › Open Live Activity tab
     • Adds direct jump from a story run to its route in the diagram UI.
     • Introduces live activity view for pending action runs within stories.
     • Adds ability to restrict access to Run Script and Event Transform actions when running in automatic mode.
     • Enables exporting OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. traces for self-hosted Tines installations.

     4 details in Everything

116. 34.6.0 Oct 6, 2025 · release notes

     Tines 34.6.0 adds visual theme management, assignable case tasks, and configurable story timeouts.

     └──▷ HOW TO FIND IT
     Change the visual appearance of your Tines workspace without editing CSS.
     📍Navigate to Settings › Themes in the console to apply a new visual theme.
     Ensure specific users are responsible for handling incidents within a Case workflow.
     📍Open the Cases interface, locate the task, and assign it to the target user.
     Prevent slow external integrations from blocking story execution by limiting wait time.
     📍Edit the Send-to-Story tool configuration and set the timeout value to your desired duration (e.g., 30s).
     • Manage page themes visually through the UI
     • Assign tasks to specific users in Cases
     • Configure Send-to-Story tool timeouts

     3 details in Everything

117. 34.3.1 Sep 17, 2025 · release notes

     New include_referencing_action_ids parameter for the resources API to control response payload size.

     • Includes various performance improvements around shared credentials, resources & stories

     1 detail in Everything

118. 34.3.0 Sep 15, 2025 · release notes

     Tines 34.3.0 adds audit log export to S3, bulk case linking, multiple dashboard snapshots, and AI agent paste support.

     • Enables audit log export directly to an Amazon S3 bucket for centralized logging
     • Allows linking multiple cases to a specific target case in bulk from the Cases toolbar
     • Adds the ability to take and manage multiple dashboard snapshots for historical comparison
     • Improves Storyboard views for story runs with clearer visual feedback
     • Supports conditional color styles on dashboards for dynamic data visualization

     +1 more show less

     • Adds contextual help tooltips accessible directly from UI elements where they are needed

     6 details in Everything

119. 34.2.0 Sep 8, 2025 · release notes

     Tines 34.2.0 adds ability to reorder case statuses in the Cases HTML block

     └──▷ HOW TO FIND IT
     Reorganize the display order of case statuses within a custom HTML block in your Tines workflow.
     📍In the Cases HTML block configuration, use the new reorder controls to drag-and-drop status items into the desired sequence.
120. 34.1.0 Sep 1, 2025 · release notes

     Tines 34.1.0 adds idle timeout for chat, AI agent monitoring, formula generation, and Workbench pre-population.

     • Adds idle_timeout configuration to enable automatic disconnect in Tines chat mode
     • Introduces a median aggregation function available for use in dashboard calculations
     • Enables auto-generation of formulas within the Tines interface
     • Pre-populates Workbench chat sessions via URL parameters
     • Adds monitoring capabilities for AI Agent actions

     5 details in Everything

121. 34.0.0 Aug 26, 2025 · release notes

     Tines 34.0.0 adds Select AI model, Code Analyst, Case list saved views, API for story runs, and new JWTJWTAn open standard (RFC 7519) for encoding claims as a signed, optionally encrypted JSON object passed between parties. Cyber tools use it to verify identity and permissions without querying a central session store./JWK functions

     • Adds the ability to select the AI model used in Workbench flows via a new configuration option
     • Introduces Code Analyst as an available action within AI Agent workflows
     • Includes Case list columns in saved views, allowing persistent column selection for case management
     • Adds API support for saving story runs, enabling programmatic persistence of execution results
     • Adds Accept all incoming changes option for handling updates to shared configurations or stories

     +3 more show less

     • Includes pending_duration in action metadata for tracking wait times in Agent actions
     • Adds JWK_TO_PEM and PEM_TO_JWK functions for cryptographic key format conversion
     • Adds JWT_DECODE function for decoding JSON Web Tokens directly in workflows

     8 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !Deprecation of Docker Content Trust in favor of cosign; users must update their image verification process
     • !Images move to the distroless model; base OS layers are removed from official Tines images
122. 32.7.0 Aug 11, 2025 · release notes

     Tines 32.7.0 adds AWS Bedrock integration, MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server building, embedded pages in collections, and action metadata

     • Use your own AWS Bedrock in Tines cloud
     • Close submitted pages immediately
     • Building MCP servers in Tines
     • Action duration metadata is available

     4 details in Everything

123. 32.6.0 Aug 4, 2025 · release notes

     Tines 32.6.0 adds pre-filtering to HTTP/Transformation actions, granular dashboard permissions, case template 2.0, and UI-driven Pages loops.

     • Pre-filter events directly on HTTP Request and Event Transformation actions to reduce downstream processing.
     • Apply granular dashboard permissions via the UI to control which users can view or edit specific dashboards.
     • Configure cases with improved action configuration options for more complex workflows.
     • Connect external systems using native Webhooks support within Tines flows.
     • Manage access with Tines API keys for programmatic interaction.

     +1 more show less

     • Build User-driven looped elements directly in the Pages UI for interactive forms.

     6 details in Everything

124. 32.5.0 Jul 28, 2025 · release notes

     Tines 32.5.0 adds email message capture, HTTP pagination, tunnel filtering, case monitoring, and UI enhancements.

     • Adds raw_message field to Send Email action to capture outgoing payload for debugging
     • Increases cases file upload limit from previous default to 60 MB
     • Adds pagination controls (page/size parameters) to HTTP Request Action Workbench for list endpoints
     • Enables filtering of stories by active tunnel status in the console API
     • Adds Select All checkbox to events table in the console for bulk operations

     +2 more show less

     • Delivers detailed action run failure notifications via email with error context and stack traces
     • Adds Case Activity Monitor dashboard view to track recent case modifications and assignments

     7 details in Everything

125. 32.4.0 Jul 22, 2025 · release notes

     Adds custom options for the when failure occurs action trigger in Tines workflows

     • Introduces the ability to specify custom_options when configuring an action's failure behavior.

     1 detail in Everything

126. 32.3.0 Jul 14, 2025 · release notes

     Tines v32.3.0 adds case file metadata API, code diff view for run script actions, and story-level change request approvals

     • Adds API endpoints to retrieve file metadata on cases
     • Introduces a code diff view in the run script action editor
     • Enables required change request approvals at the story level

     3 details in Everything

127. 32.1.0 Jul 1, 2025 · release notes

     Tines v32.1 adds Governance settings, Story/StoryOwner APIs, mock payload re-runs, and network controls for Run Script

     • Exposes a new API endpoint for managing story monitoring recipients
     • Exposes a new API endpoint for retrieving story owners
     • Enables re-running saved story runs using mock payloads via the UI or API
     • Requires a reason message when bypassing approvals in change control
     • Adds advanced page element condition rules for workflow logic

     +2 more show less

     • Makes networking options for run_script actions available to all cloud tenants
     • Adds a no networking mode for run_script actions

     7 details in Everything

128. 32.0.0 Jun 24, 2025 · release notes

     Tines 32.0.0 adds team/case-group dashboard duplication and upstream-triggered run triggers.

     • Duplicating dashboards within teams and case groups
     • Trigger actions with upstream events

     2 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !The action performance widget in reporting is sunset.
     • !The GET /api/v1/reporting/action_performance API is sunset.
129. 31.5.0 Jun 17, 2025 · release notes

     Tines 31.5.0 adds tunnel egress control, live/test mode records, image uploads in cases, and new dashboard/charting features.

     • Adds Action egress control for tunnels to restrict outbound traffic from automation flows
     • Enables Direct image upload in cases notes or description for richer case documentation
     • Introduces Cases group block type to aggregate and display multiple case records visually

     3 details in Everything

130. 31.4.0 Jun 9, 2025 · release notes

     Tines 31.4 adds dashboard snapshot scheduling, custom Anthropic models, and more upcoming actions view

     └──▷ HOW TO FIND IT
     Automate regular exports of dashboard state for reporting or backup.
     📍In the UI, schedule a Dashboard snapshot action to export automatically on your desired cadence.
     • Adds scheduled export of Dashboard snapshots

     1 detail in Everything

131. 31.3.1 Jun 2, 2025 · release notes

     Tines 31.3.1 adds personalized story suggestions, ordered bar charts, new webhook fields, and AI provider configuration with formulas.

     • Adds personalized story suggestions for users to discover relevant automations
     • Enables configuring AI providers using credentials and formula inputs in the UI
     • Supports ordered bar charts in dashboard widgets for controlled data visualization

     3 details in Everything

132. 31.2.6 May 27, 2025 · release notes

     Tines 31.2.6 adds OpenAI tenant-level timeout, enhanced Events Search filters, throttle/delay event handling, and editor navigation improvements.

     • Adds tenant level timeout configuration for OpenAI integrations
     • Adds custom date and time filters to the Events Search interface
     • Filters events by re-emitted events in Throttle and Delay event transform actions
     • Shows a Re-emitted events badge on event cards
     • Enables navigation between connected pages directly within the workflow editor

     5 details in Everything

133. 31.1.2 May 20, 2025 · release notes

     31.1.2 adds unprivileged Nginx container and TINES_NGINX_IMAGE env var

     • Introduces TINES_NGINX_IMAGE environment variable to specify the Nginx image used by the Tines platform.

     1 detail in Everything

134. 31.1.0 May 13, 2025 · release notes

     Tines 31.1.0 adds AI formula config, case search filters, webhook path prefixes, and looping page elements

     • Configure AI model with a formula allows dynamic selection of AI models in Workbench.
     • API path prefixes for webhooks enables naming consistency across services without changing the underlying endpoint.
     • Looping page elements lets you repeat inputs or outputs on custom pages.
     • Cases search: Subscribed filter adds a new filter option to find cases you follow.

     4 details in Everything

135. 31.0.0 Apr 28, 2025 · release notes

     Tines 31.0.0 adds Rich text comments in Cases, custom AWS Bedrock models, and CASE_BLOCK_LIMIT config.

     • Adds CASE_BLOCK_LIMIT environment variable to control the maximum number of blocks per case for self-hosted runners
     • Supports using custom models with the AWS Bedrock AI provider
     • Enables rich text comments in Cases

     3 details in Everything

     └──▷ BREAKING ON UPGRADE

     • !Version 31.0.0 is deprecated in favor of 31.0.1; users should upgrade to the newer release immediately.
136. 30.3.4 Apr 23, 2025 · release notes

     Tines 30.3.4 adds DATABASE_SCHEMA and DATBASE_SCHEMA_SEARCH_PATH env vars for Postgres schema configuration.

     └──▷ HOW TO FIND IT
     Run Tines on a custom Postgres schema instead of the default public schema.
     📍DATABASE_SCHEMA=my_custom_schema DATBASE_SCHEMA_SEARCH_PATH='"$user", my_custom_schema' docker run ...
     • Adds DATABASE_SCHEMA environment variable to specify the Postgres schema for Tines data.
     • Adds DATBASE_SCHEMA_SEARCH_PATH environment variable to configure the Postgres search path.

     2 details in Everything

137. 30.3.1 Apr 14, 2025 · release notes

     Tines 30.3.1 adds case blocks, private templates, draft webhooks, search API, and Workbench text generation controls

     • Adds case_blocks to define additional case structures within a story.
     • Adds mention_files support to link files directly within a case.
     • Enables configuring an API webhook via the Stories API for automated integration.
     • Adds reorder_pages capability to move pages within a collection directly.
     • Adds stop_text_generation flag in Workbench to halt running AI text generation.

     +3 more show less

     • Introduces private_templates that can be created and cloned within Workbench.
     • Enables running webhooks for all draft versions simultaneously via the new run endpoint.
     • Adds search_stories_api endpoint to query the story list programmatically.

     8 details in Everything

138. 30.2.0 Mar 31, 2025 · release notes

     Tines 30.2 adds story API workbench controls, webhook rule formula evaluation, and JSON data item counts in the event console.

     • New POWER function available in formula evaluation
     • RSA_SIGN function added to formula capabilities

     2 details in Everything

139. 30.1.0 Mar 17, 2025 · release notes

     Tines 30.1.0 adds CONST_EQUALS and median functions, file import drag-and-drop, and story runs API filtering

     • Adds CONST_EQUALS function for static value comparison in stories
     • Adds median aggregation function to data processing blocks
     • Enables drag and drop of files directly into Story canvas to trigger file import workflow

     3 details in Everything

140. 30.0.0 Mar 10, 2025 · release notes

     Tines 30.0 introduces Workbench containers, gRPCgRPCAn open-source remote procedure call framework from Google that uses HTTP/2 and Protocol Buffers to let services call each other's functions across a network, giving tools low-latency, strongly typed inter-process communication. support, new formula functions, and scoped tags.

     └──▷ HOW TO FIND IT
     Send an HTTP request including the original URL's query parameters
     📍HTTP Request Action with Query params option enabled
     • Adds GROUP_BY support for LAMBDA expressions in change control draft details
     • Adds configurable columns on the Stories table via UI preferences
     • Adds IN_CIDR function that now takes an array of addresses
     • Adds TO_SNAKE_CASE function supporting conversion from camel case
     • Adds IS_YAML strict mode for validation

     +21 more show less

     • Adds support for gRPC requests in actions
     • Adds Records action with list mode
     • Adds CAMELIZE formula function
     • Adds Amazon Nova models availability in the AI action
     • Adds new Claude 3.7 Sonnet model powered by Workbench
     • Adds Team scoped tags for resource organization
     • Adds detachable change request modal UI element
     • Adds Slider element for pages layout
     • Adds Query params option for HTTP Request Action
     • Adds Capture raw body option for Webhooks
     • Adds Edit workbench presets capability
     • Adds Share workbench conversations feature
     • Adds Case file attachment block for Cases UI
     • Adds Cases block API endpoints for programmatic access
     • Adds Events search: scroll through results in Workbench
     • Adds ability to refer to URL query parameters in pages
     • Adds Send to story action featuring the story icon
     • Adds Rewinding Workbench conversations feature
     • Adds Storyboard header redesign UI update
     • Adds Improved user filtering for resources API
     • Adds API endpoint to monitor web server health

     26 details in Everything