Changelog

A workflow that starts from a webhook now has credentials of its own. Each workflow gets its own ingress token, so revoking one integration never touches another.

Inspect a webhook from the editor

Select the webhook trigger in the workflow editor to see everything a caller needs: the saved webhook URL, the authentication header, inputs generated from the workflow's schema, and a curl example ready to copy. Change the example inputs and the command updates without running the workflow. Because a webhook always runs the saved version, the editor points out changes you have not saved yet.

Tokens per workflow

Workspace owners and administrators create and revoke tokens for each workflow. A new secret is shown once, when it is created, and never again.

Scoped execution keys

Steps that call back into your workspace carry a short-lived key, scoped to that workspace and to the operations the run is allowed to perform. Every call re-checks the caller's membership and role, so removing someone from the workspace takes effect on their running workflows too.

Also in this release

• GPT-6 Astra is now available in the assistant's model options, at medium and high effort.

A workflow step can now call a procedure your workspace already exposes, with the same validation and permissions as when your app calls it.

The Call procedure step

Add a Call procedure step and pick a procedure from the list. The editor builds the input form from the procedure's own schema, and each input accepts an expression such as workflow_input.name. The result is available to every step that follows.

Safe by contract

Each step remembers a fingerprint of the procedure it was built against. If the procedure later changes in an incompatible way, the stale step is rejected before anything runs, instead of sending the wrong shape. The procedure keeps its own validation and authorization: making it callable from a workflow never grants extra permissions.

For developers

Only procedures you opt in appear in the editor. Opt one in with workflow metadata and explicit input and output schemas:

greeting: workspaceProcedure
  .meta({ workflow: { version: 1 } })
  .input(z.object({ name: z.string().min(1) }))
  .output(z.object({ message: z.string() }))
  .query(({ input }) => ({ message: `Hello ${input.name}` }))

Increase version when the procedure's behavior changes incompatibly without a change to its schemas.

We're thrilled to share some exciting updates with you! This release brings powerful new capabilities to help you work more efficiently and visualize your data in entirely new ways.

Enhanced Views

We've significantly improved how you can view and interact with your data:

• Kanban View: Organize and visualize your data in a beautiful Kanban board layout. Drag and drop items between columns to update their status, making workflow management more intuitive than ever.
• Group By & Aggregations: Take your data analysis to the next level with powerful grouping and aggregation capabilities. Group your records by any field and calculate sums, averages, counts, and more, all directly in your views.

Charts

Visualize your data like never before with our new charting capabilities. Transform your data into beautiful, interactive charts that help you spot trends, compare values, and make data-driven decisions at a glance.

Catering Features

We've added specialized features for event catering management:

• Event Formula Management: Create and manage formulas for your events with ease. Define recipes, quantities, and ingredients all in one place, making event planning smoother and more organized.
• Production Needs Tracking: Keep track of all food production requirements for your events. Monitor what needs to be prepared, when, and in what quantities, ensuring nothing falls through the cracks.

Agentic Data Fetching (Prototype)

We're experimenting with intelligent, AI-powered data fetching that understands context and retrieves exactly what you need. This prototype feature learns from your queries and adapts to provide more relevant results over time.

Bug Fixes & Improvements

We've also squashed a lot of bugs and made numerous improvements under the hood to make your experience smoother and more reliable.

Today we're launching our public changelog. But this isn't just a list of features: it's a commitment to building in the open with you.

Building Momentum Together

Startups rarely die mid-keystroke. They die from demoralization. We've found that maintaining a regular cadence of shipping and sharing keeps us focused on what matters: delivering value to you. Every update here is a reminder to ourselves and our users that we're moving forward.

You're Part of This

When you share feedback, we listen. When we fix something you reported or build something you requested, you'll see it here. This changelog is our way of closing the loop: showing you that your input shapes what we build.

Transparency as Culture

We believe in execution over talk. This changelog is how we hold ourselves accountable. If we're not shipping, there's nothing to write about. Simple as that.

Follow Along

You can subscribe to our updates via RSS or check back here regularly. We aim to update weekly with meaningful improvements, not noise but real progress.

Read more about our philosophy in our article: Startups Should Write Changelogs