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): rewrite Configuring section, surface V2 design rationale, slim webhook-verification, drop toolkit FAQ walkthroughs
Big cleanup pass on the trigger docs. Four threads, one commit. 1. Rewrite "Configuring the webhook endpoint" intro - Drop "Skip this section unless all three are true:" robot speak in favor of reassurance-first ("With Composio-managed OAuth, this is already done for you"). - Drop the (toolkit_slug, project_id, client_id) tuple syntax and the "endpoints are keyed by..." phrasing — internal developer language, not customer-facing. - Surface the V2 design rationale from the changelog: providers accept only one callback URL per OAuth app + each ingress URL routes to one project, so 1 OAuth app = 1 project. Frame the constraint as a trade ("the upside") with the per-project wins from the changelog: isolated ingress rate limits, own signing secret/app-level token, clean fan-out, per-project metering. - Pull the ingress signature verification details into this section as a single paragraph: HMAC-SHA256 / Ed25519 / shared token, replay protection, 400 on tamper. They were on webhook-verification.mdx but belong with the setup material. - Warn callout reduced to action only ("Sharing one OAuth app across projects? Consolidate or register separate apps"). 2. Rename `requires_webhook_endpoint` → `requires_webhook_endpoint_setup` The current name was ambiguous (every webhook trigger goes through a webhook endpoint; what's variable is whether the user sets one up). Adding "_setup" makes the flag's meaning clear. - 4 prose mentions updated: glossary.mdx, creating-triggers.mdx (×1, the second was removed in the rewrite), webhook-verification was removed entirely, troubleshooting/triggers.mdx. 3. Slim webhook-verification.mdx - Drop the "Ingress signature verification" section. The page is about the *delivery* hop signature (you verify Composio's signature on your endpoint) — ingress is automatic and the setup details for it belong on creating-triggers. - Slim the top callout: drop "see Ingress signature verification below" cross-reference (no longer below). 4. Revert toolkit-specific FAQ walkthroughs - slack.md: my five-step Slack walkthrough on "How do I set up Slack event webhooks?" → short pointer to the shared docs. "Why aren't my Slack triggers working?" → short pointer to the troubleshooting page. The shared Configuring section in creating-triggers already mentions Slack-specific dashboard paths (Event Subscriptions → Request URL); duplication on the toolkit page added drift risk. - notion.md: drop the new "How do I set up Notion webhook triggers?" entry I added in a previous pass. Same reasoning — toolkit-specific webhook setup is covered once, on the shared Configuring section. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>