If you are creating a new function, see the Console Quickstart on Cloud Run. The content on this page only applies to existing legacy functions created with the Cloud Functions v1 API.
Stay organized with collections
Save and categorize content based on your preferences.
Cloud Run functions triggers (1st gen)
You can set up Cloud Run functions to execute in response to various scenarios by
specifying a trigger for your function. Triggers can be HTTP(S) requests or
one of a number of supported events. This page provides an overview of the
triggers supported by Cloud Run functions.
Broadly, triggers fall into two categories:
HTTP triggers, which react to HTTP(S) requests, and correspond to
HTTP functions.
Event triggers, which react to events within your Google Cloud project,
and correspond to
event-driven functions.
You specify triggers as part of
function deployment. You cannot bind the
same function to more than one trigger at a time, but you can have the same
event cause multiple functions to execute by deploying multiple functions
with the same trigger settings.
Supported triggers
Cloud Run functions supports the following types of triggers:
Because Cloud Run functions can be triggered by messages on a Pub/Sub
topic, you can integrate Cloud Run functions with any other Google service that
supports Pub/Sub as an event bus. In addition, by using HTTP triggers
you can also integrate with any service that provides HTTP callbacks (webhooks).
The following sections describe some example integrations.
Cloud Logging
Cloud Logging can route logs to a Pub/Sub topic, where they can then
be consumed by Cloud Run functions. See
Configure and manage sinks in the
Cloud Logging documentation for more information.
Cloud Scheduler
Cloud Scheduler jobs can send messages to a Pub/Sub topic, where
they can then be consumed by Cloud Run functions. See the Cloud Scheduler
tutorial
Using Pub/Sub to trigger a Cloud Run function
for more information.
Cloud Tasks
Cloud Tasks HTTP Target tasks enable you to run task handlers at any
HTTP endpoint, so a Cloud Run function with an HTTP trigger can be used
as a task handler. You can also use tasks to throttle or rate-limit function
invocations. See
Create HTTP Target tasks in the
Cloud Tasks documentation for more information.
Gmail
Using the Gmail
Push Notification API,
you can send Gmail events to a Pub/Sub topic and consume them
with Cloud Run functions.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eCloud Run functions can be triggered by HTTP(S) requests or various events within your Google Cloud project.\u003c/p\u003e\n"],["\u003cp\u003eTriggers are categorized into HTTP triggers for HTTP(S) requests and event triggers for events within the Google Cloud project.\u003c/p\u003e\n"],["\u003cp\u003eYou can only bind one trigger to a single function at a time, but you can deploy multiple functions with the same trigger settings for parallel execution.\u003c/p\u003e\n"],["\u003cp\u003eCloud Run functions support a variety of event triggers, including Pub/Sub, Cloud Storage, Firestore, and several Firebase-related triggers.\u003c/p\u003e\n"],["\u003cp\u003eFunctions can be integrated with any Google service that supports Pub/Sub or any external service with HTTP callbacks by using Pub/Sub or HTTP triggers, respectively.\u003c/p\u003e\n"]]],[],null,["# Cloud Run functions triggers (1st gen)\n======================================\n\nYou can set up Cloud Run functions to execute in response to various scenarios by\nspecifying a *trigger* for your function. Triggers can be HTTP(S) requests or\none of a number of supported events. This page provides an overview of the\ntriggers supported by Cloud Run functions.\n\nBroadly, triggers fall into two categories:\n\n- **HTTP triggers** , which react to HTTP(S) requests, and correspond to\n [HTTP functions](/functions/1stgendocs/writing/write-http-functions).\n\n- **Event triggers** , which react to events within your Google Cloud project,\n and correspond to\n [event-driven functions](/functions/1stgendocs/writing/write-event-driven-functions).\n\nYou specify triggers as part of\n[function deployment](/functions/1stgendocs/deploy). You cannot bind the\nsame function to more than one trigger at a time, but you can have the same\nevent cause multiple functions to execute by deploying multiple functions\nwith the same trigger settings.\n| **Note:** Trigger binding does not happen instantaneously. It may take several minutes for a deployed function to start triggering on incoming events.\n\nSupported triggers\n------------------\n\nCloud Run functions supports the following types of triggers:\n\n- [HTTP triggers](/functions/1stgendocs/calling/http)\n- Event triggers:\n - [Pub/Sub triggers](/functions/1stgendocs/calling/pubsub)\n - [Cloud Storage triggers](/functions/1stgendocs/calling/storage)\n - [Firestore triggers](/functions/1stgendocs/calling/cloud-firestore-1st-gen)\n - [Google Analytics for Firebase triggers](/functions/1stgendocs/calling/google-analytics-firebase)\n - [Firebase Realtime Database triggers](/functions/1stgendocs/calling/realtime-database)\n - [Firebase Authentication triggers](/functions/1stgendocs/calling/firebase-auth)\n - [Firebase Remote Config triggers](/functions/1stgendocs/calling/firebase-remote-config)\n\nAdditional triggers via Pub/Sub and webhooks\n--------------------------------------------\n\nBecause Cloud Run functions can be triggered by messages on a Pub/Sub\ntopic, you can integrate Cloud Run functions with any other Google service that\nsupports Pub/Sub as an event bus. In addition, by using HTTP triggers\nyou can also integrate with any service that provides HTTP callbacks (webhooks).\nThe following sections describe some example integrations.\n\n### Cloud Logging\n\nCloud Logging can route logs to a Pub/Sub topic, where they can then\nbe consumed by Cloud Run functions. See\n[Configure and manage sinks](/logging/docs/export/configure_export_v2) in the\nCloud Logging documentation for more information.\n\n### Cloud Scheduler\n\nCloud Scheduler jobs can send messages to a Pub/Sub topic, where\nthey can then be consumed by Cloud Run functions. See the Cloud Scheduler\ntutorial\n[Using Pub/Sub to trigger a Cloud Run function](/scheduler/docs/tut-gcf-pub-sub)\nfor more information.\n\n### Cloud Tasks\n\nCloud Tasks HTTP Target tasks enable you to run task handlers at any\nHTTP endpoint, so a Cloud Run function with an HTTP trigger can be used\nas a task handler. You can also use tasks to throttle or rate-limit function\ninvocations. See\n[Create HTTP Target tasks](/tasks/docs/creating-http-target-tasks) in the\nCloud Tasks documentation for more information.\n\n### Gmail\n\nUsing the Gmail\n[Push Notification API](https://developers.google.com/gmail/api/guides/push),\nyou can send Gmail events to a Pub/Sub topic and consume them\nwith Cloud Run functions."]]
