Tines offers a variety of credential types to help you securely connect to different systems. Let's explore each type and understand when to use them. Don't worry if some of these seem complex right now. As you progress with building in Tines, you'll become more familiar with each type.
🪄Tip
AWS credentials
What they are: AWS credentials enable secure authentication with Amazon Web Services using the AWS Signature Version 4 signing process. When you use an AWS credential with an HTTP Request action, Tines automatically handles the complex authentication requirements, including generating and including the proper authorization headers.
When to use them: Use AWS credentials whenever you need to interact with AWS services like S3, Lambda, DynamoDB, SQS, or any other AWS service that requires API authentication.
HTTP Request credentials
What they are: HTTP Request credentials are dynamic credentials that fetch authentication tokens or API keys in real-time, every time they're used. Think of them as "just-in-time" credentials that always provide the most up-to-date authentication information.
When to use them: Use HTTP Request credentials when:
You need to fetch fresh tokens for each request.
You're working with short-lived access tokens.
You need to perform a token exchange before making your actual request.
JWT credentials
What they are: JWT (JSON Web Token - pronounced "jot") credentials allow you to generate secure tokens that verify identity and transmit information between parties. These tokens are digitally signed to ensure they haven't been tampered with and can contain various claims or pieces of information.
When to use them: Use JWT credentials when connecting to services that require JWT-based authentication, such as:
Modern web APIs
Single sign-on (SSO) systems
Microservices architectures
Cloud services that use token-based authentication
Custom enterprise applications
OAuth 2.0 credentials
What they are: OAuth 2.0 credentials enable secure authentication with services that use the OAuth 2.0 protocol, the industry standard for authorization. These credentials handle the complex OAuth flow, including token management and automatic refreshing, so your automations can securely connect to popular services without dealing with token expiration issues.
When to use them: Use OAuth 2.0 credentials when connecting to services that support OAuth authentication, such as:
Google Workspace (Gmail, Drive, Calendar)
Microsoft 365 (Exchange, SharePoint, Teams)
Social media platforms (Twitter, Facebook, LinkedIn)
Cloud services (Dropbox, Box, Salesforce)
Many modern SaaS applications
Multi-request credentials
What they are: Multi-request credentials enable complex authentication flows that require multiple HTTP requests to obtain access tokens. This advanced credential type allows you to chain together two HTTP requests to retrieve authentication information from sophisticated security systems.
When to use them: Use multi-request credentials when connecting to services with multi-step authentication processes, such as:
Services with challenge-response authentication.
APIs that require token exchange.
Systems where you need to retrieve a temporary token before getting the actual access token.
Complex enterprise authentication systems.
Mutual TLS credentials
What they are: Mutual TLS credentials (also known as MTLS, mutual SSL, or two-way authentication) enable your Tines automations to authenticate with services that require client certificate verification. Unlike standard TLS where only the server proves its identity to the client, mutual TLS requires both parties to verify each other's identities using certificates.
When to use them: Use Mutual TLS credentials when connecting to highly secure systems that require client certificate authentication, such as:
Financial services APIs
Healthcare systems
Internal enterprise services
Government platforms
Security-critical infrastructure
Text credentials
What they are: Text credentials are the simplest form of credentials, storing a single text value like an API key or token.
When to use them: Perfect for straightforward authentication where you just need one piece of information, such as:
Simple API keys
Access tokens
Webhook secrets
Shared keys