Automation · Orders and fulfillment
Accept, prepare and close Rappi orders without living on the tablet
How an AI agent receives Rappi orders by webhook, accepts them in time, marks them ready and switches off whatever sold out before somebody orders it.
How do I stop losing Rappi orders because nobody accepted them in time?
A Rappi order that is not accepted in time cancels itself, and the store pays for that cancellation. This automation registers the Rappi webhook once, so every new order reaches Meteor the moment it lands, accepts it with a prep time, marks it ready when the kitchen finishes and alerts the team on the channel they already watch. In parallel it keeps availability current: whatever sold out is switched off in the Rappi catalog, and if the location gets swamped, the store closes until it catches up.
Where it applies: Colombia. The API domain depends on the country; this automation is written on the Colombian operation.
What starts it
When the outside system calls
Rappi calls the Meteor webhook URL when a new order comes in, and that event fires the task. It is the right mechanism here: polling every minute would arrive late exactly when volume is highest.
A task on a webhook trigger: the provider posts to your Meteor URL and the procedure starts with that event.
Who runs it
Met for store operations
It is not a Met with a seeded name: it is an internal operations Met with no contact with the buyer. Its job is that no order falls through for the sake of a few minutes.
What you need connected
- Rappi E-commerce and marketplaces
6 steps · 10 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
Register the webhook once
Registration subscribes your stores to the new order event and stores the secret Rappi generates to validate the signature on every call. You run it once, after the credentials are configured. Without that secret the orders are still recorded, but they come in flagged with an invalid signature. And an order you cannot trust is not an order.
- 2
Accept the order with its prep time
Acceptance states how many minutes until it is ready, which is what Rappi uses to dispatch the courier at the right moment. The list of orders waiting to be accepted lets you review before accepting, and answers what is in the queue without touching the tablet.
- 3
Mark it ready when it actually is
Marking it ready too early leaves the courier waiting at the counter; marking it late means the food arrives cold. The order event history confirms which stage it is really in (accepted, ready, delivered) instead of trusting whoever is in the kitchen to remember.
- 4
Switch off what sold out before somebody orders it
Availability is toggled by SKU, or by Rappi's own identifier when you do not keep your own SKUs. It is the change that prevents the worst case on this channel: accepting an order for something you do not have and cancelling it with the courier already on the way.
- 5
Close the store when the kitchen is swamped
Closing the store stops new orders without rejecting them one by one. It is the clean way out of a rush that got away from you or of being open past hours, and you reopen once the kitchen catches up. Rejecting twenty orders in a row costs reputation; closing for twenty minutes does not.
- 6
Reject only with a person confirming
Rejection is destructive: the order is not prepared and the buyer gets the notice. So it always goes through a person first, and the reason is written down. The list of received events lets you review afterwards which orders came in and how they ended, with their real headers.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
Credentials for the Rappi integration
Rappi issues them when it enables its public integrations API: client identifier, secret and the domain for your country. They are configured per workspace.
-
Your Rappi store identifier
Rappi gives it to you when the location is set up. If you run a single store you can leave it as the default and stop repeating it on every operation.
-
Somebody watching the channel where the Met posts
This automation removes the tablet, not the attention. The alert lands on whichever internal channel you use, and somebody has to be on the other side to cook.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not change prices on Rappi. It only turns product availability on and off: visible or hidden, nothing else.
-
It does not manage the menu. Creating products, editing descriptions or uploading photos is still work inside the Rappi panel.
-
It does not reject orders on its own. Rejecting is destructive and notifies the buyer, so it always goes through a human confirmation.
-
It does not replace inventory control. It switches off what sold out when told to, or when another integration tells it; on its own it does not know how many units are left.
FAQ
Questions about this automation
Because the window to accept is minutes wide. A check every five minutes arrives late exactly during the rush, which is when each cancellation costs the most. The webhook delivers the order the moment it lands.
The list of received events shows the real headers of the last calls, so you can see which one Rappi is using and configure it. In the meantime the orders are still recorded, flagged as invalid signature.
Yes. The operations take a store identifier, and one webhook registration can subscribe several at once. With a single location you can set it as the default and never pass it again.
Keep going
Other automations built on the same tools
Orders and fulfillment
Quote a TCC shipment inside the conversation
How do I give a customer the cost of a TCC shipment without leaving the chat?
Finance and operations
- Starts:
- when the customer writes
- Steps:
- 5, with 8 real tools
- Needs:
- TCC · Meteor CRM
Orders and fulfillment
From a WooCommerce order to an Aveonline shipping label
How do I move orders from my store into Aveonline without retyping them one by one?
- Starts:
- at a set time
- Steps:
- 6, with 13 real tools
- Needs:
- WooCommerce · Aveonline
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.