Changelog

Always-on client operations

Saaporo now supports automations for building always-on workflows that run based on triggers and instructions you define. Unlike manual processes, automations run continuously in the background and respond to client events as they happen.

Automations are powered by the same workflow architecture as your delivery templates, but they run autonomously — sending reminders, updating statuses, routing approvals, and delivering reports without manual intervention.

Trigger types

Automations can be triggered by a variety of events:

• Scheduled — Run on a cron schedule (weekly status reports, monthly reviews, or custom cadences)
• Slack — Respond to client messages, approvals, or channel activity
• HubSpot — Trigger on deal stage changes, onboarding milestones, or renewals
• Project tools — React to task completion, deadline changes, or milestone approvals
• Email — Parse inbound client requests and route them to the right workflow
• Webhooks — Accept custom HTTP payloads from any service

Memory and learning

Automations can reference past client activity to improve routing, reminders, and reporting over time. Over time, your client operations become more efficient at handling edge cases, escalations, and recurring delivery patterns.

Templates and marketplace

Get started quickly with pre-built automation templates at saaporo.com/automations. Choose from categories like client onboarding, project delivery, reporting, and account management. You can also save and share your own automations across your team.

Speed and reliability

We have made significant performance improvements across the entire platform. These changes affect every workflow, every client portal, and every integration — delivering a noticeably faster and more reliable experience.

Our engineering team spent the last sprint optimizing the core workflow engine, reducing overhead in notification delivery, and improving how we handle concurrent client workspace activity.

By the numbers

• 40% faster workflow execution times across all plan types
• 60% reduction in API latency for real-time triggers
• 99.99% uptime for the last 30 days — our best stretch ever
• 3x improvement in memory usage for large client workspaces
• 50% faster load times for client portal dashboards

Improved error handling

We have overhauled the error recovery and retry logic. Workflows that encounter transient failures (network timeouts, rate limits, temporary service outages) now recover automatically with exponential backoff and smart retry strategies.

You can also configure custom retry policies per step — setting max attempts, delay intervals, and fallback actions when retries are exhausted.

What is next

These improvements are available to all users immediately — no configuration changes needed. We are continuing to invest in performance and will share more updates in the coming weeks. Check our status page for real-time performance metrics.

Deprecation timeline

API v2 will be officially deprecated on May 1, 2026. After this date, all v2 endpoints will return a 410 Gone response. We encourage all users to migrate to API v3 as soon as possible to avoid any disruption to your client operations integrations.

API v2 was introduced in 2024 and has served us well, but v3 brings significant improvements in performance, security, and developer experience that require breaking changes.

What is changing in API v3

• Authentication — New OAuth 2.0 flow with refresh tokens and scoped permissions. API keys are no longer supported.
• Rate limits — Updated to 1,000 requests/min (up from 100), with burst allowance up to 2,000 requests/min for short periods.
• Webhooks — Signature verification is now required on all incoming webhook payloads using HMAC-SHA256.
• Removed endpoints — Several deprecated endpoints have been removed. See the full list in the migration guide.
• Response format — All responses now use a consistent envelope format with data, meta, and errors fields.

Migration guide

We have published a comprehensive migration guide at docs.saaporo.com/api/v3/migration that covers every change in detail. The guide includes:

• Side-by-side comparisons of v2 and v3 requests
• Automated migration scripts for common SDKs
• A compatibility layer you can enable during the transition
• FAQ and troubleshooting for common migration issues

Support

If you need help migrating, our developer relations team is available on Discord and via email at api-support@saaporo.com. We also offer free migration consultations for teams with more than 50 active client workflows.