Meta Ads connects in one step, and Spotlight pages follow your Brand Kit

Meta Ads is now one connection

Connecting your Meta ad account is a single flow now. An owner or manager clicks Connect on the Integrations page, signs in with Facebook, and approves access in Meta's own dialog. Then you pick your ad account from a list of exactly what you granted; if the grant covers just one account, it's chosen for you. Nobody types an account id by hand anymore.

The Ads dashboard also tells you what's actually wrong when something is. If you're connected but haven't chosen an account, it says so and takes you to the picker. If the grant was revoked on Meta's side, you'll see that instead, with a reconnect link. Your campaign history stays readable the whole time, even while a connection is being repaired.

The connection is read-only reporting: campaign results and spend flow in, and SharpOS changes nothing on your Meta account. Disconnecting removes SharpOS's access at Meta itself, not just on our side.

One thing to do: if you had Meta connected before, reconnect it once from Integrations and pick your ad account. Your campaign history is preserved throughout.

Spotlight pages put on your Brand Kit

A Spotlight page you never styled now picks up your organization's Brand Kit on its own: colors, fonts, and the wordmark in the header, drawn for whichever colorway the page uses. Change the Brand Kit and every page that inherits from it follows. Pages you already customized keep the look you gave them.

In the builder, you can tie any color or font to a named Brand Kit entry so it tracks the kit instead of holding a copy. Untie it and whatever was on screen stays. A page with a logo can now hide its written title too, while staying properly named for search engines and screen readers.

Link images got three looks: a small inline icon, a full-width cover, or a card thumbnail. A freshly uploaded image now survives the save instead of vanishing from the builder. The Design tab itself was reorganized into Header, Theme, and Social preview, with every control naming what it inherits and offering a reset.

Integrations tell you what they do and who they run as

Every provider card on the Integrations page now answers both questions at once: what this integration does, and which account it's running as. A connected-but-broken provider reads Needs attention instead of showing a green badge next to a warning, and long error messages fold into a single line you can open when you want the detail.

Key-based providers like Resend, ElevenLabs, OpenAI, and OpenRouter now ask for an API key, which is what they actually use, and link you straight to the provider's page where you create one.

Cal.com connections set up their booking webhook by themselves the moment you connect. If an existing connection has been showing a webhook warning, it heals on its own or on reconnect. There's nothing to register by hand.

Sturdier footing for agents and the API

If you've connected an AI agent or built on the SharpOS API, a few rough edges are gone. Tool listings spell out every required field and its type, so an agent knows what to send on its first try. An argument sent as plain text where a structured value was expected is understood when it clearly is one. When something is genuinely wrong, the error names the field and what was expected instead of returning a bare failure.

Requests carrying perfectly valid API keys no longer fail intermittently. And when an outside provider stalls, you get a clear error back quickly rather than a request that hangs.

Also in this release

Repeated edits to cards and pages through the API now save reliably instead of eventually jamming. Studio tells you when a frame is too large to render rather than failing quietly. Media Center picker previews no longer disappear as you scroll, the Support knowledge-base table keeps the columns you switched on, and the provider logos across the product were redrawn as one curated set, sized properly and in full color where a flattened mark was unrecognizable.