@devries-cameron20 / composio-1 / commits / 107734b94
Fork 0

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(triggers): drop verified_at and "retry trigger creation" wording

Two issues flagged on review: 1. "Retry the trigger creation call" in step 4 implied the user had already failed once. First-time setup users hadn't tried at all. Reword to "head back to Using the SDK to create your trigger". 2. verified_at isn't universal — providers that don't run a URL verification handshake never populate it. Telling readers to check verified_at would mislead them on toolkits that don't verify. Remove all verified_at references from the docs: - creating-triggers.mdx Step 4 ending: drop the verified_at framing; reword the verification challenge sentence to lead with "for providers that issue a verification challenge on save" so providers without a handshake aren't misframed. - creating-triggers.mdx "Updating an endpoint": drop the "(handy for checking verified_at after a provider re-save)" parenthetical from the GET-by-id example. - slack.md FAQ: simplify the "Why aren't my Slack triggers working?" answer to just point at the troubleshooting page, dropping the enumerated failure-mode list (which referenced verified_at and is no longer on the troubleshooting page anyway). The changelog mention of verified_at (line 44 of the V2 announcement) is left intact — historical reference, shouldn't be retroactively edited. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed May 7, 2026 at 21:06 UTC 107734b94174ed909cfc339bf2f06640062d8782
2 files changed +3 -3
docs/content/docs/setting-up-triggers/creating-triggers.mdx
+2 -2
@@ -216,7 +216,7 @@ Paste the `webhook_url` from step 2 into the provider's app dashboard:
216 - **Slack** → Event Subscriptions → Request URL
217 - **Notion** → Webhook Endpoints (in the integration's settings)
218
219 -Composio responds to the provider's verification challenge automatically (Slack `url_verification`, Notion's verification token, and so on) — you don't write any handshake code on your side. Once the provider saves the URL, retry the trigger creation call from [Using the SDK](#using-the-sdk).
219 +For providers that issue a verification challenge on save (Slack `url_verification`, Notion's verification token, and so on), Composio responds automatically — no handshake code on your side. Once the provider accepts the URL, head back to [Using the SDK](#using-the-sdk) to create your trigger.
220
221 ### Updating an endpoint
222
@@ -240,7 +240,7 @@ curl -X POST "https://backend.composio.dev/api/v3.1/webhook_endpoints/<ENDPOINT_
240
241 The `webhook_url` is immutable for the lifetime of the endpoint — rotating the signing secret on the provider side is a `PATCH` on the existing endpoint, not a new one.
242
243 -To inspect a single endpoint (handy for checking `verified_at` after a provider re-save):
243 +To inspect a single endpoint:
244
245 ```bash
246 curl "https://backend.composio.dev/api/v3.1/webhook_endpoints/<ENDPOINT_ID>" \
docs/content/toolkits/faq/slack.md
+1 -1
@@ -36,6 +36,6 @@ For the Slack toolkit, set `as_user=True` to post as the authenticated user. For
36
37 ## Why aren't my Slack triggers working?
38
39 -See [Triggers troubleshooting](https://docs.composio.dev/docs/troubleshooting/triggers) for the common failure modes — signing secret missing, `verified_at` null, missing app-level token, and replay-window rejections.
39 +See [Triggers troubleshooting](https://docs.composio.dev/docs/troubleshooting/triggers).
40
41 ---