Sign inStart your trial

WakaTimeWakaTime
01Integration field card

WakaTime Integration & Workflow Automation

Run WakaTime on autopilot. Keep the veto.

17 actions

Your coding stats pile up in WakaTime and nothing acts on them until you do. Rills reads the data, proposes the next move, and waits for your call.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential development action from WakaTime arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

WAKATIME · WEEKLY STATS REVIEW
82

Post stats summary for 4 projects to client report?

3 projects under goal target this week

Get User Stats by Range: Mon-Sun, all languages

Same report sent last 6 Fridays without changes

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About WakaTime automation

Coding data doesn't stay neutral. When WakaTime's stats by range show a project going quiet or a goal slipping, that signal sits there until someone acts, and if automation acts first, you find out after the fact.

When WakaTime runs unsupervised

Development data feeds into reports, goal reviews, and team dashboards whether you've looked at it or not. When something fires on stale numbers, the correction is always harder than the original call would have been.

  • Goal status is read and shared before you've verified the underlying hours tracked that week.
  • User stats get pulled into a client-facing summary that reflects an incomplete coding session.
  • Project activity reports go out based on List User Projects data that doesn't account for a mid-week repo rename.
  • A leaderboard snapshot gets posted using List Leaders data from a range where one contributor was out sick.

What Rills does inside WakaTime

Rills reads your WakaTime automation layer: it runs Get User Stats by Range on schedule, compares against your active goals via List Goals, and surfaces a proposed action with the context attached. Nothing posts, sends, or updates until you approve it.

The stat is already there; you just decide what happens next.

Why WakaTime has no triggers and how Rills fills the gap

WakaTime doesn't push events outward, so there's nothing to react to in real time. Rills compensates by polling on a schedule you control and chaining operations so the data pull and the proposed action arrive together.

  • Get User Stats by Range runs on a weekly cadence and queues a summary for your review before it reaches anyone else.
  • List Goals is checked each morning; if a goal looks off-track, Rills flags it rather than letting it quietly miss the deadline.
  • Get User Summaries feeds a scheduled digest that waits for your approval before going to a client or a Slack channel.
  • Get User's Total Time Since Creation runs at month-end to anchor billing or progress reviews, proposed for your sign-off before the number is used anywhere.
04. Actions

What Rills can do in WakaTime

4 of 17 actions across reads, writes, and updates.

  1. 01

    Get User Stats

    Retrieve comprehensive coding statistics including languages, editors, projects, and daily productivity metrics for a user. Use this to analyze coding patterns and measure developer productivity over time.

  2. 02

    Get User Summaries

    Retrieve detailed daily breakdowns of your coding activity including time spent by project, language, and editor over a specified date range. This helps you understand your development patterns and track productivity metrics.

  3. 03

    List User Projects

    Retrieve all WakaTime projects associated with a user account, including project names, IDs, and activity timestamps to understand coding work history and project inventory.

  4. 04

    Get current user's status bar summary for today

    Retrieves a summary of your coding activity for today, including time spent on different projects, languages, and editors. This helps you monitor productivity and understand where your development time is being allocated.

05. FAQ

Common questions about WakaTime automation

06. NEXT MOVE

Approve every WakaTime change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.