Does Ominiflow have an Uber Eats integration?
Connect Uber Eats order events to the WhatsApp Business API. Alert the store on a real number, and message diners only when they opted in — the marketplace phone is usually a relay. No native Uber Eats connector. Connect the order event from your POS, an Uber Eats partner webhook, or Make, then send WhatsApp from Ominiflow.
Last updated: 8 October 2026
An Uber Eats WhatsApp API integration sends a WhatsApp message when an Uber Eats order event fires. The reliable message is to your store, on a number you control. The diner’s number inside Uber Eats is usually a temporary relay, so it is not a WhatsApp recipient.
This guide is the wiring: which event to listen for, what to send the kitchen, and the only path that lets you message the customer later. It is not a native “Connect Uber Eats” button. Ominiflow does not ship an Uber Eats app. You connect an order webhook, a POS, or Make to the WhatsApp API.
Too long? Start here
- Do this first: new Uber Eats order → WhatsApp template to the store manager’s own number.
- Do not send that template to the phone Uber Eats shows on the order. It is often a masked relay, not the diner’s WhatsApp.
- Customer WhatsApp starts when they opt in themselves: QR on the bag, your site, or a past direct order.
- Uber Eats is not in India. Zomato took the India business in January 2020. The same relay-number rule applies to Swiggy and Zomato.
- Templates for “order accepted” and “running late” are utility. “Order direct next time, skip the app fee” is marketing and needs a separate opt-in.
What this integration actually is
Uber Eats is the marketplace. The WhatsApp Business API (Cloud API) is Meta’s channel for a business number. Ominiflow is the inbox, templates, and webhook layer in between.
Three systems have to agree:
- Uber Eats creates the order and tells a partner system (your POS, or Uber’s order webhook if you are an approved partner).
- Your middleware — POS, Make, or a small webhook — reads the order id, items, and prep time. It does not treat the customer contact field as a WhatsApp number.
- Ominiflow sends an approved template to a number you already have consent for, or opens the team inbox so a person replies.
The send path is the same as any other order system: WhatsApp API integration guide. If you do not want to write code, the same event can land in Make: Make + WhatsApp.
If you are in India
You cannot connect a live Uber Eats India store. Uber Eats stopped taking consumer orders in India in January 2020, when Zomato acquired that business. A 2026 “Uber Eats India WhatsApp” setup has no marketplace on the other end.
Indian restaurants still need this pattern for Swiggy and Zomato. Those apps also hide the diner’s real mobile behind a relay. If those tickets land in Petpooja, alert the store and keep the relay off WhatsApp: Petpooja WhatsApp API integration. Direct reservations on your own number: table reservations on WhatsApp.
Why the Uber Eats phone number fails on WhatsApp
Uber shows restaurants a contact number so the store can call about a missing item or a gate code. On the Order API that value is a privacy relay. It expires. It is meant for a voice call during that delivery, not for a WhatsApp template at 9pm.
If you pass it to Cloud API you get a failed send, or you message a line that is not the guest’s WhatsApp. Neither helps the order. Do not store that relay in your WhatsApp contact list.
You may message the guest on WhatsApp only when you collected the number and they opted in. Typical sources:
- QR on the bag or receipt: “Message us for the next order.”
- Your own site or WhatsApp menu, not the Uber Eats checkout.
- A previous dine-in or direct-delivery booking where they ticked WhatsApp updates.
A match between an Uber Eats order and an old opt-in is allowed only when you are sure it is the same person and the consent still covers this message. A marketing “skip the app fee” blast to every Uber customer is not utility traffic. Meta will treat it as marketing without opt-in.
Architecture
- Order placed on Uber Eats.
- POS or webhook receives the order (UrbanPiper, Deliverect, your own listener, or Make).
- Filter drops cancelled tests and orders with no items.
- Ominiflow sends one utility template to the store WhatsApp number, with order id, item count, and promised ready time.
- Optional: if the payload includes a first-party phone you already opted in, send the guest a separate utility template. If not, stop.
- Reply lands in the Ominiflow shared inbox. A late order is a person typing a new ready time, not a second marketing blast.
Keep the store number and the guest number in different automations. Mixing them is how a kitchen alert gets sent to a customer, or a customer delay note gets sent to the masked relay.
How to set it up
- Put the restaurant on Cloud API. Display name should match the store guests already know. Onboarding outline: API onboarding checklist.
- Opt in the store phone. The manager’s mobile, in E.164. That number receives the order alert. One store, one alert number, or one number per outlet if you run several kitchens.
- Submit two utility templates before you go live. Approval is hours to a couple of days. Samples are in the table below.
- Catch the Uber Eats order. If your POS already ingests Uber Eats, trigger from the POS “order created” event. If you are an Uber Eats API partner, use the order notification webhook. If you are neither, start with Make polling or a POS that already has the connector. Do not scrape the Uber Eats Manager screen.
- Map four fields: order id, item count or short item list, ready-by time, store name. Leave the customer phone out of this first flow.
- POST to Ominiflow to send the template. Same pattern as any order webhook: integration guide.
- Test with a real order on a staff Uber Eats account. Confirm the manager receives WhatsApp, and confirm nothing is sent to the relay number.
- Add the bag QR only after the alert is stable. The QR opens your WhatsApp with a pre-filled “direct order” message so the next sale is yours, not another marketplace order.
Flows worth building
1. Store order alert
Trigger: Uber Eats order created and accepted. Recipient: manager WhatsApp. One message per order. Body is the order id, how many items, and the ready time you sent Uber. This is the integration. Everything else is optional.
2. Guest delay, only with opt-in
Trigger: kitchen marks the order late. Recipient: a guest number you collected yourself. Utility template with the new time and the order id. No coupon in this message. A discount makes it marketing.
3. Cancellation
Trigger: order cancelled. Tell the store so they stop cooking. Tell the guest only if you have their real number and the cancellation needs them to do something. Uber Eats already notifies them in the app.
4. Direct reorder
Trigger: guest messages the QR, or a week later if they opted into offers. Marketing template, separate consent from “order updates.” Offer your own menu link or a WhatsApp catalogue. This is how the integration pays for itself: the first order stayed on Uber Eats; the second does not pay the marketplace commission.
Own-store orders, where you do have the phone at checkout, follow the Shopify pattern: Shopify WhatsApp integration and order confirmation copy.
Templates
| Flow | Category | Who receives it | Sample body |
|---|---|---|---|
| New order | Utility | Store manager | Uber Eats {{1}}: {{2}} items. Ready by {{3}}. Order {{4}}. |
| Running late | Utility | Guest, opted in | Hi {{1}}, order {{2}} is delayed. New ready time {{3}}. |
| Cancelled | Utility | Store manager | Uber Eats {{1}} cancelled. Stop prep if it has not left the kitchen. |
| Order direct | Marketing | Guest, marketing opt-in | Hi {{1}}, next time order from us on WhatsApp and skip the app fee: {{2}} |
Variable rules and categories: template message API guide.
Opt-in
- The store manager opts in when you register that number for alerts. Write it down.
- A guest opt-in is a checkbox or a WhatsApp reply they sent you, with a time and a source. The Uber Eats checkout is not that checkbox.
- Utility copy stays transactional. Ready time, order id, cancellation. No “20% off.”
- Marketing copy lives in its own template and its own consent.
- STOP on the guest thread suppresses future marketing the same day.
- Do not export Uber Eats relays into a broadcast list.
Troubleshooting
| What you see | Cause | Fix |
|---|---|---|
| Template fails as soon as the order lands | You sent the Uber relay number | Send the store number only |
| Manager gets nothing | POS event never left Uber Eats | Check the POS Uber Eats connection, then the Ominiflow webhook log |
| Double alerts | Webhook retried and you sent again | Deduplicate on Uber Eats order id |
| Meta rejects the “direct reorder” template as utility | The body is an offer | Resubmit as marketing |
| Guest says they never agreed | You matched an Uber order to an old number by guess | Stop. Only message numbers with a stored opt-in |
FAQ
Does Ominiflow have an Uber Eats integration? expand_more
No native Uber Eats connector. Connect the order event from your POS, Uber’s partner webhook, or Make, then send WhatsApp from Ominiflow.
Can I WhatsApp every Uber Eats customer? expand_more
No. The number on the order is usually a temporary relay for phone calls. WhatsApp the guest only after they give you their real number and opt in.
Does Uber Eats work in India? expand_more
Not as a consumer delivery app. Uber Eats India moved to Zomato in January 2020. Use the same alert pattern for Swiggy or Zomato, and use WhatsApp for your own reservations and direct orders.
What does the WhatsApp side cost? expand_more
Ominiflow plans start at ₹15,000/year in India, or $99/month on the USD Scale plan. Meta conversation fees are passed through at cost. A store alert is a utility conversation. A “order direct” offer is marketing and is priced as marketing. India rates on the pricing page: marketing ₹0.86, utility and authentication ₹0.115 per 24-hour conversation.
How fast can a restaurant go live? expand_more
The store-alert flow is one template plus one webhook. Most teams send the first real order the same week the template is approved. Guest marketing waits until opt-ins exist. It should not be in version one. Set up restaurant WhatsApp alerts → Related: WhatsApp table reservations · Shopify order integration · Cloud API setup Updated October 2026. Uber Eats has no consumer marketplace in India (Zomato, January 2020). Customer contact fields on marketplace orders are treated as call relays, not WhatsApp numbers.
