Check activity reporting after an editor change
A quick follow-up can catch a missing reporting connection before it creates a confusing gap in your stats.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
List User Agents
Tool to list plugins and editors which have sent data for a specified user. Use when needing to discover which development environments and tools a user is actively using.
Why this helps
Changing editors adds setup steps, and it is easy to miss whether WakaTime reporting followed you.
- Review which agents and editors have sent WakaTime data.
- Catch a possible reporting gap soon after changing tools.
- Avoid wondering later why coding stats look incomplete.
Setup
Build it in a few focused steps.
- 1Connect Test app and WakaTime to Notis once through the portal.
- 2Create an automation with a prompt asking Notis to list the WakaTime agents and editors currently reporting and point out whether the newly chosen editor appears.
- 3Choose an incoming webhook trigger and select the channel for run reports.
- 4Send one real webhook after the editor change and check the results after using the editor.
Questions about this workflow
Does this confirm a plugin is correctly configured?
It shows which agents and editors have sent data; it does not inspect local settings directly.
Should I send the webhook immediately after installing an editor?
Send it after you have had a chance to use the editor so WakaTime may have activity to report.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Test app to Wakatime. A trigger fires from one place; an action lands in another.
Test app triggers
Wakatime actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Aggregate Stats
Tool to retrieve aggregate coding statistics across all WakaTime users for a given time range. Use when analyzing global trends in programming languages, editors, operating systems, and categories.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get current user's status bar summary for today
Tool to get current user's coding activity today for displaying in IDE status bars. Use when you need a summary of today's coding time broken down by projects, languages, editors, etc.
List IDE Plugins
Tool to list WakaTime IDE plugins with metadata. Use when you want to discover available IDE integrations and their latest versions.
List Goals
Tool to list a user's goals with progress series and metadata. Use after authenticating the user with read_goals scope.
Get User Insight
Tool to retrieve an insight for a user over a time range. Use when analyzing user coding metrics after authentication.
List Leaders
Tool to list public leaders ranked by coding activity. Use when viewing top coders globally or filtering by language, country code, or hireable status.
List Machine Names
Tool to list a user's machines including last seen time. Use when needing machine names for a specific user.
Get API Meta Information
Tool to retrieve WakaTime API meta information, including public IP addresses used by WakaTime servers. Use when you need to know WakaTime's infrastructure details for network configuration or security purposes.
Connect any two apps with Notis in the middle.
Test app and Wakatime, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Wakatime.