P0 App Documentation
Sign up for FreeKnowledge Base
  • What Is P0?
    • πŸŽ›οΈIAM Dashboard
    • πŸ”ŽAccess Inventory
    • πŸͺ‘IAM Posture
    • ⏱️Just-In-Time Access
    • ♻️Service-Account Key Rotation
  • Getting Started
    • ⬇️Quick Start
    • 🎁Share P0 With Your Team
  • INVENTORY
    • πŸ—ΊοΈAccess Inventory
    • πŸ”¬Result Details
    • ❔Query Search
      • πŸ“–Search Reference
  • Posture
    • βš–οΈPosture Overview
  • Monitor Results
  • πŸ€”Finding Details
  • ORCHESTRATION
    • ⏰Just-in-time access
      • πŸ–οΈRequesting Access
        • πŸ‘‰For Another Party
      • 🏁Approving Access
        • Pre-approving Access
      • πŸ”€Request Routing
        • Google Cloud Filtering
        • AWS Filtering
      • πŸ—’οΈSession Recording
        • πŸ“¦AWS
      • πŸ”ŒJust-in-time API
        • Command API
        • Access Requests API
        • Routing Rules API
  • Environments
    • ☁️Creating an Environment
    • πŸ““Environment Terminology
    • βš™οΈSettings
  • Integrations
    • πŸ“žNotifier integrations
      • πŸ’¬Slack
      • πŸ‘¬Microsoft Teams
      • πŸ“£Custom Notifiers
        • AWS Lambda Notifier
    • πŸ”‘Resource integrations
      • ☁️Google Cloud
        • Security Perimeter
        • Requesting Access
        • Permissions Reference
          • Cloud Storage
          • Compute Engine
        • Function Caller
      • πŸ“¦AWS
        • Requesting Access
        • AWS Integration API
        • Function Caller
      • ☸️Kubernetes
        • Requesting Access
        • Advanced Requests
      • πŸ”‹PostgreSQL
        • Requesting Access
      • ❄️Snowflake
      • πŸ–₯️SSH
      • GitHub
        • Requesting Access
      • πŸ› οΈCustom Resource
        • Installing a Custom Resource Integration
    • πŸ‘₯Directory integrations
      • Microsoft Entra ID
        • Requesting Access
      • Google Workspace
      • Okta
    • βœ”οΈApproval integrations
      • πŸ””PagerDuty
    • ⚑SIEM Integrations
      • Splunk HEC Setup
  • πŸ“Tracker integrations
    • 🎟️Jira
  • P0 Management
    • 🎩Role-Based Access Control
    • πŸ”ŒManagement API
      • Role Management API
      • Just-in-time settings API
Powered by GitBook
On this page
  • Before you begin
  • Install the Google Cloud function caller component
  1. Integrations
  2. Resource integrations
  3. Google Cloud

Function Caller

PreviousCompute EngineNextAWS

Last updated 1 day ago

The GCP Cloud Run integration in P0 allows you to securely invoke your Cloud Run services in response to events like access requests, approvals, or escalations. Whether you're running fully containerized workloads or deploying lightweight functions, this integration ensures that P0 can trigger your services reliably and securely.

This component is important because it:

  • Event-driven automation: Trigger Cloud Run services from access requests or escalations.

  • Flexible deployment: Supports both containers and function-style deployments.

  • Authenticated requests: Uses IAM identity tokens for secure, private access.

  • Reusable setup: Use the same service across multiple P0 events.

Setting up the function-caller is a powerful way to connect P0's event system to your existing GCP infrastructure β€” giving you flexibility, security, and control over your automation.

Before you begin

This guide walks you through setting up your Google Cloud function caller, but before diving into the steps make sure you have configured a Google Cloud Organization and a Cloud Run service.

Install the Google Cloud function caller component

First, you'll need to define an installer component in P0 that knows how to call your Google Cloud service. This component will give P0 the permission to invoke only the specified service.

  1. Go to p0.app in your browser, navigate to Integrations, and select Google Cloud.

  2. Select the function-caller component

  1. Inside the Google Cloud integration, find the function caller component and click "Add Cloud Run Service".

4. Please provide the Cloud Run service name, service URL, as well as the project ID and region. All of which can be found on your Google Cloud Run service details page.

5. Follow the provided instructions to provision access using Google Cloud Shell or Terraform. This step grants P0 permission to call your Cloud run service securely.

  1. Once completed, P0 is now set up to call your Google Cloud run function.

πŸ”‘
☁️
How to install the Google Organization installation