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>