# Create Teams notifications for new tickets in ConnectWise: n8n workflow

> Started by a clock, and works across Redis. 8 steps: small enough to read in one sitting and change without fear.

Source: https://millionrounds.com/workflow/create-teams-notifications-for-new-tickets-in-connectwise (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Customer support](https://millionrounds.com/workflows?category=Customer+support#library)

# Create Teams notifications for new tickets in ConnectWise

Started by a clock, and works across Redis. 8 steps: small enough to read in one sitting and change without fear.

Small

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fcreate-teams-notifications-for-new-tickets-in-connectwise)

**8 steps** Small: readable in one sitting

**0** Branches: places the flow splits

**0** Loops or waits

**1** Service it connects to

## The flow

Starts it 1 Logic 3 Service 4

The steps in the order they run, from what starts it.

- 1 **Schedule Trigger** Schedule trigger *Starts it*
- 2 **Get New Tickets** Http Request *Service*
- 3 **Query Database** Redis *Service*
- 4 **Add Filterable Parameter** Code *Logic*
- 5 **Filter Out Tickets that have already been sent** Merge *Logic*
- 6 **Combine like Companies** Code *Logic*
- 7 **Log in Redis** Redis *Service*
- 8 **Teams to Dispatch** Microsoft Teams *Service*

## How it's built

- **Starts on:** A clock
- **Steps:** 8
- **Size:** Small: readable in one sitting
- **Connects to:** Redis
- **Model:** None. This is plumbing, not judgement

## Questions

What does it need to run?

An n8n account, plus your own Redis account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Not long. At 8 steps it can be read in one sitting and changed without fear.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

**Before you run it**

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 8 steps before you point it at anything that matters.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fcreate-teams-notifications-for-new-tickets-in-connectwise)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[Redis](https://millionrounds.com/workflows?service=Redis#library)

## Workflows like it

Also customer support, with the same services where possible, closest in size first.

- [**Customer authentication for chat support with OpenAI and Redis** 14 steps · calls a model · Redis](https://millionrounds.com/workflow/customer-authentication-for-chat-support-with-openai-and-red)
- [**Advanced Telegram bot, ticketing system, liveChat, user** 31 steps · Redis, Telegram](https://millionrounds.com/workflow/advanced-telegram-bot-ticketing-system-livechat-user)
- [**WhatsApp to Chatwoot message forwarder with Postgres and Redis** 31 steps · Postgres, Redis](https://millionrounds.com/workflow/whatsapp-to-chatwoot-message-forwarder-with-postgres-and-red)
- [**WhatsApp AI customer service chatbot – handles text, voice** 37 steps · calls a model · Google Drive, Postgres](https://millionrounds.com/workflow/whatsapp-ai-customer-service-chatbot-handles-text-voice)