Automation · Customer service and scheduling
Save the requests that arrive on WhatsApp in your Base44 app and answer how they are going
An AI agent saves every request that arrives on WhatsApp in your Base44 app, answers what status it is in and logs what the customer adds.
How do I get WhatsApp requests into the app I built in Base44?
If you built an app in Base44 to track requests, appointments or orders, the Met uses it as its base. When a message arrives, it finds your project, reads the entity where you store requests to learn its fields and checks whether that customer already has an open one. If not, it creates the record with what they said; if so, it adds the new details to that request. When the customer asks how it is going, the Met queries the record and answers with the status your team has in the app. This procedure only works with records: it does not change your app's code or structure.
What starts it
When the customer writes
It starts when a customer writes on WhatsApp to leave a request or ask about one they already left. 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
Support Met that saves requests in Base44
Customer service team
This is not a named, seeded Met. It is the Met that already answers the business's WhatsApp, with Base44 connected: its work ends when the request is saved in your app, or when the customer knows what status it is in.
Run by the customer support Met
Channels: WhatsApp
What you need connected
- Base44 Automate and collaborate
5 steps · 5 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 your app in Base44
The Met lists your projects filtering by the name you wrote in the skill and keeps your app's project. It only sees projects in the workspace you chose when connecting.
- 2
Read the fields of the requests entity
The Met gets the project's entity schemas to know which fields the requests entity has, such as name, phone, details and status. That way it does not write into a field that does not exist.
- 3
Check whether the customer already has an open request
The Met queries the entity's records looking for the conversation's phone number. If it finds an open request, it works on that one and does not create a duplicate.
- 4
Create the request or add the new details
If there is no open one, the Met creates the record with what the customer said and the initial status your team uses. If it already existed, it updates only the details with what the customer added, without touching the status.
- 5
Answer how it is going
When the customer asks later, the Met queries their record and answers with the status your team left in the app. If the status has not changed, it says so, without making up progress.
Before you start
What you need ready
The Met solves none of these for you. If one is missing, the automation stops there.
-
A Base44 app with a requests entity
The app you built in Base44, with an entity that stores at least the phone, the details and a status your team keeps up to date.
-
Base44 connected in Met
With a Builder plan or higher, in Met open Connections → Base44 → Connect and choose the app's workspace. Leave the create and update record actions on.
-
A WhatsApp line with the Met assigned
The business connects its WhatsApp Business API line and assigns the Met that answers customers, with the Base44 skill.
The limits
What this automation does NOT solve
Better said here than discovered halfway through the rollout.
-
It does not change your app's code or structure: this procedure only creates and updates records. For an app in use, it is better to leave the code and sandbox actions off.
-
It does not ask for confirmation in the chat before creating or updating the record: if the action is on, it does it with what it understood from the conversation.
-
It does not move the request's status: your team still does that in the app, and the Met only reads it to answer.
-
It does not work on plans below Builder: Base44 requires that plan or a higher one to connect its MCP server.
FAQ
Questions about this automation
Yes. The Met works with whatever entity your app has, whether appointments, orders or requests, because it reads its fields before writing.
This procedure only uses record tools. The ones to change the app and write files arrive switched on; if you do not need them, the admin turns them off in Connections. Running commands and calling the platform API start switched off.
The Met searches by the conversation's phone number. If it finds nothing, it asks for a detail stored in the request, such as their name, and queries by that field.
You do, with your Base44 plan. Meteor does not resell Base44 and does not charge for the calls the Met makes to your account.
Keep going
Other automations built on the same tools
Customer service and scheduling
Open a Linear issue from a customer report on WhatsApp and tell them how it is going
How do I make customer reports on WhatsApp arrive in Linear as issues?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 6 real tools
- Needs:
- Linear
Customer service and scheduling
Open a Freshdesk ticket from WhatsApp and tell where it stands
How do I turn a complaint that arrives on WhatsApp into a Freshdesk ticket without copying it by hand?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 10 real tools
- Needs:
- Freshdesk
Customer service and scheduling
Open a Gorgias ticket from WhatsApp and escalate it to the team that solves it
How do I move a complaint that arrives on WhatsApp into Gorgias without copying it by hand or losing what the customer said?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 7 real tools
- Needs:
- Gorgias
Customer service and scheduling
Open a Jira issue from a report that comes in on WhatsApp and answer how it is going
How do I make customer reports on WhatsApp arrive in Jira as issues?
Customer service
- Starts:
- when the customer writes
- Steps:
- 5, with 6 real tools
- Needs:
- Jira y Confluence
Want this automation running on your own data?
We will show it to you with your accounts connected, not with a canned demo.