Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Webhook
Konektor Webhook memungkinkan Anda memproses peristiwa dari backend yang mendukung webhook. Konektor ini dirancang untuk digunakan dengan pemicu webhook. Pemicu Webhook menerima peristiwa dari aplikasi berbasis SaaS pihak ketiga yang mendukung kemampuan peristiwa webhook. Pemicu ini mendukung beberapa jenis autentikasi untuk pemroses peristiwa Anda. Untuk menggunakan pemicu Webhook dalam integrasi, Anda harus mengonfigurasi konektor Webhook terlebih dahulu.
Sebelum memulai
Sebelum menggunakan konektor Webhook, lakukan tugas berikut:
Berikan peran IAM berikut ke akun layanan yang ingin Anda gunakan untuk konektor:
roles/secretmanager.viewer
roles/secretmanager.secretAccessor
Akun layanan adalah jenis Akun Google khusus yang dimaksudkan untuk mewakili pengguna non-manusia yang perlu diautentikasi dan diberi otorisasi untuk mengakses data di Google API.
Jika Anda tidak memiliki akun layanan, Anda harus membuat akun layanan. Untuk mengetahui informasi selengkapnya, lihat Membuat akun layanan.
Jika layanan atau izin ini belum diaktifkan untuk project Anda sebelumnya, Anda akan diminta untuk mengaktifkannya
saat mengonfigurasi konektor.
Mengonfigurasi konektor
Koneksi khusus untuk sumber data. Artinya, jika Anda memiliki banyak sumber data, Anda harus membuat koneksi terpisah untuk setiap sumber data. Untuk membuat koneksi, lakukan hal berikut:
Di Konsol Cloud, buka halaman Integration Connectors > Connections
lalu pilih atau buat project Google Cloud.
Lokasi Kolom Jenis Peristiwa: Kolom wajib diisi yang menunjukkan lokasi (Header, Parameter Kueri, atau Isi Permintaan) tempat jenis peristiwa yang terkait dengan permintaan peristiwa masuk akan ada.
Nama Kolom Jenis Peristiwa: Kolom wajib di lokasi yang dikonfigurasi mengidentifikasi
jenis peristiwa yang terkait dengan permintaan peristiwa masuk.
{"event_type":"user.created",...// other request fields...}
Dalam contoh di atas, kolom event_type di isi permintaan menandakan bahwa permintaan berkaitan dengan peristiwa "user.created".
Pilih Aktifkan konektivitas pribadi untuk konektivitas yang aman antara aplikasi backend
dan koneksi Anda. Jika memilih opsi ini, Anda harus melakukan langkah-langkah konfigurasi tambahan
setelah membuat koneksi. Untuk mengetahui informasi selengkapnya, lihat Konektivitas pribadi untuk langganan peristiwa.
Masukkan konfigurasi pesan yang dihentikan pengirimannya. Jika Anda mengonfigurasi pesan yang dihentikan pengirimannya, koneksi akan menulis
peristiwa yang belum diproses ke topik Pub/Sub yang ditentukan. Masukkan detail berikut:
Project ID pesan yang tidak terkirim: Project ID Google Cloud tempat Anda mengonfigurasi topik Pub/Sub pesan yang tidak terkirim.
Topik yang dihentikan pengirimannya: Topik Pub/Sub tempat Anda ingin menulis detail peristiwa yang belum diproses.
Klik Berikutnya.
Tinjau: Tinjau detail autentikasi pendengar dan koneksi Anda.
Klik Buat.
Menggunakan koneksi Webhook dalam integrasi
Setelah Anda membuat koneksi, koneksi tersebut akan tersedia di
Apigee Integration dan Application Integration. Anda dapat menggunakan koneksi
dalam integrasi melalui tugas Konektor.
Untuk memahami cara membuat dan menggunakan tugas Konektor di Apigee Integration, lihat Tugas konektor.
Untuk memahami cara membuat dan menggunakan tugas Konektor di Integrasi Aplikasi, lihat Tugas konektor.
Mendapatkan bantuan dari komunitas Google Cloud
Anda dapat memposting pertanyaan dan mendiskusikan konektor ini di komunitas Google Cloud di Forum Cloud.
[[["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-22 UTC."],[[["\u003cp\u003eThe Webhook connector allows you to listen to events from backends that support webhooks, and it is specifically designed for use with the Webhook trigger, enabling the reception of events from third-party SaaS applications.\u003c/p\u003e\n"],["\u003cp\u003eBefore configuring the Webhook connector, you must enable the \u003ccode\u003esecretmanager.googleapis.com\u003c/code\u003e and \u003ccode\u003econnectors.googleapis.com\u003c/code\u003e services in your Google Cloud project, and grant the required IAM roles to the designated service account.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring a Webhook connection involves specifying the connection details, including selecting the Webhook connector, naming the connection, choosing a service account, and specifying the event subscription details, which is mandatory for the webhook connector.\u003c/p\u003e\n"],["\u003cp\u003eThe Webhook connector supports various listener authentication types, including No Authentication, Google Authentication, API Key Authentication, and Basic Authentication, with specific details required for each type.\u003c/p\u003e\n"],["\u003cp\u003eUpon creation, the Webhook connection can be used within Apigee Integration and Application Integration through the Connectors task, and resources are available to monitor usage, view logs, and suspend/resume the connection.\u003c/p\u003e\n"]]],[],null,["# Webhook\n\n| **Preview**\n|\n|\n| This product or feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products and features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nWebhook\n=======\n\nThe Webhook connector lets you listen to events from your backend that supports webhooks. This connector is designed to be used with the [Webhook trigger](/application-integration/docs/configure-webhook-trigger). The Webhook trigger receives events from third-party SaaS-based applications that support webhook eventing capability. This trigger supports multiple authentication types for your event listener. To use the Webhook trigger in your integration, you must first configure a Webhook connector.\n\nBefore you begin\n----------------\n\nBefore using the Webhook connector, do the following tasks:\n\n- In your Google Cloud project:\n - Enable the following services:\n - `secretmanager.googleapis.com` (Secret Manager API)\n - `connectors.googleapis.com` (Connectors API)\n\n To understand how to enable services, see [Enabling services](/service-usage/docs/enable-disable#enabling).\n - Grant the following IAM roles to the service account that you want to use for the connector:\n - `roles/secretmanager.viewer`\n - `roles/secretmanager.secretAccessor`\n\n A service account is a special type of Google account intended to represent a non-human\n user that needs to authenticate and be authorized to access data in Google APIs.\n If you don't have a service account, you must create a service account. The connector and the service account must belong to the same project. For more\n information, see\n [Creating a service account](/iam/docs/creating-managing-service-accounts#creating).\n\n\n If these services or permissions have not been enabled for your project previously, you are prompted to enable them\n when configuring the connector.\n\nConfigure the connector\n-----------------------\n\nA connection is specific to a data source. It\nmeans that if you have many data sources, you must create a separate connection\nfor each data source. To create a connection, do the following:\n\n1. In the [Cloud console](https://console.cloud.google.com), go to the **Integration Connectors \\\u003e Connections** page and then select or create a Google Cloud project.\n\n\n [Go to the Connections page](https://console.cloud.google.com/connectors/connections)\n2. Click **+ Create new** to open the **Create Connection** page.\n3. In the **Location** section, choose the location for the connection.\n 1. **Region** : Select a location from the drop-down list.\n\n For the list of all the supported regions, see [Locations](/integration-connectors/docs/locations).\n 2. Click **Next**.\n4. In the **Connection Details** section, complete the following:\n 1. **Connector** : Select **Webhook** from the drop down list of available Connectors.\n 2. **Connector version**: Select the Connector version from the drop down list of available versions.\n 3. **Connection Name** : Enter a name for the Connection instance.\n\n Connection names must meet the following criteria:\n - Connection names can use letters, numbers, or hyphens.\n - Letters must be lower-case.\n - Connection names must begin with a letter and end with a letter or number.\n - Connection names cannot exceed 49 characters.\n - For connectors that [support event subscription](/integration-connectors/docs/eventsubscription#enable-event-subscriptions-in-connections), the connection names cannot begin with the \"goog\" prefix.\n 4. **Description**: Optionally, enter a description for the connection instance.\n 5. **Service Account** : Select a service account that has the [required roles](#before-you-begin).\n 6. **Event Subscription** : Event subscription will be enabled by default and is mandatory for webhook connector. **Note:** The `Enable event subscription, entity and actions` option isn't supported for this connection.\n 7. Optionally, click **+ Add label** to add a label to the Connection in the form of a key/value pair.\n 8. Click **Next**.\n5. In the **Event Subscription Details** section, complete the following:\n 1. **Listener Authentication** : Select an authentication type for event listener and enter the relevant details.\n\n The following authentication types are supported by the webhook listener:\n - No Authentication\n - [Google Authentication](/iam/docs/workload-identities): Ensure that the service account has [roles/connectors.listener](https://cloud.google.com/iam/docs/understanding-roles#cloud-connectors-roles) role whose access token is used for authentication.\n - API Key Authentication\n - [Basic Authentication](https://www.rfc-editor.org/rfc/rfc7617)\n 2. **Event Type Field Location**: Mandatory field which denotes the location (Header, Query Param or Request Body) where event type associated with the incoming event request will be present.\n 3. **Event Type Field Name**: Mandatory field in the configured location identifies the type of event associated with the incoming event request. \n\n ```json\n {\n \"event_type\": \"user.created\",\n ...\n // other request fields\n ...\n }\n ```\n In the example above, the **event_type** field in **request body** signifies that the request pertains to a \"user.created\" event.\n 4. Select **Enable private connectivity** for secured connectivity between your backend application and your connection. If you select this option, you must perform additional configuration steps after creating the connection. For more information, see [Private connectivity for event subscription](/integration-connectors/docs/eventsubscription#psc-eventing).\n 5. Enter the dead-letter configuration. If you configure dead-letter, the connection writes the unprocessed events to the specified [Pub/Sub topic](/pubsub/docs/pubsub-basics). Enter the following details:\n 1. **Dead-letter project ID:**The Google Cloud project ID where you have configured the dead-letter Pub/Sub topic.\n 2. **Dead-letter topic:**The Pub/Sub topic where you want to write the details of the unprocessed event.\n 6. Click **Next**.\n6. **Review**: Review your connection and listener authentication details.\n7. Click **Create**.\n\nUse the Webhook connection in an integration\n--------------------------------------------\n\nAfter you create the connection, it becomes available in both\nApigee Integration and Application Integration. You can use the connection\nin an integration through the Connectors task.\n\n- To understand how to create and use the Connectors task in Apigee Integration, see [Connectors task](/apigee/docs/api-platform/integration/connectors-task#configure-the-connectors-task).\n- To understand how to create and use the Connectors task in Application Integration, see [Connectors task](/application-integration/docs/connectors-task).\n\nGet help from the Google Cloud community\n----------------------------------------\n\nYou can post your questions and discuss this connector in the Google Cloud community at [Cloud Forums](https://www.googlecloudcommunity.com/gc/Integration-Services/bd-p/cloud-integration-services).\n\nWhat's next\n-----------\n\n- Understand how to [suspend and resume a connection](/integration-connectors/docs/suspend-resume-connection).\n- Understand how to [monitor connector usage](/integration-connectors/docs/cloud-monitoring).\n- Understand how to [view connector logs](/integration-connectors/docs/view-connector-logs)."]]
