So, when would you use a record?
Records shine in situations where you need to store, query, or analyze data over time. They're perfect for workflows that generate information you'll want to reference later, whether for reporting, compliance, or driving future automation decisions.
Let's look at some real-world scenarios where records make sense.
Security incident tracking
Your security monitoring tools generate hundreds of alerts every day. Intelligent workflows can enrich each alert with threat intelligence, check for false positives, and route high-priority alerts to your team, but understanding patterns, tracking response times, and reporting on security posture requires storing that data over time.
💡 How records help: A record type captures key details from every alert: the source, severity, affected assets, enrichment data, and resolution status. Your team can query records to see which alert types are most common, how quickly incidents are resolved, and whether certain assets are repeatedly targeted.
IT service request tracking
Your IT team handles dozens of software access requests, hardware provisions, and account changes every week across multiple channels. Automation can route requests for approval and check license availability, but measuring fulfillment times, identifying bottlenecks, and reporting on request volumes requires storing that data consistently.
💡 How records help: A record type captures every request's details: the requester, request type, priority, submission date, and fulfillment status. Your team can query records to track average fulfillment times, identify which request types generate the most volume, and spot trends across departments.