Overview
When using a template or HTTP request action in Tines, you may encounter errors or null values if the credential is not properly configured. This occurs when actions attempt to reference credential data (such as INPUT.credential_name.info.metadata or CREDENTIAL.service) but cannot access it because the credential is either missing, incorrectly linked, or inaccessible in your current workspace. This guide will help you identify the cause and configure your credentials correctly.
Cause and solution
Cause one: Credential not linked to the action
When you import a template from the Tines story library or add a template action to your story, the credential may not be automatically linked. This results in null values when the action tries to reference credential metadata using the INPUT key (e.g., INPUT.jira_software_credential.info.metadata.username) or when referencing the credential by CREDENTIAL.jira.
Common error responses:
Null values returned for INPUT.credential_name.info.metadata references
"Credential not found" errors
Authentication failures (401/403 HTTP errors)
Actions failing to execute due to missing authentication
🟢 Solution:
Open the action in the Tines action editor
Look for the credential field in the action configuration
Click New connection or use the credential selector dropdown
For templates with built-in connect flows: Follow the guided connection process to authenticate
For HTTP request actions: Select an existing credential or create a new one
Once properly linked, the credential metadata will populate correctly and the action will authenticate successfully.
Cause two: Credential exists in a different workspace
Credentials in Tines are workspace-specific. If you created a credential in a Team space, it will not be available when working in your Personal space (and vice versa). This is a common issue when users switch between workspaces or collaborate across teams.
How to identify this issue:
You can see the credential listed in one workspace but not in another
The credential dropdown appears empty when configuring an action
You receive "credential not found" errors despite knowing the credential exists
🟢 Solution:
Verify which workspace you're currently in (check the team dropdown in the top left corner)
Navigate to the Credentials page for your current workspace
Check if the credential exists in this workspace
If the credential is in a different workspace, you have two options:
Option A: Switch to the workspace where the credential exists and work on your story there
Option B: Create or share the credential in your current workspace:
If you have access to the original credential, you can share it across teams (requires Team Admin permissions)
Otherwise, recreate the credential in your current workspace
Link the credential to your action following the steps in Cause One
Troubleshooting checklist
☑️ Check credential linkage: Open each action and verify a credential is selected in the credential field
☑️ Verify workspace: Confirm you're working in the correct Team or Personal space where your credentials exist
☑️ Test credential access: Navigate to the Credentials page and confirm you can see and access the credential
☑️ Review credential metadata: For templates, ensure any required metadata fields (like domain, username, etc.) are properly configured in the credential
☑️ Check credential sharing settings: If working across teams, verify the credential's Access settings allow sharing with your current team
☑️ Replace credentials story-wide: If multiple actions need the same credential update, use the story-wide credential replacement feature:
For templates: Click on the credential field, select the current credential, then choose "Replace in story" to update all instances at once
For HTTP request actions: You can replace credentials at the story level, but you may need to manually update any CREDENTIAL formula references in headers, parameters, or body fields
Need further assistance?
If you continue to experience issues after following this guide, please open a support case with the following information:
Story name and action name(s) experiencing the issue
Credential type (e.g., OAuth, HTTP Request, Text, JWT)
Workspace context: Which Team or Personal space you're working in
Error messages: Screenshots or exact text of any error messages received
Action configuration: Screenshots of the action's credential field and any relevant configuration
Expected behavior: What you're trying to accomplish with the credential
Steps taken: Which troubleshooting steps you've already attempted