When a ticket is created in NeetoDesk, send an alert in Slack

When a customer opens a ticket in NeetoDesk, this workflow posts an alert to a Slack channel with the ticket details you choose, so your support team sees new requests where they already talk.

NeetoDesk

Slack

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.8k sites Free to import

The When a ticket is created in NeetoDesk, send an alert in Slack workflow on the FlowMattic canvas, with 2 steps across NeetoDesk, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Support teams often spend the day in Slack, not in the help desk. A new NeetoDesk ticket can sit unseen until someone remembers to check the queue. An alert in the team's channel brings each new request into the place people are already looking.

The NeetoDesk trigger fires when a new ticket is created, and FlowMattic receives the ticket data NeetoDesk sends. Next, Slack receives an alert for that ticket in a channel of your choosing. You write that message after import and drop in ticket values such as the subject and the customer's name, so readers know what the ticket is about before opening it.

Every new ticket produces one Slack post, with nothing in between to sort or skip tickets. Replies and status changes on the ticket don't post again, since the template listens only for created tickets. Task History keeps a record of each run, including what NeetoDesk sent and how Slack responded.

Small support team without a dashboard

Three agents share one Slack channel. Each new NeetoDesk ticket shows up there, and whoever is free replies in the thread to say they've picked it up.

Weekend cover

The on-call agent keeps Slack notifications on their phone over the weekend, so a ticket opened on Saturday doesn't go unseen until Monday.

Product team visibility

Developers join the alerts channel to see what customers are reporting, without logging in to NeetoDesk.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
NeetoDesk Ticket Created
Fires when a new ticket is created in NeetoDesk. The ticket data is passed on for the Slack message; create a test ticket after import so the values are captured for mapping.
Step 2Action
Slack Send Channel Message
Posts the new ticket alert in the Slack channel you choose. Connect Slack, write the message and map in NeetoDesk values such as the subject, so the team can judge the ticket at a glance.

What you need

FlowMatticCore
NeetoDesk AccountAccount
Slack AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a Router whose routes check distinct values, such as the ticket's category if NeetoDesk sends one, to send billing and technical tickets to different Slack channels.
If your support channel is private, change the step to Slack's Send Private Channel Message action, because Send Channel Message is for public channels.
Build a second workflow on NeetoDesk's Ticket Closed trigger that posts to the same channel, so the team sees which tickets have been resolved.