← Back to all posts

What's new: Slack, undo, and payments that tell you when they break

What's new: Slack, undo, and payments that tell you when they break

Here is what has landed recently, roughly in order of how much it changes your day.

Your apps can post to Slack

Kreova apps could already email you when something happened. Now they can post to Slack.

You connect Slack once, in your project settings, in the same place you set up the mail server. After that any notification can go to a channel instead of an inbox, or to both. A new order, a new booking, a form submission: it arrives as a readable message with the row's fields laid out, not as a wall of raw data.

You connect it yourself, once. The webhook URL is a credential, so it never goes through a build prompt and the AI never sees it.

Undo a build by asking

Say the word and the agent puts your project back the way it was before its last change.

This sounds small. It was not possible at all before. If a build moved something you liked, your options were to describe the old version and hope, or to keep going. Now you can just ask for it back.

Word documents and attachments

Drop a .docx file into the chat and Kreova reads it. It used to ask you to export a PDF first. Now it opens the Word file directly, takes the text out and builds from it.

You can also attach files at the moment you create a project, rather than only after it exists.

Real image editing

Kreova could already look at an image and measure it. Now it can act on what it sees: crop to the part that matters, trim empty edges, pad to a shape, or size it down. Ask for a hero image that is not three thousand pixels wide and you get one.

Payments that tell you when they break

This is the least exciting update on the list and probably the most valuable one.

If you sell through a Kreova app, Stripe tells your app when a payment succeeds and your app marks the order paid. When that connection quietly breaks, nothing looks wrong. Orders keep arriving. They simply never turn into paid orders, and you find out when a customer asks.

Kreova now checks that each project's payment connection still exists, on a schedule and again shortly after every update to the platform. If it has gone, your Selling page says so in plain language, in red, with the two clicks that fix it. The check ran for the first time this week and immediately found two apps sitting in exactly that state, one of them silent for six days.

Payments also carry the project they belong to now. If you run several Kreova apps on one Stripe account, each app records only its own sales instead of reacting to every sale on the account.

Smaller things you will feel

  • The chat follows you, it does not drag you. If you have scrolled up to read something, a new message no longer yanks you to the bottom. A chip appears to tell you there is something new and waits until you want it.
  • The preview knows which page you are on. Click through into your own app and the builder follows, so "make this heading bigger" means the heading actually in front of you.
  • Clicking an element is now part of the record. Pick something in the preview and the chat shows what you picked, so a week later you can still tell which of two similar requests had the hero selected.
  • Stop actually stops. Cancelling reaches inside the step in progress instead of politely waiting for it to finish.
  • Follow-ups are quick again. A follow-up change is recognised as a follow-up now and comes back in seconds rather than a minute or two.
  • Light is the default. When a request says nothing about colour, builds come back light instead of guessing.

Still to come

More reporting on what your apps are doing, and a closer look at pricing now that we can measure what a build really costs. If something on this list changes how you work, or fails to, tell us. Most of the above started as somebody saying it was annoying.