InfluxData
Day 12 after signup
Upcoming Training: How to Use the InfluxDB 3 processing Engine
Live training on building pipelines in InfluxDB 3
Why it works
- Put the event date and time near the top so readers can quickly assess whether they can attend.
- Build the agenda from the product’s core capabilities to specific use cases, then keep the registration prompt consistent.
How it is built
- Training headline
- Date and time
- Primary registration prompt
- Product overview
- Learning agenda
- Speaker sign-off
- Preferences and footer
Email copy
Intro to the InfluxDB 3 Processing Engine October 22, 2026 | 8 am PT | 3 pm GMT Save Your Spot Join InfluxData experts live on October 22, 2026 | 8 am PT | 3 pm GMT to explore InfluxDB 3's Processing Engine. The InfluxDB 3 Processing Engine eliminates the overhead of custom data pipelines by running Python directly inside the database, so you can transform, enrich, and act on time series data where it lives, without routing it through external systems. What you’ll learn: Overview of the Processing Engine: Understand the architecture and execution model of the embedded Python VM. Learn how the processing engine fits into the InfluxDB 3 architecture. Plugin Development with Python: Write a Python plugin to handle data transformation and alerting based on custom logic. Working with Triggers: Create and configure triggers based on real-time data changes, scheduled intervals, or incoming HTTP requests. Common Use Cases and how to: Automate data downsampling. Trigger external webhooks or notifications. Perform inline anomaly detection. Enrich time series data with external APIs. Discover and use ready-made plugins: Explore the plugin library via the InfluxDB 3 Explorer UI and learn how to deploy certified and community-published plugins. Save Your Spot Cole Bowden Senior Developer Advocate If you no longer wish to receive these emails, you may update your communication preferences . 548 Market St, PMB 77953 San Francisco, California 94104 © 2026 InfluxData, Inc. This email was sent to: you@example.com