OpenClaw + Outlit

Use Outlit customer context in OpenClaw and schedule read-only customer digests.

OpenClaw can use the Outlit CLI to read authorized customer profiles, revenue, activity, and evidence. You can also schedule read-only digests to a chat channel connected to OpenClaw. Outlit continues to monitor churn and renewals in Attention; these digests help you review that work alongside other customer context.

Setup

1. Install the Outlit CLI

   npm

   npm install -g @outlit/cli
   

   bun

   bun add -g @outlit/cli
   

   Homebrew

   brew install outlitai/tap/outlit
   

   Shell script

   curl -fsSL https://outlit.ai/install.sh | bash
   

   Detects your OS and architecture, downloads the latest binary to ~/.outlit/bin, and adds it to your PATH.

   Verify with outlit --version.

2. Authenticate

   Get your API key from Settings → API keys, then:

   outlit auth login
   

   The CLI prompts for your key, validates it, and stores it securely. For OpenClaw, store OUTLIT_API_KEY through SecretRefs so the agent can authenticate without a plaintext key in its configuration. Run openclaw secrets configure to set it up.

   Treat your API key like a password. It grants whatever capabilities its configured grants allow — potentially including customer access mutations. Revoke keys anytime from the Outlit app.

3. Install the Outlit skill

   outlit setup openclaw
   

   This installs the outlit skill into the OpenClaw skills target through the shared skills installer. OpenClaw detects and loads it automatically.

4. Verify

   outlit doctor
   

   You should see:

   ✓ OpenClaw: Outlit skill installed
   

   Then message OpenClaw in your chat platform:

   List my paying customers sorted by MRR.
   

What OpenClaw can do with Outlit

Once the skill is installed, OpenClaw learns how to use the full outlit CLI. You can ask it for customer context in natural language:

Ask OpenClaw…	What it runs
”Show me paying customers who went silent this month”	outlit customers list --billing-status PAYING --no-activity-in 30d
”Get the full profile for acme.com”	outlit customers get acme.com --include users,revenue,recentTimeline
”What’s been happening across Acme’s customer communications?”	outlit customers timeline acme.com --channels COMMUNICATION --limit 50
”Find inactive users at Acme Corp”	outlit users list --customer-id <customer-uuid> --journey-stage INACTIVE
”Search for pricing concerns across all customers”	outlit search "pricing concerns"
”What do we know about acme.com recently?”	outlit facts list acme.com --status ACTIVE --limit 20
”Open the exact call behind that search result”	outlit sources get --source-type CALL --source-id call_123
”Which event types fire most often?”	outlit sql "SELECT event_type, COUNT(*) FROM activity GROUP BY 1 ORDER BY 2 DESC LIMIT 10"
”Show me the available analytics views”	outlit schema

The Outlit skill guides OpenClaw through JSON responses, money values in the billing provider’s units (cents for USD, EUR, GBP, and CAD), and pagination. Check its answer against the returned evidence.

Scheduled customer digests

OpenClaw can deliver a recurring summary of Outlit data to your messaging channel. Its cron jobs read context; they do not replace the churn and renewal monitoring Outlit runs in Attention.

Open attention digest (daily)

Start with the items Outlit has already assessed and placed in Attention.

openclaw cron add \
  --name "Open Attention Digest" \
  --cron "0 9 * * *" \
  --tz "America/New_York" \
  --message "Run: outlit attention list --json. Summarize the open items by customer and priority, with the evidence available in each item. Link each item for human review. Do not infer that an empty list means monitoring is inactive." \
  --announce

Trial health check (daily)

Trials that went quiet after a week probably need a nudge before expiration.

openclaw cron add \
  --name "Trial Health Check" \
  --cron "0 9 * * *" \
  --tz "America/New_York" \
  --message "Run: outlit customers list --billing-status TRIALING --no-activity-in 7d. Summarize as a trial health report, list each trial, days since last activity, and suggest an outreach action." \
  --announce

Revenue snapshot (weekly)

Get a current MRR snapshot for your top accounts. This recipe assumes every account bills in one currency: the customers view doesn’t name a currency, so the prompt states it. mrr_cents is in the billing provider’s units: cents for USD, EUR, GBP, and CAD. Change USD to the currency you bill in; for a currency outside those four, replace the divide-by-100 step with your provider’s amount rules (see Stripe’s currency docs). If your accounts bill in more than one currency, the ranking and the total would mix units. Use the revenue view instead, which has a currency column on each snapshot, and rank and total within each currency.

openclaw cron add \
  --name "Revenue Snapshot" \
  --cron "0 9 * * 1" \
  --tz "America/New_York" \
  --message "Run: outlit sql \"SELECT domain, mrr_cents FROM customers ORDER BY mrr_cents DESC LIMIT 15\". We bill in USD, so mrr_cents is cents: divide it by 100 for MRR in dollars. Format as a revenue snapshot table, show rank, and note the total MRR across all listed accounts." \
  --announce

Inactive users (twice a week)

Individual users who went inactive, even if their company account is still active.

openclaw cron add \
  --name "Inactive Users" \
  --cron "0 9 * * 2,4" \
  --tz "America/New_York" \
  --message "Run: outlit users list --journey-stage INACTIVE --limit 20. Summarize as an inactive users report, group by customer, show user emails and journey stage, and note any patterns." \
  --announce

New signups overview (weekly)

Friday recap of new customers that signed up during the week.

openclaw cron add \
  --name "New Signups Overview" \
  --cron "0 10 * * 5" \
  --tz "America/New_York" \
  --message "Run: outlit users list --journey-stage SIGNED_UP --order-by first_seen_at --limit 50. Summarize as a weekly new signups report, group users by customer, and note current activity level." \
  --announce

Replace America/New_York with your timezone. OpenClaw supports any valid IANA timezone string.

Managing cron jobs

openclaw cron list                  # View all scheduled jobs
openclaw cron run JOB_ID            # Test a job immediately
openclaw cron disable JOB_ID        # Pause without deleting
openclaw cron enable JOB_ID         # Resume a paused job
openclaw cron rm JOB_ID             # Delete a job

Outlit agent skills

For other coding agents or optional SDK instrumentation guidance, see Agent skills.

Troubleshooting

Problem	Solution
outlit doctor shows “Outlit skill not found”	Run outlit setup openclaw to install the skill
OpenClaw says it doesn’t know about Outlit	Confirm OUTLIT_API_KEY is available to OpenClaw through SecretRefs, then restart its Gateway
Commands return authentication errors	Run outlit auth status to verify your key is valid
Cron jobs aren’t firing	Check openclaw cron status and verify timezone settings
JSON parsing errors	Ensure you’re running the latest Outlit CLI (outlit upgrade)

Next steps

OpenClaw docs

Learn more about OpenClaw’s features: skills, cron, secrets, and more

Attention

Review the churn and renewal work Outlit prepares.