Integrations overview

Integrations are how EasyClaw gets real facts into a run — calendar rows, feed items, HTTP payloads — so the model answers from data you attached, not guesses. Everything is configured from the dashboard and consumed by the managed OpenClaw runtime on a schedule or when you message the bot.

What integrations are for

They turn EasyClaw from a clever sentence generator into a background operator that can see your week, watch sources you care about, and react when external systems signal events (on the right plan).

How they plug in

1. You connect or create a resource in the dashboard (OAuth for Calendar, URL for RSS, tokens for webhooks).
2. Automations or chat runs inject context ahead of the user message with explicit headers so tools stay scoped.
3. Output returns to Telegram (and is reflected in usage logs) unless the automation is internal-only.

Google Calendar

Connect Google Calendar to power Daily Control, meeting-aware answers, and automations that need your agenda. If auth fails, disconnect and reconnect from the dashboard; see Troubleshooting. For step-by-step connection and scope details, read Google Calendar.

RSS

RSS feeds are ideal for recurring monitoring on Starter-class setups: new items become structured input for summaries or alerts. Pair with Monitoring for the product story.

HTTP fetch and inbound webhooks (Pro)

When you need machine-to-machine glue, use the dedicated guides — they cover security, methods, and plan gates in more depth than this overview:

• HTTP and API fetch in automations
• Inbound webhooks

When to use which integration

• Calendar — time-based orientation and conflict checks.
• RSS — lightweight change streams with stable URLs.
• HTTP fetch — pull JSON or text you control (Pro).
• Inbound webhooks — push events from CI, billing, or internal services (Pro).

Plan reminders

Starter vs Pro matters for HTTP and webhooks. Calendar and RSS are central to Starter; advanced HTTP surfaces are not. Read Starter vs Pro before building automations that depend on Pro-only paths.

Common mistakes

• Pasting secrets into Telegram instead of the dashboard configuration fields.
• Expecting private RSS feeds without auth — use a bridge you control or a public feed URL.
• Confusing fetch (pull) with inbound webhooks (push) — both are documented separately.

Related

• Dashboard overview
• Using the agent in Telegram
• How EasyClaw works

Next step: connect Calendar or add an RSS automation from the dashboard, then read Daily Control or Monitoring depending on your goal.