Skip to main content

Resources in Tines

How to create and use resources in Tines.

Danielle Swanser avatar
Written by Danielle Swanser
Updated today

Resources provide a way to store information in a single, centralized location that can then be accessed from any action within Tines. This eliminates the need to update the same information in multiple places when changes occur. Think of resources as your automation's shared knowledge base—centralized information that can be accessed across your entire Tines environment.

Tines supports:

  • Plaintext resources

  • JSON objects (such as arrays)

  • Files (with a 5MB size limit)

How to create resources

Resources can be created in two ways:

  1. Selecting "Resources" in the menu opened by clicking your team name in the top left.

  2. From the storyboard by selecting the "+" next to the word Resources in the right-hand panel.

    To use a resource in an action, you reference it with the RESOURCE key in formulas. When the action runs, the resource placeholder is replaced by the contents stored in the referenced resource.

Note: If a resource is renamed, its name will change in any of the stories it's used in.

Resource sharing

Resources have configurable access controls:

  • By default, resources are only accessible to the team they are created within.

  • The team that owns the resource will always have access to it.

  • Resources can be shared with all teams in the tenant, including personal teams, by selecting the 'All teams' access option.

  • Resources can be shared with specific teams by selecting the desired team names.

When resources with the same name are shared across multiple teams, a story will use the resource located within the same team as the story.

Note: When a user is deleted in Tines, the resources they created and saved in a team will remain available.

Finding the ID of a resource

To find the ID of a resource, navigate to "Resources" in the relevant team, and select the resource.

The ID of the resource is shown in the address bar after /resources/

Did this answer your question?