Strong security and effective monitoring are critical for maintaining trust, minimizing risk, and ensuring reliable operations in Tines. This guide outlines key best practices for audit logging and alerting, helping teams stay proactive and secure in their automation flows.

If applicable, forward all of your audit logs to your SIEM tool. We recommend using your SIEM tool to generate appropriate alerts and pipe alerts back to Tines to take action on.

Sending audit logs to your SIEM centralizes visibility and allows your security team to detect and respond to activity in real time. It also supports compliance requirements and enables historical investigation when needed.

Send action/story monitoring alerts to a Tines story that alerts builders on failures in their stories. Monitoring alerts help teams quickly identify and fix issues in their stories. Routing those alerts into a Tines story keeps the response automated and ensures failures don’t go unnoticed.

We recommend building a story to monitor audit logs for unusual activity. This adds an extra layer of automated threat detection, especially useful for large teams or high-security environments. It helps spot potential misuse early, even if it slips past manual review.