Automation · Orders and fulfillment

Store the orders that come in on WhatsApp in a Craft collection, with their task

An AI agent logs each order that comes in on WhatsApp in your Craft collection, creates the task for your team and marks it once it is ready.

Show me this with my own operation See every automation

How do I log the orders I get on WhatsApp in Craft without copying them by hand?

A Met connected to Craft finds the collection where your team keeps orders and reads its schema to know which fields it has. When a customer orders something on WhatsApp, it checks whether they already have an open order and, if not, adds the row with their name, phone number, what they asked for and the date. Then it creates the task for the person who prepares it. When the team tells the Met the order is ready, it updates the row, marks the task done and tells the customer. Everything stays in the Craft space where your team already works.

What starts it

When the customer writes

It starts when a customer writes on WhatsApp to order something or ask about an order they already placed. There is no trigger to configure: the Met assigned to the line runs the procedure inside 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

Sales Met that logs orders in Craft

Sales team

This is not a named, seeded Met. It is the Met that already sells on the business's WhatsApp, with Craft connected. Its work ends when the order is logged with its task, and later when the customer knows their order is ready.

Run by the sales closing Met

Channels: WhatsApp

What you need connected

Craft Automate and collaborate

6 steps · 7 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 orders collection

The Met lists the collections in the Craft space and keeps the one the skill names, for example "Orders", without touching the others.
- collections_list Craft
2
Read its fields

Before writing, the Met reads the collection's schema to know which fields it has, such as customer, phone, order, date and status, and not invent one that does not exist.
- collectionschema_get Craft
3
Check whether there is an open order

The Met pulls the collection's rows and looks for the customer's by phone number. If they have an open order, it answers about that one instead of logging a duplicate.
- collectionitems_get Craft
4
Log the new order

If there is no open one, the Met adds the row with the name, phone number, what they asked for and the date, and confirms to the customer that it was logged.
- collectionitems_add Craft
5
Create the task for the team

The Met creates the task in Craft with what needs to be prepared, so the person who does it sees it on their list without reading the chat.
- tasks_add Craft
6
Close the order once it is ready

When the team tells the Met the order is ready, the Met updates the row's status, marks the task done and tells the customer on WhatsApp.
- collectionitems_update Craft
- tasks_update Craft

Before you start

What you need ready

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

An orders collection in Craft

Your team keeps orders in a Craft collection with clear customer, phone, order, date and status fields. The Met only fills the fields that exist.
Craft connected in Met

In Met, open Connections → Craft → Connect and approve access to the orders space. The admin leaves adding and updating rows, and creating and updating tasks, switched on.
A WhatsApp line with the Met assigned

The business connects its WhatsApp Business API line and assigns the Met that answers customers. Orders arrive there; Craft is where they are logged.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

It does not charge for the order: it only logs it and sends updates. To charge, the Met needs another payments integration.
It does not know the order is ready unless someone tells it: the team tells the Met or updates the row in Craft, and the Met answers with that.
It does not ask for confirmation in the chat before logging or creating the task: if the action is on, it does it. The admin decides which writes stay on.
It does not delete old or duplicate orders: deleting rows starts switched off, and a person does that cleanup.

FAQ

Questions about this automation

Yes, because that is where everything lives: the row in the collection and the task on the list. That is the point, so the team does not have to read the WhatsApp chat.

The Met reads the schema every time, so it fills the new fields if the skill tells it what goes in each one.

Craft's documentation does not explain how to assign a task over MCP. The Met creates it with what needs to be prepared and, if the skill says so, the assignee's name in the text.

Your Craft plan. Meteor does not resell Craft or charge per logged order.

Keep going