Connect customer service actions to your next process.
Connect TappyWhats events to n8n or your own system with webhooks sent directly from your browser. Assigning a tag or creating a note can send an event straight from your browser to a configured endpoint. Choose the data you share, then inspect each delivery instead of copying updates between systems.
A Pro feature, subject to your plan entitlements. Requires a computer that is on, internet access, an open browser, the extension active in WhatsApp Web, a reachable endpoint and browser permission for its address. Settings, secrets and logs stay in this browser. Local history is limited to 500 deliveries; records older than seven days are pruned when new deliveries are added. It is not a permanent archive.
TappyWhatsConnect WhatsApp activity to the next step in your process
Open Local webhooks and add an endpoint with a name and HTTPS URL. Set a signing secret or let the extension generate one. Grant browser access to the requested destination address.
Connect WhatsApp activity to the next step in your process
Add an endpoint from n8n, Make, Zapier or your own system. The extension sends events directly to that URL, without a TappyWhats server relay. You configure the receiving workflow in the destination tool.
Choose which events each destination URL receives.
Control shared data and verify HMAC-SHA256 signatures at your endpoint.
Test the connection, inspect statuses and responses, and resend deliveries manually.
- 01
Add your destination
Open Local webhooks and add an endpoint with a name and HTTPS URL. Set a signing secret or let the extension generate one. Grant browser access to the requested destination address.
- 02
Choose events and data
Select implemented events that your workflow needs, review privacy settings for that endpoint and activate it. Inclusion controls cannot add information that was absent from the original event.
- 03
Test and monitor
Send a test and check the response. After a real action, review the delivery status, attempts and errors in the logs. Fix the receiving endpoint and use manual resend when needed.
Illustrative example: quote requests in a spreadsheet
A shop assigns a “Quote requested” tag during a conversation. The tag.assigned event reaches n8n, where a prepared workflow matches the tag identifier and writes the contact identifier and date to Google Sheets. Set up that workflow in n8n; the event does not automatically include a name, phone number or conversation.
Illustrative example with fictional data.What to know before you install.
A Pro feature, subject to your plan entitlements. Requires a computer that is on, internet access, an open browser, the extension active in WhatsApp Web, a reachable endpoint and browser permission for its address. Settings, secrets and logs stay in this browser. Local history is limited to 500 deliveries; records older than seven days are pruned when new deliveries are added. It is not a permanent archive.
Explore plansDoes it work with the browser closed?
No. New events are neither captured nor sent while the extension is inactive. Existing pending deliveries may resume when the extension starts again, provided they remain in local history. Actions that occurred during the interruption have no guaranteed recovery.
What data leaves the browser, and how do I verify it?
Phone numbers are masked by default, and message content, note data and monetary values are omitted. Each endpoint has its own controls. Verify the HMAC-SHA256 signature at the receiver using the same secret: it authenticates the delivery, but does not encrypt the content. Available data depends on the original event.
Which events can I use now?
Current emitters cover contact creation, tag assignment and removal, note creation, follow-up creation and completion, source assignment, remarketing actions and backup exports or imports. Technical examples include contact.created, tag.assigned and note.created. Selecting a catalog item marked as upcoming does not make it emit events.
What happens if my endpoint fails?
Logs show the status, attempt count, HTTP response and error. While running, the extension retries up to five total attempts. You can also manually resend a recorded delivery. Check the URL, browser permission and endpoint availability; these tools do not guarantee delivery.
Ready to use this feature?
Choose which events each destination URL receives.
