Memicu alur kerja dengan peristiwa atau pesan Pub/Sub
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda dapat menggunakan pemicu Eventarc untuk menjalankan alur kerja sebagai
hasil dari satu atau serangkaian peristiwa. Peristiwa dirutekan dari penyedia
peristiwa ke penerima peristiwa yang berminat.
Eventarc mengirimkan peristiwa ke penerima peristiwa dalam format
CloudEvents melalui permintaan HTTP. Layanan Workflows mengonversi
peristiwa menjadi objek JSON (mengikuti
spesifikasi CloudEvents)
dan meneruskan peristiwa ke eksekusi alur kerja sebagai
argumen runtime alur kerja.
Sebagai respons terhadap peristiwa langsung seperti update pada bucket Cloud Storage atau update pada template Firebase Remote Config. Misalnya, lihat
panduan memulai ini yang memicu Workflows dengan peristiwa
langsung dari Cloud Storage.
Dengan pesan yang dipublikasikan ke topik Pub/Sub. Misalnya, lihat panduan memulai ini yang memicu Workflows dengan
pesan Pub/Sub.
Perhatikan hal berikut:
Peristiwa dianggap dikirim segera setelah eksekusi alur kerja dimulai, dan eksekusi sebenarnya terjadi secara asinkron di layanan Workflows.
Eksekusi yang dipicu oleh peristiwa tidak dicoba lagi jika eksekusi alur kerja dimulai, tetapi kemudian gagal. Untuk mengetahui informasi selengkapnya, lihat
Kebijakan percobaan ulang peristiwa.
Periode penghapusan duplikat Alur Kerja untuk memastikan pemrosesan peristiwa tepat sekali adalah 24 jam.
Saat menggunakan Workflows sebagai tujuan untuk pemicu Eventarc, peristiwa yang lebih besar dari ukuran argumen Workflows maksimum akan gagal memicu eksekusi alur kerja.
Untuk mengetahui informasi selengkapnya, lihat Kuota dan batas.
Dalam project yang dilindungi oleh perimeter layanan, saat merutekan peristiwa ke tujuan Workflows yang endpoint push Pub/Sub-nya disetel ke eksekusi Workflows, Anda hanya dapat membuat langganan push Pub/Sub baru melalui Eventarc. Perhatikan bahwa akun layanan yang digunakan untuk autentikasi push
untuk endpoint Workflows harus disertakan dalam
perimeter layanan. Untuk mengetahui informasi selengkapnya, lihat
Menyiapkan perimeter layanan menggunakan Kontrol Layanan VPC.
Membuat pemicu menggunakan Google Cloud CLI
Anda dapat membuat pemicu dengan menjalankan perintah gcloud eventarc triggers create
bersama dengan flag wajib dan opsional.
Di kolom Nama akun layanan, masukkan nama yang panjangnya antara 6 dan 30 karakter.
Nama ini dapat berisi karakter alfanumerik huruf kecil dan
tanda hubung. Setelah membuat akun layanan, Anda tidak dapat mengubah namanya.
Klik Buat dan lanjutkan.
Beri akun layanan baru Anda peran
workflows.invoker agar akun tersebut memiliki izin untuk memicu alur kerja Anda. Dalam daftar Select a role, pilih Workflows > Workflows Invoker.
Jika Anda mengembangkan aplikasi produksi, selalu berikan peran yang paling tidak permisif
yang memungkinkan. Untuk mengetahui informasi selengkapnya, lihat
Mengelola akses ke project, folder, dan organisasi.
Pilih Service account yang memanggil alur kerja Anda.
Bagian ini menentukan akun layanan IAM yang sebelumnya Anda beri peran workflows.invoker sehingga akun tersebut memiliki izin untuk memicu alur kerja Anda.
Klik Save trigger.
Pemicu Eventarc tercantum di tab Triggers
di halaman Workflows Details.
Jika ingin memperbarui atau menghapus pemicu, Anda harus mengedit alur kerja:
Di halaman Workflow Details, klik
editEdit.
Di bagian Pemicu, temukan pemicu yang ingin Anda perbarui atau hapus.
Klik editEdit fasilitas atau
deleteHapus fasilitas.
Eksekusi alur kerja Anda kini dipicu oleh peristiwa yang cocok dengan kriteria filter pemicu Anda.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[],[],null,["# Trigger a workflow with events or Pub/Sub messages\n\nYou can use an Eventarc trigger to execute a workflow as a\nresult of an event or a set of events. The events are routed from an event\nprovider to interested event receivers.\n\nEventarc delivers events to the event receiver in the CloudEvents\nformat through an HTTP request. The Workflows service converts the\nevent to a JSON object (following the\n[CloudEvents specification](/eventarc/docs/workflows/cloudevents))\nand passes the event into the workflow execution as a\n[workflow runtime argument](/workflows/docs/passing-runtime-arguments).\n\nAn execution of your workflow is triggered:\n\n- When an **audit log is created** that matches the trigger's filter criteria. For example, see this quickstart in which you trigger Workflows with [events from BigQuery using Cloud Audit Logs](/eventarc/docs/workflows/quickstart-cal).\n- In response to **direct events** such as an update to a Cloud Storage bucket or an update to a Firebase Remote Config template. For example, see this quickstart in which you trigger Workflows with [direct\n events from Cloud Storage](/eventarc/docs/workflows/quickstart-storage).\n- By **messages published to a Pub/Sub topic** . For example, see this quickstart in which you trigger Workflows with [Pub/Sub messages](/eventarc/docs/workflows/quickstart-pubsub).\n\nNote the following:\n\n- Events are considered delivered as soon as the workflow execution starts, and\n the actual execution takes place asynchronously in the Workflows\n services.\n\n- Executions triggered by events are not retried if the workflow execution\n starts, but later fails. For more information, see the\n [Event retry policy](/eventarc/docs/overview#event_retry_policy).\n\n- The Workflows deduplication window to ensure exactly-once\n processing of events is 24 hours.\n\n- When using Workflows as the destination for an\n Eventarc trigger, events larger than the maximum\n Workflows argument size will fail to trigger workflow executions.\n For more information, see [Quotas and limits](/workflows/quotas).\n\n- In projects protected by a service perimeter, when routing events to\n Workflows destinations for which the Pub/Sub\n push endpoint is set to a Workflows execution, you can only\n create new Pub/Sub push subscriptions through\n Eventarc. Note that the service account used for push\n authentication for the Workflows endpoint must be included in\n the service perimeter. For more information, see\n [Set up a service perimeter using VPC Service Controls](/eventarc/docs/using-vpc-service-controls).\n\nCreate a trigger using the Google Cloud CLI\n-------------------------------------------\n\nYou can create a trigger by running a `gcloud eventarc triggers create` command\nalong with required and optional flags.\n\nFor more information, see the **gcloud** instructions in the \"Create a\ntrigger\" section when\n[creating a trigger for a specific provider, event type, and Workflows destination](/eventarc/docs/targets#triggers).\n\nCreate a trigger using the console\n----------------------------------\n\nThe following steps show you how to create a trigger on the\n**Workflows** page in the Google Cloud console.\n\n### Before you begin\n\n1.\n\n\n Enable the Eventarc and Pub/Sub APIs.\n\n\n [Enable the APIs](https://console.cloud.google.com/flows/enableapi?apiid=eventarc.googleapis.com,pubsub.googleapis.com)\n2. Create a [service account](/workflows/docs/authentication)\n so that Eventarc can make requests to the Workflows API:\n\n 1. In the Google Cloud console, go to the **Service Accounts** page.\n\n\n [Go to Service Accounts](https://console.cloud.google.com/projectselector2/iam-admin/serviceaccounts)\n\n \u003cbr /\u003e\n\n 2. Select a project and then click **Create service account**.\n\n 3. In the **Service account name** field, enter a name that is between 6 and\n 30 characters.\n\n It can contain lowercase alphanumeric characters and\n dashes. After you create a service account, you cannot change its name.\n 4. Click **Create and continue**.\n\n 5. Grant your new service account the\n [workflows.invoker](/workflows/docs/access-control#roles) role so that the\n account has permission to trigger your workflow. In the **Select a role**\n list, select **Workflows \\\u003e Workflows Invoker**.\n\n If you are developing a production app, always grant the least permissive roles\n possible. For more information, see\n [Manage access to projects, folders, and organizations](/iam/docs/granting-roles-to-service-accounts).\n 6. Click **Done**.\n\n3. To allow the principal that will run your Eventarc\n commands the ability to act as an Identity and Access Management (IAM) service\n account,\n [grant a role that allows the principal to impersonate the service account](/iam/docs/service-account-permissions#roles).\n\n### Configure the trigger\n\n1. If you don't already have a workflow that you want to trigger,\n [create and deploy one](/workflows/docs/creating-updating-workflow#creating_a_workflow).\n\n2. In the Google Cloud console, go to the **Workflows** page:\n\n\n [Go to Workflows](https://console.cloud.google.com/workflows)\n\n \u003cbr /\u003e\n\n3. On the Workflows page, select a workflow to go to its details\n page.\n\n4. On the **Workflow Details** page, click\n *edit* **Edit**.\n\n5. On the **Edit workflow** page, select **Add new trigger \\\u003e\n Eventarc**.\n\n The **Eventarc trigger** pane opens.\n6. Follow the instructions to\n [create a trigger for a specific provider, event type, and\n Workflows destination](/eventarc/standard/docs/event-providers-targets#triggers)\n and refer to the **Console** instructions in the \"Create a trigger\" section.\n\n7. Select the **Service account** that invokes your workflow.\n\n This specifies the IAM service account to which you\n previously granted the `workflows.invoker` role so that the account has\n permission to trigger your workflow.\n8. Click **Save trigger**.\n\n | **Note:** If you are updating an existing workflow, you do *not* need to redeploy the workflow. However, if you are creating a new workflow, you must also deploy the workflow.\n\n The Eventarc trigger is listed on the **Triggers**\n tab of the **Workflows Details** page.\n9. If you want to update or delete the trigger, you must edit the workflow:\n\n 1. On the **Workflow Details** page, click *edit* **Edit**.\n 2. In the **Triggers** section, find the trigger you want to update or delete.\n 3. Click *edit* **Edit resource** or *delete* **Delete resource**.\n\nYour workflow execution is now triggered by the events that match your trigger's\nfilter criteria.\n\nCreate a trigger using Terraform\n--------------------------------\n\nYou can create a trigger for a workflow using Terraform. For details, see\n[Trigger a workflow using Eventarc and Terraform](/eventarc/docs/creating-triggers-terraform).\n\nWhat's next\n-----------\n\n- [Learn more about Eventarc](/eventarc/docs/overview)"]]
