A developer dives into building a first Kestra.io flow, wrestling with the Google Calendar API plugin. An empty array returned from a seemingly successful call forced a deep dive into the calendarID—often the user’s email, not the default “primary.” Fixing that cleared the path forward.

Next, the author experiments with the ForEach plugin, iterating over event metadata and storing a simple count in a KV Store. The Notion plugin, initially thought to overwrite pages, surprisingly appends content, while the Confluence API demands an exact version bump, prompting a feature request.

The flow also pulls closed GitHub issues via an HTTP request, logging results and looping through them with Return and ForEach tasks. A missing GitHub plugin in earlier releases is resolved in 1.1.13, and the author plans to refine data shaping with the Return plugin.

Feedback loops with the responsive Kestra team keep bugs and feature requests moving fast. The author promises a final blog with practical plugin tips, aiming to help others build robust flows while the platform evolves.