# Google PubSub

{% hint style="info" %}
The content of this documentation is under revision and may change. We appreciate your understanding as we work to improve it.
{% endhint %}

**Google PubSub** sends messages to Google Cloud Platform PubSub Service.

## **Parameters**

Take a look at the configuration parameters for the connector. Parameters supported by [Double Braces expressions](https://docs.digibee.com/documentation/connectors-and-triggers/double-braces/overview) are marked with `(DB)`.

### **General tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Project Id</strong> <code>(DB)</code></td><td>The Google Cloud PubSub Project ID.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Destination Name</strong> <code>(DB)</code></td><td>The Destination Name. For the consumer this will be the subscription name, while for the producer this will be the topic name.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Fail On Error</strong></td><td>If the option is activated, the pipeline's execution with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the <code>"success"</code> property.</td><td>False</td><td>Boolean</td></tr></tbody></table>

### **Optional tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Authenticate</strong></td><td>Use Credentials when interacting with PubSub service (no authentication is required when using emulator).</td><td>True</td><td>Boolean</td></tr><tr><td><strong>Logger Id</strong> <code>(DB)</code></td><td>Logger ID to use when a match to the parent route is required.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Service Account Key</strong> <code>(DB)</code></td><td>The Service account key that can be used as credentials for the PubSub publisher/subscriber. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Message Ordering Enabled</strong></td><td>When active, the message ordering is enabled.</td><td>False</td><td>Boolean</td></tr><tr><td><strong>Pubsub Endpoint</strong> <code>(DB)</code></td><td>Pub/Sub endpoint to use. Required when using message ordering, and ensures that messages are received in order even when multiple publishers are used.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Body</strong> <code>(DB)</code></td><td>The body, if applicable.</td><td><code>{}</code></td><td>JSON</td></tr></tbody></table>

### **Headers tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>MessageId</strong> <code>(DB)</code></td><td>The ID of the message, assigned by the server when the message is published.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Attributes</strong></td><td>The attributes of the message.</td><td>N/A</td><td>String</td></tr><tr><td><strong>Ordering Key</strong> <code>(DB)</code></td><td>If non-empty, identifies related messages for which publish order should be respected.</td><td>N/A</td><td>String</td></tr></tbody></table>

### **Documentation tab**

<table data-full-width="true"><thead><tr><th>Parameter</th><th>Description</th><th>Default value</th><th>Data type</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td>Section for documenting any necessary information about the connector configuration and business rules.</td><td>N/A</td><td>String</td></tr></tbody></table>