Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
docs: soften the Gmail endpoint timing note
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Anshu Garg committed
Nov 5, 2026 at 16:37 UTC
52dd3d9b991367eea01e3a96702ad82535214c4a
1 file changed
+1
-1
docs/content/changelog/11-05-26-gmail-google-calendar-instant-triggers.mdx
+1
-1
@@ -53,7 +53,7 @@ Gmail delivers mailbox changes through Google Cloud Pub/Sub, so your app needs a
53
Setup is complete once your Gmail [webhook endpoint](/docs/setting-up-triggers/custom-oauth-webhooks) exists and holds every field: `topic_name`, `push_service_account_email`, and `push_audience`. Until then, new Gmail triggers keep polling, and `fallback_reason` tells you which piece is missing. Nothing breaks while you set up.
54
55
<Callout type="warn">
56
-**Composio can't see your Google Cloud setup.** It treats the endpoint as ready as soon as it holds every field, and from then on, new Gmail triggers you create without `type` use the webhook. If your Pub/Sub push subscription doesn't deliver to the endpoint's `webhook_url` yet, Gmail's changes never reach Composio. Those triggers stay silent, and no error tells you. The rollout below avoids this.
56
+**A note on timing.** Composio can't look inside your Google Cloud project, so it treats your endpoint as ready as soon as you've filled in every field. From then on, new Gmail triggers you create without `type` use the webhook. If your Pub/Sub push subscription isn't delivering to the endpoint's `webhook_url` yet, Gmail's changes won't reach Composio, and those triggers will stay quiet with no error to tell you why. The rollout below keeps you on polling until you've seen an event arrive.
57
</Callout>
58
59
For a smooth, test-first rollout: