If your team lives in Discord, let tawk.to tell them when a visitor starts a chat, leaves a ticket or finishes a conversation. Alerts go to the right channel or person, offline tickets become forum posts the team can claim, and ended chats can arrive as a short summary.
9 triggers 12 actions 6 example workflows 1 ready-made template Unlimited runs
When this happens in Tawk.to3 triggers
Do this in Discord12 actions
1. TriggerChat Start2. ActionSend Channel MessageWhen Tawk.to fires Chat Start, FlowMattic runs Send Channel Message in Discord with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateA visitor waiting in the chat widget becomes a message in your support channel, with their name and first message, so whoever is free can pick it up.
Chat StartSend Channel Message
View the template Tickets left while nobody was online become forum posts, one per ticket. Agents reply in the thread to say they have it, so two people never answer the same customer.
Capture New TicketCreate new Forum Post
An AI Agent reads the finished chat and writes three lines: what the visitor wanted, what was promised and what is still open. The team reads that instead of the full transcript.
Chat EndAI AgentSend Channel Message
Agencies running tawk.to on several client sites use a Router on the property name, so every client's chats appear in that client's channel and nowhere else.
Chat StartRouterSend Channel Message
A Lookup Table holds who covers each tawk.to property. Discord finds that member by name and sends a direct message, which is harder to miss than a busy channel.
Chat StartLookup TableFind UserSend Direct Message
A Filter checks the ticket text for words like refund or charge, and only those tickets reach the billing channel, keeping money questions out of the public support room.
Capture New TicketFilterSend Channel Message
Once set up, each new tawk.to chat posts a message in the Discord channel you pick.
In FlowMattic, open Connects and add a Discord connection for the server where your support channel lives.
Create a workflow, choose Tawk.to and the Chat Start trigger, and follow the steps shown to link your tawk.to property.
Open your site in a private window and start a chat so FlowMattic captures the visitor and chat fields.
Add a Discord step with Send Channel Message, choose the channel, write the message from the chat fields, test it and switch the workflow on.
1. Trigger in Tawk.to
Chat Start
2. Action in Discord
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From Tawk.to | To Discord |
|---|---|
| Visitor name | Message: who |
| Visitor email | Message: contact |
| First message | Message: what they asked |
| Property name | Message: which site |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Tawk.to and Discord connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Visitor names, emails and messages go from tawk.to to Discord through your own WordPress server, not another automation company.
Runs are unlimited, so a launch day with hundreds of chats needs no larger plan than a quiet Sunday.
Channel messages, forum posts and direct messages are all available, so each kind of tawk.to event can go to the place that suits it.
FlowMattic receives the tawk.to event, such as Chat Start, Chat End or Capture New Ticket, and passes its details to a Discord action like Send Channel Message. You build and test the workflow on the canvas in your WordPress admin.
No. These workflows run from tawk.to to Discord, so replies still happen in the tawk.to dashboard or app. Discord is where the team is told and decides who answers.
Yes. Put a Router after the trigger with one path per tawk.to property and point each path's Send Channel Message step at that site's channel.
Start the workflow with Chat End and post the chat details to a channel. Many teams add an AI Agent step first so the message is a short summary rather than the full conversation.
Yes. Use Create new Forum Post on a forum channel. Each ticket gets its own post, and later updates or replies from the team stay inside that thread.
Did not find your answer? You can browse the help center or ask us directly.
Discord and Google Sheets8 shared templates
Discord and Telegram7 shared templates
Discord and WordPress6 shared templates
Discord and Notion6 shared templates
Discord and ClickUp5 shared templates
Discord and Airtable5 shared templates
Discord and Slack4 shared templates
Discord and AI Agents4 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Tawk.to integration 1.0, Discord integration 1.1.1.
