Automation · Content and publishing

Change a promotion's text or price on your Storyblok site from WhatsApp

An AI agent gets a promotion change on WhatsApp, updates the story in Storyblok and leaves a note of what changed.

Show me this with my own operation See every automation

How do I change a promotion on my Storyblok site by sending a WhatsApp message?

The owner writes to the Met on WhatsApp something like «the weekend promo is now 2x1» or «the discount goes up to 20 %». The Met searches Storyblok's Management API for the operation that reads stories, gets the promotion's story with only the fields it needs, finds the operation that updates it, reads which parameters it takes and, if the admin turned on the write tool, which starts turned off, runs it with the new text or price. Depending on what the skill says, it publishes the story in the same step, and the change goes live on your site, or it saves it unpublished for your team to review. Then it reads the story again to check the change and leaves a note on the owner's contact with what changed.

What starts it

When the customer writes

It starts when the owner or someone on the team writes to the Met on WhatsApp with a promotion change. There is no trigger to configure: the Met handles it in that conversation.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Content Met that keeps promotions up to date in Storyblok

Social team

This is not a named, seeded Met. It is a Met that serves the team, not customers, with Storyblok connected: its work ends when the promotion is updated, published or saved as the skill says, and the note of the change is on the contact.

Run by the content and social Met

Channels: WhatsApp

What you need connected

Storyblok Automate and collaborate
Meteor CRM Sell and serve

6 steps · 5 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

1
Find the operation that reads stories

The Met searches Storyblok's Management API by keyword and gets the ID of the operation that retrieves stories, with its behavior hints and the fields it returns.
- search Storyblok
2
Learn which parameters it takes

The Met asks for that operation's detail: the path and query parameters, the space ID it needs and which execute_ tool matches it.
- describe Storyblok
3
Get the promotion's story

The Met runs the read in the space the skill names and gets the promotion's story by its slug, asking only for the fields it needs, such as the title and the price.
- execute_readonly Storyblok
4
Update the promotion

The Met searches for and describes the operation that updates a story, and runs it with the new text or price. execute_mutating starts turned off: the admin turns it on for this step. If the skill says so, it publishes in the same step and the change goes live; if not, it saves it unpublished.
5
Check the change

The Met gets the story again and confirms the field holds the value the owner asked for, before telling them the change is done.
- execute_readonly Storyblok
6
Leave a note of the change

The Met adds an internal note to the owner's contact with the promotion that changed, the old value, the new one and whether it was published or saved unpublished.
- crm_add_note Meteor CRM

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

Storyblok connected with writing on

In Met, open Connections → Storyblok → Connect and sign in with an account that can edit the site's space. The admin turns on execute_mutating, which starts turned off, and leaves execute_destructive off.
A Met that serves only your team

Connect Storyblok on a Met your team uses, not on the one that serves customers: the Met does not check by itself who is writing, and anyone talking to it could ask for a change.
The space, the folder and the publish rule in the skill

Write in the skill the space ID, where the promotions live and whether the Met publishes in the same step or leaves the story saved unpublished.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not ask you for confirmation in the chat before updating or publishing: if the admin turned on execute_mutating, which starts turned off, it runs the operation.
It does not change the promotion's photo: uploading files needs a console to send the file, and someone on the team does that.
It is not deterministic: Storyblok states the server is not meant for bulk, repeatable changes, and points to its CLI for that.
It does not tell who is writing. That is why it goes on a team Met and not on the customer line.
It does not delete old promotions. This procedure does not use execute_destructive, which starts turned off until the admin turns it on.

FAQ

Questions about this automation

Yes. Storyblok advises testing first in a sandbox space that mirrors production, and you can tell it in the skill to save without publishing.

This procedure does not create stories: if the read does not return the promotion, the Met tells the owner. If you want it to create stories, that goes in another skill instruction.

Yes, in the internal note on the owner's contact in Met, with the promotion, the old value, the new one and whether it was published.

Keep going