Webhook
Google Pub/Sub Broadcaster Setup Guide
Introduction
This guide will help you configure the Google Pub/Sub Broadcaster feature, enabling you to broadcast platform events to your Google Pub/Sub topics.
Steps to Configure Google Pub/Sub Broadcaster
Step 1: Accessing Google Pub/Sub Broadcaster
To access the Google Pub/Sub Broadcaster:
- Log in to the Fynd Partner Panel.
- Navigate to Extensions and select the desired extension.
- Under the selected extension, click on Webhook.
- Click on Add Configuration.
- From the broadcaster options, select GCP PubSub.
- You will be directed to the Google Pub/Sub Config page.
Step 2: Configuring Google Pub/Sub Broadcaster
Fill in the following details:
- Name: Provide a name for identification.
- Credentials: Upload your Google Cloud service account credentials JSON file.
Explanation of Fields:
- Credentials: Upload the service account JSON file with the necessary permissions for Pub/Sub.
Step 3: Validation
- Click on Validate.
- The platform will use the provided credentials to connect to Google Pub/Sub.
- If validation is successful, a confirmation message will be displayed.
- Click on Save to finalize the configuration.
A pop-up will appear indicating Validation Successful if the entered details are valid.
Step 4: Create PubSub Subscriber API
1curl --location 'https://{{host}}/service/platform/webhook/v2.0/company/1/subscriber' --header 'Content-Type: application/json' --header 'Authorization: {{Bearer Token}}' --data-raw '{2 "name": "PubSub Subscriber",3 "provider": "pub_sub",4 "association": {5 "company_id": 1,6 "criteria": "ALL",7 "extension_id":"6684c91938568e58638a2b42"8 },9 "custom_headers": {},10 "status": "active",11 "email_id": "[email protected]",12 "auth_meta": {},13 "events": [14 {15 "slug": "company/article/update/v1",16 "topic": "fynd-json-broadcast-extension"17 }18 ]19}'
Congratulations!
You have successfully configured the Google Pub/Sub Broadcaster feature, enabling seamless event broadcasting for effective collaboration with Fynd Platform. Should you encounter any issues or have additional questions, please reach out to [email protected].
Was this section helpful?