Modules you can drive over MCP

Ondes PRO Automations: workflows drafted by your AI

Ondes PRO automations chain a trigger and a series of steps — wait, check a condition, send an email, create a promo code, update the CRM. Through the MCP server, your AI assistant drafts them from a single sentence: it creates a draft, tests it with no side effects on a sample or a real case, and tells you what is missing. Publishing stays a human decision: you review the flow, then switch it on.

Updated on

Look after Arc floor lamp buyers

Atelier Lumen wants to take care of customers who buy its brushed-brass floor lamp, and give them a reason to come back. The marketing lead describes the flow to her assistant.

Claude · Example conversation · demo data (Atelier Lumen)
  1. You : Draft an automation: when an order containing an Arc floor lamp is paid, wait 14 days and send brushed-brass care tips; then, if there is no new order within 60 days, offer a 10% code valid for a month.
  2. MCP tool : ondes_appeler POST automations/automations/ia-creer/ — draft created, with two remarks.
  3. MCP tool : ondes_appeler POST automations/automations/{id}/tester/ — dry run on a real order: no email sent, no code created.
  4. Assistant : The “Arc floor lamp follow-up” draft is ready: order paid → wait 14 days → email “Caring for brushed brass” → wait 60 days → if no new order, 10% code valid for 30 days plus an email. The dry run on Résidence Les Pins’s order clears every step. Two remarks: the promotional email will carry an unsubscribe link, and I suggest a daytime sending window.
  5. You : Great. Add a 9am–7pm window and publish.
  6. MCP tool : ondes_appeler POST automations/automations/{id}/enregistrer/ — sending window added to the draft.
  7. Assistant : The window is saved in the draft. Publishing I will leave to you: it makes you the owner of the flow, which will act on your behalf. Open it in Automations, review both emails, then click “Publish”.

Building an automation with AI: how does it work?

You describe the outcome in plain language. Your assistant, connected over MCP, calls the ia-creer/ action of the automations/automations resource, which turns the request into a flow: one or more triggers, then steps. A block the catalogue does not know is removed and flagged, never made up — the draft only contains what the engine can actually run.

The assistant can then refine the draft (enregistrer/), preview an email on a real case (apercu-email/), send you a test copy (email-test/) or dry-run the whole path (tester/). None of these actions sets anything off for your customers. To see how automations compare with integration tools such as Zapier, Make or n8n, read our comparison.

Why publishing stays a human decision

A published automation acts on behalf of whoever switches it on: it sends emails from your store, creates promo codes, edits CRM records, sometimes for months. That is a commitment, and it belongs to someone who has read the flow.

Hence Ondes PRO’s rule: an API key can only prepare drafts — create, save, preview, test, duplicate, or delete a never-published draft. Publishing, activating, pausing and launching a flow are refused. An OAuth connection carries your full permissions; even then, we recommend publishing from the editor after review, and Ondes PRO’s built-in assistant only ever creates drafts.

What an AI can do, depending on how it connects

ActionAPI keyOAuth connection
Create a draft from one sentenceYesYes
Edit, preview, test a draftYesYes
Read run history and logsYes (read-only)Yes
Publish, activate, pause, launchRefusedPossible with your permissions — do it after review
Stop or retry a runRefusedPossible with your permissions

An OAuth connection carries the full identity of the person who authorises it. For access limited to drafts, use an API key.

What you can automate in Ondes PRO

The catalogue is shared by the editor, the AI and the engine: a block exists everywhere or nowhere.

  • Triggers: order paid, abandoned cart, low stock, inactive customer, invoice issued, paid or overdue, quote about to expire, document signed, support ticket resolved, Kanban card created or moved, newsletter sign-up, incoming webhook.
  • Logic: wait for a delay or an event (“was the email opened?”), if / else, split into branches, stop.
  • Actions: email laid out in your company’s colours, promo code, CRM update, order status, calendar event, Telegram message, outgoing webhook, AI drafting or classification.
  • Tracking: per-step counters — passes, emails opened and clicked, unsubscribes, errors, attributed orders.

The engine’s safeguards once a flow is live

  • A frozen version: you edit a draft, the engine runs a published version. People already partway through finish the flow as it was.
  • Permissions re-checked: before every action the engine checks that the owner still has the module involved; if not, the automation pauses and the owner is notified.
  • Unsubscribes respected: promotional emails carry an unsubscribe link, and a cap limits promotional sends per person per day.
  • Silent imports: a bulk order import does not trigger anyone.
  • Test objects: an order created in test mode only triggers simulated actions.

For developers: plugging in a website or an external tool

An external website can feed a flow: the newsletter/ action signs up an address and starts the “Newsletter sign-up” journey, and an “incoming webhook” trigger receives events from another tool. The automations/executions resource can be read with a read-only key, to follow who went through which flow and spot failures.

Your coding assistant finds all of this without guessing: ondes_ressource gives each resource’s exact sheet, ondes_guide the automations section, ondes_exemple complete recipes. The guide to automating with AI walks through a full case.

Keep exploring

Frequently asked questions

Can an AI build an automation from one sentence?

Yes. Connected to Ondes PRO over MCP, your assistant turns a plain-language request into a draft automation: triggers, waits, conditions, emails, actions. A block the catalogue does not know is removed and flagged, never made up.

Can the AI switch an automation on by itself?

With an API key, no: publishing, activating, pausing and launching are refused, so it only prepares drafts. An OAuth connection carries your full permissions; we recommend publishing yourself from the editor after review, since the flow will act on your behalf.

Can I test an automation without sending emails?

Yes. The tester/ action dry-runs the whole path, on a sample or a real case (an order, a cart, an address), without writing or sending anything. email-test/ sends a step’s email to you alone.

How is this different from Zapier, Make or n8n?

Those tools connect different pieces of software through scenarios you build and maintain. Ondes PRO automations react directly to events in your modules — orders, invoices, stock, Kanban — with no connector to configure. The two approaches complement each other; see the detailed comparison.

What happens if I edit an automation that is running?

You edit the draft. Runs in progress carry on with the published version they started on; the new version only applies once published, to new entries.

Are automations included in my plan?

Yes. Automations and the MCP server are included in every Ondes PRO plan. See pricing.

Plug your AI into your business

The MCP server is included in every plan, with no add-on or extra fee.

Create my workspaceSee pricing

Read next