Blog & Updates

Product progress, usage tips and industry notes.

Release announcement

September 28, 2026 · Release announcement

Opengency enters public beta

Opengency opens its public beta today. We set out to solve a very specific problem: the small, repetitive tasks that happen every day and aren't worth hiring a developer to script — notifying sales when an order comes in, sending a data summary every morning, pushing new records to a partner.

The beta supports building workflows visually, with 8 built-in connectors — HTTP, DingTalk, WeCom, Feishu, Email, SQLite, MySQL and Webhook. You can set up scheduled triggers, or trigger workflows directly from a script or another system with an API key; execution progress is visible in real time, and failures notify you automatically. There's also a template library, import/export, and plan upgrade requests. The Free plan is free forever — just sign up and go.

During the beta, send any issues you hit or connectors you'd like to see to hello@opengency.ai — we'll reply to each one.

Changelog

0.1.12

2026-10-15

Added Cloudflare Turnstile protection at sign-up and required new accounts to verify their email address.
Unverified accounts cannot sign in; admins can see verification status in the account list.

0.1.11

Rolled out the A2 OpenCore brand mark across key app and portal surfaces.
Added a connector simulation theater for order, lead, and support-ticket examples; it does not connect to external services or send real messages.
Includes autoplay, step-by-step playback, pause/resume and replay, with the full trace kept visible.

0.1.10

2026-10-12

Added a one-click demo that shows an event, its processing and the resulting email preview or delivery status in one flow.
When mail is configured, the experience can send a real test email; without it, it stays preview-only and clearly states that nothing was sent.
Added retry, stop and delete controls.

0.1.9

2026-10-12

Get a ready-to-explore onboarding package with a demo Agent, simulated email connector, and a workflow that is disabled by default. Manual runs use a simulation for the current account’s registered email.
Released build 707 with installers for four platforms and a verified Windows download mirror.

0.1.8

Choose one of your Agents for an AI workflow step; the step uses that Agent’s system prompt.
Kept the stable 0.1.8 archive as a rollback reference; all seven checksums were verified.

0.1.0 beta

2026-09-28

Workflows are now a graph: trigger, condition and action nodes, with conditional branches taking a Yes or No path
8 connectors shipped: HTTP, DingTalk, Email, SQLite, Webhook, WeCom, Feishu, MySQL
Conditions are now structured comparisons, with 9 operators and $ references
Scheduled workflow triggers, with a visual way to set the run frequency
API keys: scripts and other systems can trigger workflows directly
Real-time execution progress; automatic failure notifications, with repeated failures merged into one message
Template library: get started in one click from common scenarios
Workflow import/export, for moving between environments or sharing
Plan upgrade requests: submit in-app, effective once an admin confirms
Execution logs now record each node's input, output and duration; a node's failure stops the run immediately
Hardened security: connectors can't reach internal-network addresses, SQLite is isolated per user, Webhook signature verification can be made mandatory
A connector's "Test connection" now performs a real connection test

Product notes and updates

0.1.7: Admin prospect management and import review

For Opengency admins: create and maintain prospect organizations and contacts, preview CSV data before import, and review import history.

Image previews for support attachments (admin view)

The support-ticket admin view includes image thumbnails, zoom, and download interactions. Current checks cover a synthetic browser setup; real attachment authorization and production file access still need separate verification.

Agents in workflows

Choose one of your Agents in an AI workflow step. The step uses that Agent’s system prompt.