@devries-cameron20 / composio-1 / commits / 3d0f561c9
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): refine concept page — better one-liner, restored steps, 5 cards

Three iterations rolled up into the same commit since they all touch triggers.mdx: 1. One-liner reworded to spell out reason → action → purpose - Was: "If you bring your own OAuth app... you may need to register the Composio-issued ingress URL with the provider once per OAuth app so events can flow into Composio..." - Now: "Composio handles ingress setup on most webhook triggers. For some webhook triggers — typically when you bring your own OAuth app — providers only deliver webhooks to URLs you've registered on the OAuth app, so you'll need to register the Composio-issued ingress URL there once for events to start flowing into Composio." - Reasoning: "for some webhook triggers" makes the conditional framing explicit (it's not all triggers, not all apps); the "providers only deliver to URLs you've registered" clause explains why; "for events to start flowing into Composio" keeps the user-facing purpose at the end. 2. Working with triggers section restored — original numbered list shape (plain ordered list, action verb bold, single line each), updated to the new vocabulary - Step 1: "Configure your webhook endpoint" (which referred to the subscription, confusingly named) → "Subscribe to events" - Step 3: now references both Creating triggers AND the Configuring the webhook endpoint section anchor, so readers scanning the steps know that section exists when their trigger needs it - Steps 2, 4, 5: same shape as the original, reworded for the subscription terminology 3. Next-steps cards reduced from 6 to 5 — drop the standalone "Configuring the webhook endpoint" card. Still reachable from the one-liner, the step 3 link, and the Creating triggers page. The card duplicated those references and made a situational step look like a primary one. Gmail labeler card kept. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Anshu Garg committed May 7, 2026 at 19:21 UTC 3d0f561c9eed31a8cadc040c2b14548adae6efef
1 file changed +9 -2
docs/content/docs/triggers.mdx
+9 -2
@@ -15,7 +15,15 @@ When events occur in apps — a new Slack message, a GitHub commit, an incoming
15 | **Webhook** | The provider pushes events to a Composio-issued ingress URL in real time. Composio verifies the provider's signature, processes the payload, and fans the event out to matching trigger instances. | Slack, Asana, Notion, Outlook |
16 | **Polling** | Composio polls the provider on a schedule. Composio managed auth has a 15-minute minimum interval; expect that as the worst-case delay between source event and delivery. | Gmail, Google Calendar |
17
18 -If you bring your own OAuth app for a webhook trigger, you may need to register the Composio-issued ingress URL with the provider once per OAuth app so events can flow into Composio — see [Configuring the webhook endpoint](/docs/setting-up-triggers/creating-triggers#configuring-the-webhook-endpoint) on the Creating triggers page. Composio handles this for you in most cases.
18 +Composio handles ingress setup on most webhook triggers. For some webhook triggers — typically when you bring your own OAuth app — providers only deliver webhooks to URLs you've registered on the OAuth app, so you'll need to register the Composio-issued ingress URL there once for events to start flowing into Composio. See [Configuring the webhook endpoint](/docs/setting-up-triggers/creating-triggers#configuring-the-webhook-endpoint).
19 +
20 +## Working with triggers
21 +
22 +1. **Subscribe** to events so Composio knows which URL to deliver to. One-time per project.
23 +2. **Discover** available trigger types for a toolkit (e.g., `GITHUB_COMMIT_EVENT`).
24 +3. **Create** an active trigger scoped to a user's connected account — see [Creating triggers](/docs/setting-up-triggers/creating-triggers), which also covers [Configuring the webhook endpoint](/docs/setting-up-triggers/creating-triggers#configuring-the-webhook-endpoint) for triggers that need it.
25 +4. **Receive events** at your subscription URL and route on `metadata.trigger_slug`.
26 +5. **Manage** triggers — enable, disable, or delete as needed.
27
28 <Accordions>
29 <Accordion title="What is a trigger type?">
@@ -35,7 +43,6 @@ Triggers are scoped to a connected account. If you haven't set up authentication
43 <Cards>
44 <Card icon={<Plug />} title="Subscribing to events" href="/docs/setting-up-triggers/subscribing-to-events" description="One-time per project: tell Composio which URL to deliver events to" />
45 <Card icon={<Zap />} title="Creating triggers" href="/docs/setting-up-triggers/creating-triggers" description="Inspect a trigger type and create trigger instances via the SDK or dashboard" />
38 - <Card icon={<RouteIcon />} title="Configuring the webhook endpoint" href="/docs/setting-up-triggers/creating-triggers#configuring-the-webhook-endpoint" description="Situational: required only when you bring your own OAuth app and the trigger needs it" />
46 <Card icon={<ShieldCheck />} title="Verifying webhooks" href="/docs/webhook-verification" description="Verify webhook signatures and understand payload versions" />
47 <Card icon={<Wrench />} title="Managing triggers" href="/docs/setting-up-triggers/managing-triggers" description="Discover, list, enable, disable, and delete triggers" />
48 <Card icon={<BookOpen />} title="Example: Gmail labeler" href="/cookbooks/gmail-labeler" description="Build an automated email labeling agent using triggers" />