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(creating-triggers): tighten intro paragraph
The intro was cramming five things into one runaway sentence: where you can create triggers, the Composio-managed flow, the bring-your-own-OAuth flow, the requires_webhook_endpoint_setup flag, and the 400 status code. Plus a meta "see Configuring below" pointer. Reduced to two short sentences. Flag name and 400 status drop out — the Configuring section's own intro already explains both, so they don't need to be teased here. Reader gets oriented (SDK or dashboard) with a soft anchor for the conditional case. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Anshu Garg committed
May 7, 2026 at 21:00 UTC
b0b85804c452e8c91f5d7f15c24dbf984f88035d
1 file changed
+1
-1
docs/content/docs/setting-up-triggers/creating-triggers.mdx
+1
-1
@@ -12,7 +12,7 @@ Create a trigger to start receiving events. A trigger watches for a specific eve
12
- A [webhook subscription](/docs/setting-up-triggers/subscribing-to-events) on the project, so events have somewhere to land
13
</Callout>
14
15
-You can create triggers using the [SDK](#using-the-sdk) or the Composio [dashboard](#using-the-dashboard). With Composio-managed OAuth, Composio handles all webhook endpoint setup for you. If you bring your own OAuth app and the trigger type's `requires_webhook_endpoint_setup` flag is `true`, the create call returns a `400` until you set up the endpoint — see [Configuring the webhook endpoint](#configuring-the-webhook-endpoint) below.
15
+You can create triggers using the [SDK](#using-the-sdk) or the Composio [dashboard](#using-the-dashboard). Some webhook triggers also need a webhook endpoint configured first — covered in [Configuring the webhook endpoint](#configuring-the-webhook-endpoint) below.
16
17
## Using the SDK
18