# WhatsApp Trigger node

Use the WhatsApp Trigger node to respond to events in WhatsApp and integrate WhatsApp with other applications. n8n has built-in support for a wide range of WhatsApp events, including account, message, and phone number events.

On this page, you'll find a list of events the WhatsApp Trigger node can respond to, and links to more resources.

Credentials

You can find authentication information for this node [here](../../credentials/whatsapp/).

Examples and templates

For usage examples and templates to help you get started, refer to n8n's [WhatsApp integrations](https://n8n.io/integrations/whatsapp-trigger/) page.

## Events

- Account Review Update
- Account Update
- Business Capability Update
- Message Template Quality Update
- Message Template Status Update
- Messages
- Phone Number Name Update
- Phone Number Quality Update
- Security
- Template Category Update

## Related resources

n8n provides an app node for WhatsApp. You can find the node docs [here](../../app-nodes/n8n-nodes-base.whatsapp/).

View [example workflows and related content](https://n8n.io/integrations/whatsapp-trigger/) on n8n's website.

Refer to [WhatsApp's documentation](https://developers.facebook.com/docs/whatsapp/cloud-api) for details about their API.

## Common issues

Here are some common errors and issues with the WhatsApp Trigger node and steps to resolve or troubleshoot them.

### Workflow only works in testing or production

WhatsApp only allows you to register a single webhook per app. This means that every time you switch from using the testing URL to the production URL (and vice versa), WhatsApp overwrites the registered webhook URL.

You may have trouble with this if you try to test a workflow that's also active in production. WhatsApp will only send events to one of the two webhook URLs, so the other will never receive event notifications.

To work around this, you can disable your workflow when testing:

Halts production traffic

This workaround temporarily disables your production workflow for testing. Your workflow will no longer receive production traffic while it's deactivated.

1. Go to your workflow page.
1. Toggle the **Active** switch in the top panel to disable the workflow temporarily.
1. Test your workflow using the test webhook URL.
1. When you finish testing, toggle the **Inactive** toggle to enable the workflow again. The production webhook URL should resume working.
