| Active |
|---|
| This application does not need additional settings. So you can make connectionUnique, active service acces point to a network. There are different types of connections (API key, Oauth…). More only by using your login credentials or by following the instructions below . |
The Google Cloud Pub/Sub modulesThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More enable you to monitor and publish messages or create, update, retrieve, and delete topics and subscriptions in your Google Cloud Pub/Sub.
In order to use Google Cloud Pub/Sub with Boost.spaceCentralization and synchronization platform, where you can organize and manage your data. More IntegratorPart of the Boost.space system, where you can create your connections and automate your processes. More, it is necessary to have a Google account and a project created in the Google Cloud Console.
![[Note]](https://docs.boost.space/wp-content/themes/bsdocs/docs-parser/HTML/css/image/note.png) |
Note |
|---|---|
|
Boost.space Integrator‘s use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy. |
To connect your Google Cloud Pub/Sub account to Boost.space Integrator, you’ll need to obtain the project’s Client ID and Client Secret in the Google Cloud Console.
-
Sign in to Google Cloud console using your Google credentials.
-
Click Select a project > new project. Enter the desired project name and click the create button.
-
Select the project you have created.
-
Go to APIs & Services > Library.
-
Search and enable the following required APIs:
The desired service option should display as you type. Click on the API/service you want to connect to Boost.space Integrator.
-
Click the enable button to enable the selected API.
-
Open APIs & Services > Library, and search and enable the two remaining required APIs (see step 5 above).
-
Open Big Data > Pub/Sub. This will enable the rest of the required APIs in your project.
-
Navigate to APIs & Services > OAuth consent screen.
-
Choose the External option, and click the create button.
Note You will not be charged when selecting this option! For more details, please refer to Google’s Exceptions to verification requirements.
-
Fill the required fields as follows and then click the Save and Continue button:
App name
Enter the name of the app asking for consent.
For example
Boost.space Integrator.Authorized domains
Boost.space Integrator.com -
You don’t have to set anything in the Scopesand Optional info sections. Click Save and Continue.
-
Navigate to Credentials. Click on + create credentials, and select the OAuth Client ID option.
-
Fill in the required fields as follows, and then click the createbutton to create the application:
Application type
Web applicationName
e.g.
Boost.space IntegratorAuthorized redirect URIs
https://integrator.boost.space/oauth/cb/google-custom -
Copy your Client ID and Client Secret and store them in a safe place.
-
Log in to your Boost.space Integrator account, add a Google Cloud Pub/Sub moduleThe module is an application or tool within the Boost.space system. The entire system is built on this concept of modularity. (module - Contacts) More to your scenarioA specific connection between applications in which data can be transferred. Two types of scenarios: active/inactive. More, and click Create a connection.
-
Optional: In the Connection name field, enter a name for the connection.
-
Click the Sign in with Google button and select your Google account.
-
If a This app isn’t verified window appears, continue to the next step. If not, continue to Step 21.
Note The app is your OAuth client you have created above.
-
Click the Advanced link, and then the Go to Boost.space Integrator (unsafe) link to allow access using your custom OAuth client.
-
Review the access information and click Allow
-
Click the Allow button to confirm your choices.
The connection to your Google Cloud Pub/Sub has been established.
TriggersEvery scenario has a trigger, an event that starts your scenario. A scenario must have a trigger. There can only be one trigger for each scenario. When you create a new scenario, the first module you choose is your trigger for that scenario. Create a trigger by clicking on the empty module of a newly created scenario or moving the... when a message is published for the specified topic.
|
WebhookA webhook is a way for an app to send real-time information to a specific URL in response to certain events or triggers. name |
Enter the name for the webhook. |
|
Connection |
|
|
Project |
Select the project that contains the topic you want to watch for published messages. |
|
Topic Name |
Select the topic you want to watch for published messages. |
|
Subscription Filter |
Set the filter according to the filter syntax. If the filter is set, only messages that match this filter are returned. |
|
Message Retention Duration |
Enter the duration in seconds. Specify how long to retain unacknowledged messages in the subscription’s backlog, from the moment a message is published. Minimum 10 minutes, maximum 7 days. The default is 7 days.Duration in seconds with up to nine fractional digits, terminated by ‘s’. Example: |
|
Order Messages with an Ordering Key |
If enabled, messages published with the same |
|
Enable Dead Lettering |
Check to enable a dead letter policy, which specifies the conditions for dead lettering messages.Then, set the name of the topic to which dead letter messages should be published and the number of delivery attempts. |
|
Retry after Exponential Backoff Delay |
Check to enable a policy that specifies how Pub/Sub retries message delivery. Uncheck to retry immediately. Retry delay will be exponential based on provided minimum and maximum backoffs. https://en.wikipedia.org/wiki/Exponential_backoff. Set the minimum and maximum backoff (in seconds). |
|
LabelsA label is a “tag” that can be added to items within a module. It's a flexible tool used to categorize and organize data, making it easier to customize workflows and processes. More |
Specify labels. See Creating and managing labels. An object containing a list of |
Publishes a message to the specified topic.
|
Connection |
|||||
|
Topic Name |
Enter the topic path in the following format: Or use the Search button to browse the desired topic. |
||||
|
Messages |
Either message or attribute will be required to publish.
|
Returns a list of topics in the specified project.
|
Connection |
|
|
Project |
Select or map the ID of the project you want to retrieve topics from. |
|
Limit |
Set the maximum number of topics Boost.space Integrator will return during one execution cycleA cycle is the operation and commit/rollback phases of scenario execution. A scenario may have one or more cycles (one is the default).. |
Returns a list of topic subscriptions.
|
Connection |
|
|
Topic Name |
Enter the topic path in the following format: Or use the Search button to browse the desired topic you want to list subscriptions for. |
|
Limit |
Set the maximum number of subscriptions Boost.space Integrator will return during one execution cycle. |
Creates a new subscription to a specified topic.
|
Connection |
|
|
Subscription ID |
Specify the unique resource name. |
|
Project |
Select the project or map the ID of the project that contains the topic you want to create a subscription for. |
|
Topic Name |
Select the topic or map the ID of the topic you want to create a subscription for. |
|
Enable Push Delivery |
Check this option to use Push delivery instead of Pull delivery. |
|
Enable Subscription Expiration |
Check to enable a policy that specifies the conditions for this subscription’s expiration. A subscription is considered active as long as any connected subscriber is successfully consuming messages from the subscription or is issuing operationsAn operation is a task performed by module. More on the subscription. |
|
Time To Live |
Specify the “time-to-live” duration for an associated resource in seconds. The resource expires if it is not active for a period of Indicate the duration in seconds with up to nine fractional digits, terminated by ‘ |
|
Acknowledgement Deadline in Seconds |
Enter the approximate amount of time (on a best-effort basis) Pub/Sub waits for the subscriber to acknowledge receipt before resending the message. In the interval after the message is delivered and before it is acknowledged, it is considered to be outstanding. During that time period, the message will not be redelivered (on a best-effort basis). |
|
Subscription Filter |
Set the filter according the filter syntax. If the filter is set, only messages that match this filter are returned. |
|
Message Retention Duration |
Enter the duration in seconds. Define how long to retain unacknowledged messages in the subscription’s backlog, from the moment a message is published. Minimum 10 minutes, maximum 7 days. The default is 7 days.Duration in seconds with up to nine fractional digits, terminated by ‘s’. Example: |
|
Retain Acknowledged Messages |
If enabled, messages are not expunged from the subscription’s backlog, even if they are acknowledged, until they fall out of the |
|
Order Messages with an Ordering Key |
If enabled, messages published with the same |
|
Enabled Dead Lettering |
Check to enable a dead letter policy, the policy that specifies the conditions for dead lettering messages.Then, set the name of the topic to which dead letter messages should be published and the number of delivery attempts. |
|
Retry after Exponential Backoff Delay |
Check to enable a policy that specifies how Pub/Sub retries message delivery. Uncheck to retry immediately. Retry delay will be exponential based on provided minimum and maximum backoffs. https://en.wikipedia.org/wiki/Exponential_backoff. Set the minimum and maximum backoff (in seconds). |
|
Labels |
Specify labels. See Creating and managing labels. An object containing a list of |
Updates an existing subscription.
|
Connection |
|
|
Subscription Name |
Enter the path to the subscription you want to update in the following format: |
Please find the descriptions of the fields in the Create a Subscription section above.
Deletes a subscription. All messages retained in the subscription are immediately dropped.After a subscription is deleted, a new one may be created with the same name, but the new one has no association with the old subscription or its topic unless the same topic is specified.
|
Connection |
|
|
Subscription Name |
Enter the path to the subscription you want to delete in the following format: |
Allows you to perform a custom API call.
|
Connection |
||||
|
URL |
Enter a path relative to
|
|||
|
Method |
Select the HTTP method you want to use: GET to retrieve information for an entry. POST to create a new entry. PUT to update/replace an existing entry. PATCH to make a partial entry update. DELETE to delete an entry. |
|||
|
Headers |
Enter the desired request headers. You don’t have to add authorization headers; we’ve already added those for you. |
|||
|
Query String |
Enter the request query string. |
|||
|
Body |
Enter the body content for your API call. |
The following API call returns all snapshots in the specified topic:
URL:
/v1/projects/{project}/topics/{topic}/snapshots/
Method:
GET
 |
The result can be found in the module’s Output under BundleA bundle is a chunk of data and the basic unit for use with modules. A bundle consists of items, similar to how a bag may contain separate, individual items. More > Body > snapshots.
In our example, 3 snapshots were returned:
 |