From 1afbfce49f535df7f8ac01ea217e93c6ee14d029 Mon Sep 17 00:00:00 2001 From: Christian Castelli Date: Wed, 23 Jan 2019 17:03:49 +0100 Subject: [PATCH] Added another link to inform how events are published --- pybytes/integrations/google.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pybytes/integrations/google.md b/pybytes/integrations/google.md index cdd6530..2757293 100644 --- a/pybytes/integrations/google.md +++ b/pybytes/integrations/google.md @@ -22,7 +22,7 @@ Whenever one of your integrated devices sends a signal to our broker, we republi ![Step 1: project ID and region](../../.gitbook/assets/04_google_integration.png) -7. The following step allows you to create a new registry or select an existing one. Whenever you choose a registry, the corresponding topics will be loaded in the dropdown menu below. This is required by Google, but it's different from the topics used by the integration to publish payloads to Google cloud. +7. The following step allows you to create a new registry or select an existing one. Whenever you choose a registry, the corresponding topics will be loaded in the dropdown menu below. This is required by Google, but it's different from the topics used by the integration to publish payloads to Google cloud. For further information, [please read this section](https://cloud.google.com/iot/docs/how-tos/mqtt-bridge#publishing_telemetry_events). ![Step 2: registry and topic](../../.gitbook/assets/05_google_integration.png)