Skip to content

Automation · Orders and fulfillment

Log the orders that arrive on WhatsApp in NocoDB and answer how they are going

An AI agent saves every order that arrives on WhatsApp in your NocoDB table, links it to the customer and answers what status it is in.

How do I get WhatsApp orders into my NocoDB base without copying them by hand?

When a customer orders something on WhatsApp, the Met finds your customers and orders tables in NocoDB and reads their fields so it does not make up columns. It looks up the customer by phone, creates the order with what they asked for and links it to the customer's record. Days later, when the customer asks how it is going, the Met queries the orders table with their phone or order number and answers with the status your team has in NocoDB. The Met does not change the status: your team still does that, because updating records starts switched off.

What starts it

When the customer writes

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

Orders Met that keeps the base in NocoDB

Customer service team

This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with NocoDB connected: its work ends when the order is logged and linked to the customer, or when the customer knows what status their order is in.

Run by the customer support Met

Channels: WhatsApp

What you need connected

5 steps · 6 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. 1

    Find the customers and orders tables

    The Met lists the tables in the base you named in the skill and keeps the customers table and the orders table. If the connection does not reach that project, it cannot see them: you need to add it in the NocoDB authorization.

  2. 2

    Read the fields before writing

    The Met gets each table's schema to know which fields exist, such as product, quantity, address or status, and which link field connects order and customer. That way it does not write into a column your team never created.

  3. 3

    Find the customer or register them

    The Met queries the customers table filtering by the conversation's phone number. If they are not there, it creates their record with name and phone; if they are, it keeps their ID.

  4. 4

    Create the order and link it to the customer

    The Met creates the order record with what the customer asked for and the initial status your team uses, and links it to the customer's record through the link field, without touching the other links.

  5. 5

    Answer how the order is going

    When the customer asks later, the Met queries the orders table with their phone or order number and answers with the status the record has. If they have several orders, it counts how many are open before listing them.

Before you start

What you need ready

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

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

Only if the admin turns on the update action, which starts switched off because NocoDB marks it as destructive. This procedure leaves the status to your team.

The Met searches by the conversation's phone number. If it cannot find it, it asks for the order number and queries by that field.

Yes. If your base keeps everything in one orders table with the phone as a field, the Met skips linking to the customer.

Up to 100 records per call, but in this procedure it creates one per conversation: the order the customer just placed.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.