Anthropic and Google models are now available inside the AI Agent Action in workflows, alongside OpenAI. You can choose your provider, select a model, and control how much reasoning it applies, all from a redesigned selection interface.

The AI Agent Action now supports models from three providers:

Models are grouped by provider in a new selection interface. Models that support reasoning are marked with a thinking chip, and each model carries a short description of what it is built for, so you can evaluate the options before committing.

Set reasoning effort to Low, Medium, or High from the same dropdown. Higher effort produces deeper reasoning on complex tasks; lower effort returns faster responses on simpler ones. Effort control is available on models that support thinking.

A flagship model can handle multi-step reasoning where accuracy is critical, while a faster, lighter model handles intent classification, simple reads, and basic operations - allowing you to choose the right model for your task in hand.

Effort control adds a second dimension to that decision, letting you tune quality against speed and token consumption on each action independently.

Layered on top of the token optimization shipped earlier, the same task now runs up to 50% cheaper.

Meta has as part of their Marketing API v26 update.

This upgrade means . But, your existing campaigns stay running, and the transition happens automatically in the background with no errors or action required.

We’re rolling out to make it easier for new users to go from

✨

Users can simply describe what they need, and Calendar AI recommends and creates the appropriate calendar.

During the guided flow, users can:

🔜

We're extending Calendar AI to help with one of our common Calendar support questions:

>

Calendar AI will use the customer's Calendar configuration to identify

Your SaaS customers can now switch their billing frequency — from monthly to annual, or annual to monthly — including at the same time as upgrading or downgrading their plan. This wasn't possible before.

If your SaaS customers have wanted to move to annual billing (or back to monthly), they can now do that directly — on its own or together with a plan change.

We’ve improved to clearly separate from bookings where .

✨

Previously, businesses could configure a when they wanted to collect a customer’s card details without charging them.

This created an unintended experience: if a booking became free — for example, after applying a — customers could still be asked to enter their card details and a $0 transaction could be processed.

We’re separating these two use cases with a dedicated option in Calendar Payment settings.

💳

When is enabled:

This gives businesses an explicit way to collect a card .

💰

When is enabled, payment collection will now depend on the .

This means customers making a genuinely

The Email Events trigger fires on opens and clicks, but the event never carried anything that identified which email produced it. If you pushed those events to an external system with the Send Webhook action, there was no Message ID variable to pick.

Email Events now carries a unique Message ID, and you can select it as a custom value inside the Send Webhook body.

Open the Send Webhook action in a workflow that starts with Email Events, then pick Message ID from the custom value picker when you build the payload. Every open and click on the same email sends the same ID. A different email sends a different one. The ID rides along with the event itself, so an open that arrives late still points back to the email that generated it.

Teams feeding email engagement into an external dashboard had no reliable way to dedupe. Email Opened fires on every open, including repeat opens of the same message, and resolving the email through the API by "most recently sent" got the wrong answer whenever a contact opened something older.

A marketing agency sends two campaign emails in the same week and pipes open and click events into its own reporting dashboard. With Message ID in the webhook body, each open lands against the specific email it came from, and the same contact opening one email four times collapses into a single engagement record instead of four.

Dropdown fields in the Create Record and Update Record actions, including the associated record versions, stopped offering dynamic values. If you had saved something like {{contact.day_1}} in a dropdown, the field opened empty with nothing selected. There was no way to enter a new merge tag either.

Single-select dropdown fields now have the Standard and Dynamic toggle, the same one you already use in Update Contact Field.

Standard mode gives you the searchable picklist, image options included. Dynamic mode gives you a text input with the custom value picker, so you can drop in a merge tag from a trigger, a formatter, or an inbound webhook. Saved values that don't match a picklist option now open in Dynamic mode on their own, so existing configs render the way you set them up. Switching between the two modes clears the field, which stops a leftover value from the other mode saving without you noticing.

Pinned and Recent in the Actions & Triggers sidebar ignored what kind of workflow you were in. Use a Contact action once, and it started showing up in your Custom Object and Company workflows too.

Both sections now list only the actions and triggers that work in the workflow you have open.

The sidebar checks the workflow's object type before it renders Pinned and Recent. Contact actions stay in Contact workflows. Company actions stay in Company workflows. Custom object actions stay in workflows built for that object. Everything else is hidden, so you can't pick a shortcut that breaks the moment you click it.

If your sub-account is on hold for a SaaS plan or rebilling and a payment card has already been added — whether you added it yourself or your agency added it for you — you'll now see that card on the billing screen and can go straight to paying, instead of being asked to add a card you already have.

You no longer have to re-enter payment details you've already provided. You'll get clear feedback when you pay, and your account unlocks automatically as soon as the payment succeeds.

If you sell SaaS plans through a sub-account, your customers' subscription details inside that sub-account now automatically update whenever they upgrade or downgrade their plan. Previously, only the subscription record behind the scenes was updated — the copy shown in your sub-account stayed on the old plan.

You can now trust that invoices sent from your sub-account always show the correct product, price, and tax for your customer's current plan. This means no more mismatched invoices or incorrect charge amounts after a customer changes their subscription.