I’ve noticed there’s a concept of Resources in Tines that seems separate from just hardcoding values in actions. I’m a bit unclear on when I should be using a Resource versus just putting a value directly in an action. Can someone explain what Resources are for and when they’re the right choice?
Resources in Tines are team-level stores for reusable data like JSON objects, lists, text values, or configurations that multiple stories need to reference. You define a Resource once and reference it anywhere using <<RESOURCE.name>> or in a formula as RESOURCE.name. When you need to update that value, you change it in one place and every story referencing it picks up the new value automatically.
The right time to use a Resource over hardcoding in an action is when the same value appears in more than one place, when the value is likely to change (like a list of safe domains, an access list, or a configuration threshold), or when it represents something meaningful that benefits from being named and centralized rather than buried in an action.
Resources are also useful for environment-specific configuration. You can define different Resource values for test and production environments, so the same story behaves differently depending on context without any story-level changes. You can manage Resources directly from the UI, but also update, create, list, and delete Resources via the Tines API.