WhatsApp MCP integration for AI agents.
Connect AI agents to WhatsApp through 17 structured actions, including get business profile, create message template, and delete message template. Review aut…
- ACTION CONTRACTS
- 17
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the WhatsApp integration exposes
The WhatsApp Agent App exposes 17 provider-backed actions for communication work. Its current contract lets an authorized agent get the business profile configured for a whatsapp business phone number, create a new whatsapp message template for a waba, and delete all message template variants that share the same name. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected WhatsApp account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real WhatsApp capabilities.
Showing 12 of 17 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_business_profileREADGet the business profile configured for a WhatsApp Business phone number.
INPUTS: phone_number_id / fields
create_message_templateWRITECreate a new WhatsApp message template for a WABA.
INPUTS: waba_id / name / category / language / components
delete_message_templateHIGH IMPACTDelete all message template variants that share the same name.
INPUTS: name / waba_id
get_media_infoREADGet metadata and a short-lived download URL for uploaded media.
INPUTS: media_id
get_message_templatesREADList message templates for a WhatsApp Business Account.
INPUTS: waba_id / after / limit / status / category
get_phone_numberREADGet metadata for a specific WhatsApp Business phone number.
INPUTS: phone_number_id / fields
get_phone_numbersREADList phone numbers for a WhatsApp Business Account.
INPUTS: waba_id / limit
get_template_statusREADGet status details for a specific message template.
INPUTS: template_id / fields
send_contactsWRITESend one or more contacts to a WhatsApp user.
INPUTS: phone_number_id / to_number / contacts
send_interactive_buttonsWRITESend an interactive reply-button message.
INPUTS: phone_number_id / to_number / body_text / buttons / header_text
send_interactive_listREADSend an interactive list message with sections and rows.
INPUTS: phone_number_id / to_number / body_text / button_text / sections
send_locationWRITESend a location message to a WhatsApp user.
INPUTS: phone_number_id / to_number / latitude / longitude / name
INPUT CONTRACTS
Know what the action needs before it runs.
get_business_profile
phone_number_idREQUIRED- Meta phone number ID for the WhatsApp Business number used by this action.
fieldsOPTIONAL- Comma-separated list of fields to retrieve.
create_message_template
waba_idOPTIONAL- WhatsApp Business Account ID. Omit to use the default credential WABA ID.
nameREQUIRED- Unique template name.
categoryREQUIRED- Template category.
languageREQUIRED- Template language code such as en_US.
componentsREQUIRED- Components submitted when creating the template.
delete_message_template
nameREQUIRED- Template name to delete.
waba_idOPTIONAL- WhatsApp Business Account ID. Omit to use the default credential WABA ID.
get_media_info
media_idREQUIRED- Meta media ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Business Profile
Get the business profile configured for a WhatsApp Business phone number. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_business_profileControl Create Message Template
Create a new WhatsApp message template for a WABA. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_message_templateVerify with Get Media Info
Get metadata and a short-lived download URL for uploaded media. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_media_infoSAFETY BOUNDARY
Operate WhatsApp with explicit limits
- Authorize WhatsApp with API key and grant only the provider access required by the selected actions.
- 10 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_message_template` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in WhatsApp rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the WhatsApp task completed successfully.
CONNECTION MODEL
API key
Meta access token used with the Authorization Bearer header. Generate a permanent token from the official WhatsApp Cloud API getting started guide and Meta Business Settings: https://developers.facebook.com/docs/whatsapp/cloud-api/get-started and https://business.facebook.com/latest/settings . The token should include WhatsApp Business messaging and management permissions.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 7
- WRITE SIGNALS
- 9
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by WhatsApp.