Skip to Content
OpenClaw GuidesEnd-To-End Walkthrough

End-To-End Walkthrough

Use this walkthrough for one complete OpenClaw-to-Chirpier pass.

Goal

Verify the full loop:

  1. log events
  2. compare recent windows with analytics
  3. create a policy and destination
  4. inspect test and real delivery behavior
  5. hand a human the public dashboard page

Sequence

  1. Export CHIRPIER_API_KEY.
  2. Emit one canonical event such as tool.errors.count from openclaw.main.
  3. Confirm the event definition appears in Chirpier.
  4. Run an analytics comparison:
curl -G https://api.chirpier.co/v1.0/events/$EVENT_ID/analytics \ -H "Authorization: Bearer $CHIRPIER_API_KEY" \ --data-urlencode "view=window" \ --data-urlencode "period=1h" \ --data-urlencode "previous=previous_window"
  1. Create one policy for the event.
  2. Create one destination.
curl -X POST "https://api.chirpier.co/v1.0/destinations" \ -H "Authorization: Bearer $CHIRPIER_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "channel": "slack", "url": "https://hooks.slack.com/services/T000/B000/secret", "scope": "all", "policy_ids": [], "enabled": true }'
  1. Send a destination test and capture the returned test alert_id:
TEST_ALERT_ID=$(curl -s -X POST \ -H "Authorization: Bearer $CHIRPIER_API_KEY" \ https://api.chirpier.co/v1.0/destinations/$DESTINATION_ID/test | jq -r '.alert_id')
  1. Inspect the test delivery history:
curl -G https://api.chirpier.co/v1.0/alerts/$TEST_ALERT_ID/deliveries \ -H "Authorization: Bearer $CHIRPIER_API_KEY" \ --data-urlencode "kind=test"
  1. Trigger a real alert by exceeding the policy threshold.
  2. Inspect the default delivery history view for the real alert.
  3. Make the event public.
  4. Direct the user to the public dashboard page for the event.

What success looks like

  • the event definition is stable under agent + event
  • analytics returns the expected current and previous window values
  • the policy triggers on the intended threshold
  • the destination test returns an alert_id
  • kind=test shows the destination test delivery for that alert_id
  • the real alert appears in the default delivery history view
  • the public dashboard page works for human trend inspection
Last updated on