Looker Direct Integration

Overview


Integrating your Looker account with Spendflo facilitates streamlined management of your Looker resources. This guide provides step-by-step instructions to seamlessly connect your Looker account to Spendflo, empowering you to efficiently manage and track Looker usage in your organisation. 


Pre-requisites


An admin role is required to integrate Looker on Spendflo.


Connecting Your Looker Account


1. Open the Spendflo Integrations page

Navigate to the integrations page from Settings>Management Hub>Integrations>Available Apps > Looker.

2. Click on "Connect Account" to initiate the Looker integration process.


3. You'll now be prompted to add the Client ID, Client Secret and Instance Name, Port.


4. Finding your Looker Client ID, Client Secret


  1. To find Client ID, Client Secret, sign in to your Looker Admin Console.
  2.  Navigate to Admin > Users.
  3. Click the Edit Keys button. The Edit User API keys page opens and shows the existing API keys. Click the New API key button to generate a new key.
  4. Copy your Client ID, Client Secret and paste it in the relevant field in Spendflo.



5. Finding your Looker Instance Name

  1. You will find the Looker Instance from the Looker website URL in your browser.


6. Finding your Looker Port


  1. For Looker instances hosted on Google Cloud Platform (GCP), Microsoft Azure, and instances hosted on Amazon Web Service (AWS) that were created on or after 07/07/2020, the default Looker API path uses port 443.

  2. For Looker instances hosted on AWS that were created before 07/07/2020, the default Looker API path uses port 19999.


7. Review permissions & click submit. 


8. Integration Successful

You'll see the successful integration prompt back on Spendflo Integration page.







Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article