Trigger with events

Eventarc is a Google Cloud service that lets you build event-driven architectures without having to implement, customize, or maintain the underlying infrastructure.

You can create an Eventarc trigger by specifying filters for the trigger and configuring the routing of the event, including the event source and the target Cloud Run service. When the specified event or set of events match the filters, this causes your Cloud Run service to be invoked automatically, in response to the events.

Events sent to your Cloud Run service are received in the form of HTTP requests.

The following event types trigger requests to your service:

This page shows you how to create a trigger for a service through the Cloud Run console page. For similar instructions on how to create a trigger for a function, see Deploy functions in Cloud Run.

You can also create an Eventarc trigger using the Google Cloud CLI or through the Eventarc console page. For instructions on creating a trigger for a specific provider, event type, and destination, filter the list to learn more about Eventarc's Event providers and destinations.

Before you begin

Before you create a trigger with Eventarc, understand the required roles for the trigger identity.

  1. Enable the Eventarc API.

    Enable the API

  2. Every Eventarc trigger is associated with an Identity and Access Management (IAM) service account at the time the trigger is created. This service account is known as the trigger service account, and is used to invoke the Eventarc API. For example, to send events to a Cloud Run service that requires authentication, ensure the trigger identity is granted the Cloud Run Invoker IAM (roles/run.invoker) role.

  3. If you are creating a trigger for a direct event from Cloud Storage, grant the pubsub.publisher role to the Cloud Storage service account:

    SERVICE_ACCOUNT="$(gcloud storage service-agent --project=PROJECT_ID)"

gcloud projects add-iam-policy-binding PROJECT_ID \
    --member="serviceAccount:${SERVICE_ACCOUNT}" \
    --role='roles/pubsub.publisher'

    Replace PROJECT_ID with your Google Cloud project ID. You can find your project ID on the Welcome page of the Google Cloud console.

Create a trigger

After deploying your service, you can use the Cloud Run console page to create an Eventarc trigger.

  1. In the Google Cloud console, go to Cloud Run.

    Go to Cloud Run

  2. From the list of services, click an existing service, or create a new service.

  3. On the Service details page, click the Triggers tab.

  4. Click Add Eventarc trigger.

    The Eventarc trigger pane opens. To determine how best to route events, see Event routing options.

  5. Follow the instructions to create a trigger for a specific provider, event type, and destination and refer to the Console instructions in the "Create a trigger" section.

  6. Select the Service account that invokes your Cloud Run service, or create a new service account.

    This specifies the IAM service account email associated with the trigger. For Cloud Run destinations, this service account is used to generate identity tokens when invoking the service.

  7. Optionally, specify the Service URL path to send the incoming request to.

    This is the relative path on the destination service to which the events for the trigger should be sent. For example: /, /route, route, route/subroute.

  8. After creating the trigger, verify its health by ensuring that there is a checkmark on the Triggers tab.

What's next