Inbound webhooks

An inbound webhook gives you a private HTTPS URL that other systems can POST to when something happens. EasyClaw validates the request, formats the payload safely, and can surface a concise message in your Telegram chat — useful for glue between tools you already run and your agent.

What it is

A Pro-oriented integration surface: you create or rotate a secret token in the dashboard, receive a path-style URL, and send JSON (or similar) bodies from your backend, Zapier-style bridge, or CI system. Delivery and rate limits are enforced server-side so abuse does not exhaust shared infrastructure.

How it works

1. In Dashboard → Automations (or the inbound webhook section your UI exposes), generate a webhook URL.
2. Your external system sends an HTTP POST to that URL on your site's domain, shaped like /api/webhooks/inbound/<token> — the dashboard shows the exact string to copy.
3. EasyClaw accepts the body within size limits, applies per-agent rate limits, and forwards a trimmed summary to Telegram when appropriate.

Treat the full URL like a password: anyone who has it can post events into your agent's pipeline until you rotate it.

When to use it

• CI finished, payment received, form submitted — you want a single Telegram ping with key fields.
• You have a small internal service that already speaks HTTP and should not learn the Telegram API.
• You want to complement HTTP fetch (pull) with push-style events.

Examples (payload ideas)

• {"event":"deploy","env":"prod","status":"ok"} → short confirmation in chat.
• Stripe-style hooks or your own JSON — keep bodies focused; large blobs are truncated or rejected for safety.

Limits and plans

Inbound webhooks require Pro entitlement for the agent. If you are on Starter, use RSS, Calendar, and Telegram-first flows instead. See Starter vs Pro.

POST is the supported method for ingestion; oversized bodies and excessive per-hour volume are rejected or throttled — check the product if you need enterprise-scale ingress.

Common mistakes

• Pasting the webhook URL into public repos or client-side code — rotate immediately if leaked.
• Expecting a full bi-directional API — this path is for notify EasyClaw, not arbitrary RPC.
• Confusing with outbound webhooks (EasyClaw calling your URL after a run) if your plan exposes those separately.

Related

• HTTP fetch
• Integrations overview
• Troubleshooting

Next step: confirm Pro on checkout, create the webhook in the dashboard, send a test POST from curl or your backend, and verify delivery in Telegram.