Looker

Use the Looker connector to explore and visualize business intelligence data.

Integrating your application with Looker lets you use these operations in an automation. It exposes 15 actions, listed below. Add the connector from the Connections area, authenticate, then select its operations in the automation builder. Capabilities: actions.

Authentication

Before you begin, make sure you have the following information:

Connection Name: Choose a meaningful name for your connection. This name helps you identify the connection within your application or integration settings.

Authentication Type: Looker supports API token authentication.

Authentication & setup

Creating API Credentials

For Looker (Google Cloud)

1. In your Looker instance, go to the Admin section

2. Navigate to Users

3. Click on the user for which you want to create API credentials

4. Create new API credentials

5. You'll receive a Client ID and Client Secret

For Looker (Original)

1. Request credentials creation from your Looker admin if you're not an admin

2. The admin will create credentials via the Admin section > Users

Authentication Methods

Using an SDK (Recommended)

Provide your Client ID and Client Secret to the Looker SDK, which handles token acquisition and insertion automatically.

Without an SDK

1. Call the login endpoint with your Client ID and Secret to obtain an OAuth 2.0 access token

2. Include the token in the HTTP Authorization header for subsequent requests: Authorization: Bearer {access_token}

3. Tokens can be invalidated via the logout endpoint

OAuth with CORS

Looker can use the Cross-Origin Resource Sharing (CORS) protocol to let web applications make calls to the Looker API from outside a Looker instance's domain.

Credential Security

• Create multiple credential sets per user account if needed

• API credentials are independent of user login settings (2FA/SAML don't apply to API)

• Best practice: use service accounts with minimal privileges rather than admin accounts

• Keep secrets private; never store them in source code

• Use environment variables or a secure key management service

Actions