# Pub/Sub Subscription Name

### PUBSUB

The following figure depicts the information to be provided to add PUBSUB as an integration.

<figure><img src="/files/TUoQeGyYLHtqpDoybijh" alt=""><figcaption></figcaption></figure>

Following are the fields:

* **Account Name**: The name of the Aquawave user account&#x20;
* **Project Name**: Name of the GCP project where the subscription is
* **Subscription Name**: Name of the subscription
* **Message Format**: Select the message format from the drop down. The supported formats are GCB, GCS, GCR, CUSTOM
* **Authentication Type**: Select the user authentication mode for the Artifactory.&#x20;

  1. Select **Anonymous / Role-Based** as the authentication type if no authentication is required.
  2. You can also select **Json Key File** as the authentication type. Add the JSON service account file in the **File** field for Spinnaker to use as credentials. If this option is selected another field named **Translation Template** is displayed.&#x20;
  3. **Translation Template** - This template translates the Pub/Sub payload as a Spinnaker artifact by creating a Jinja template. Add your file by clicking **Choose File**.&#x20;

  <figure><img src="/files/uIYuyD8nLZILC9XIOObB" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The Translation Template field is optional for GCB, GCR, GCS message formats and mandatory for Custom message format.&#x20;
{% endhint %}

* **Validate**: To validate the entries before saving, enable the Validate radio button. The default value is true
* **Connect to CD**: Enable the selection & Select the spinnaker instance you want to associate this account to&#x20;
* **Group and Permissions**: To enable access to all user groups, check the  **Enable all access to all the groups for this** checkbox. To provide access to only selected user groups, uncheck this checkbox and select the required users from the **Select Group** drop down and enable the needed permissions like **Edit**, **View** or **Delete**.&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.opsmx.com/opsmx-1/opsmx-context-engine/user-guide/data-sources/available-integrations/pub-sub-subscription-name.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.