No authentication
No credentials needed
Simple
Headers and query params only
OAuth 2.0
Token-based authentication
Session
Cookie-based sessions
Google/GCP
Service account auth
No authentication
The simplest option, and the one selected by default when you create a new connection. Use it when the API doesn’t ask for any credentials. Requests are sent as-is, with no extra headers or parameters.When to use
- Public APIs that anyone can call
- Test and sandbox endpoints
- Destinations like webhook.site that accept any request
Configuration
Nothing to configure: when No authentication is selected, the header and query parameter fields are hidden.Connections that were previously saved as Simple with no parameters now show up as No authentication when you edit them. It’s the same behavior, under a clearer name.If you type parameters under Simple and then switch to No authentication, the values stay in the form (switching back to Simple restores them), but they are not saved while No authentication is selected.
Simple
Basic connection type for APIs that authenticate via HTTP headers. Use this when the API requires a static API key, basic authentication, or any header-based credential that doesn’t expire or refresh.When to use
- APIs with static API keys
- Services using
Authorization: Basicheaders - Any API where credentials are passed directly in headers
Configuration
Simple connections require only the headers that the target API expects. No additional configuration is needed. Required fields:OAuth 2.0
Connection type for APIs that use OAuth 2.0 authentication. RWS Integration requests an access token from the OAuth server and includes it in subsequent API calls.When to use
- Enterprise APIs (Salesforce, HubSpot, Microsoft)
- APIs requiring client credentials flow
- Services where tokens expire and need refresh
- Any API that issues Bearer tokens
Configuration
OAuth 2.0 connections require details about the token endpoint, how to extract the token from the response, and how the token should be sent in subsequent requests. Required fields:Token Type and Header Attribute Name
The Token Type determines the format used when sending the token, while the Header Attribute Name specifies which header carries the token:Session
Connection type for APIs that use session-based authentication via cookies. RWS Integration performs a login request, captures theSet-Cookie headers, and maintains the session for subsequent requests.
When to use
- Legacy systems with session-based authentication
- Internal APIs that require cookie authentication
- Web services with login flows
- Systems that don’t support modern token-based auth
Configuration
Session connections require the login endpoint details. RWS Integration automatically handles cookie capture and session management. Required fields:RWS Integration captures all
Set-Cookie headers from the login response and includes them automatically in all subsequent requests to the same base URL.Google/GCP
Connection type for Google Cloud Platform services. Uses service account authentication to access GCP APIs like Google Sheets, BigQuery, Cloud Storage, and others.When to use
- Google Sheets integration
- BigQuery data extraction or loading
- Google Drive file operations
- Cloud Storage (GCS) access
- Any GCP API service
Configuration
GCP connections require a service account with appropriate permissions and the OAuth scopes for the services you need to access. Required fields:Common scopes
Permissions
Next steps
Pagination
Handle different API pagination patterns
Business Rules
Transform data with JavaScript