Activepieces 0.79.2: Google Vertex AI Integration Live

Here at industry sources, we tracked the latest Activepieces release and identified a straightforward addition: native support for Google Vertex AI. This piece enables direct integration with Google's managed AI service, allowing workflow builders to call Vertex AI models without custom connectors or workarounds. The implementation appears standard - you get the ability to route requests through Vertex AI endpoints within your Activepieces automation.

This release maintains the steady cadence of incremental improvements Activepieces has established. The addition isn't groundbreaking, but it closes a gap for teams already invested in Google Cloud infrastructure. If you're building workflows that need to leverage Gemini or other Vertex AI models, you no longer need external HTTP steps or custom code.

• New Google Vertex AI piece added to core integration library
• Enables direct model calls without middleware or custom setup
• Continues pattern of cloud vendor support across major platforms

The bigger story here is the warning that continues from previous releases: secret manager refactoring is coming in 0.80.0, and it requires action. Activepieces is restructuring how secrets are stored and managed - a breaking change that will force upgrades across deployments. This is a quality-of-life improvement on the backend, but it means planning is required.

If you're running Activepieces in production, you need to treat 0.80.0 as a mandatory upgrade, not optional maintenance. The refactoring suggests Activepieces is addressing scalability or security concerns in how credentials are stored. Waiting until after 0.80.0 ships to upgrade creates technical debt quickly. This is especially critical if you have multiple teams or high-security compliance requirements.

• Secret manager refactoring arriving in 0.80.0 - not backward compatible
• Requires planned upgrade cycle, not a patch you can defer
• Affects how all stored credentials and API keys are managed

If you're using Activepieces, the immediate move is inventory your current secret storage and credential patterns. Know exactly what secrets are in use, where they're referenced, and which workflows depend on them. This exercise takes 30 minutes but prevents chaos during the 0.80.0 migration.

For teams wanting to leverage Vertex AI: test the new piece in a staging environment first. Verify that your Vertex AI service account credentials work properly through Activepieces and that response handling matches your workflow expectations. Google's AI services have specific rate limits and quota models - validate those work with your automation volume.

The broader operator move is this: 0.79.2 is a safe incremental update, but use it as your upgrade window before the harder migration arrives. Don't jump straight from an old version to 0.80.0. The momentum in this space continues to accelerate.

• Audit existing secrets and credential dependencies before 0.80.0
• Test Google Vertex AI piece in non-production first
• Plan upgrade cycle - treat 0.80.0 as mandatory, not discretionary