How do I import "New Ticket Alerts to Teams" into n8n?

Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.

Which integrations does "New Ticket Alerts to Teams" use?

It uses: schedule, redis, httpRequest, microsoftTeams. The flow diagram above shows how each service connects across the 8 nodes. Filter OpenRuna by integration to find related workflows and tools.

Can I import a sanitized export without credentials?

Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own schedule and redis credentials in n8n after import.

What trigger type does "New Ticket Alerts to Teams" use?

Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.

Is "New Ticket Alerts to Teams" free to use?

OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for schedule, redis, httpRequest, microsoftTeams.

← Workflows

New Ticket Alerts to Teams

8 nodes · schedule, redis, httpRequest, microsoftTeams

Engine: n8n
Nodes: 8
Trigger: scheduled/triggered
Source file: 1933_Redis_Code_Create_Webhook.json

Workflow flow

IntegrationsSchedule

RedisHTTPMicrosoftTeamsCodeMerge

100%

TRIGGER

Schedule Trigger

Schedule

Get New Tickets

HTTP

Add Filterable Parameter

Code

Query Database

Redis

Filter Out Tickets that have already been sent

Merge

Combine like Companies

Code

Redis

Teams to Dispatch

MicrosoftTeams

8 steps · flows top to bottom, branches left to right

Browse by integration

schedule redis httpRequest microsoftTeams

Browse all integrations →

Download n8n JSON Download sanitized JSON Download flow graph

Import into n8n

Download the n8n JSON file (full or sanitized).
In n8n: Workflows → Import from file.
Open each node and reconnect credentials to your accounts.
Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: New Ticket Alerts to Teams. 8 nodes across schedule, redis, httpRequest, microsoftTeams, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "New Ticket Alerts to Teams" chains 8 nodes to move data between schedule, redis, httpRequest, microsoftTeams. 8 nodes · schedule, redis, httpRequest, microsoftTeams Execution begins at the scheduled/triggered trigger and flows through the 8 configured nodes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

Study how data moves from schedule to redis before building your own variant.
Share it with your team as a documented reference for scheduled/triggered automations in the schedule stack.
Import "New Ticket Alerts to Teams" into n8n, reconnect credentials for schedule, redis, httpRequest, microsoftTeams, and run the same automation in your own workspace.
Use it as a starting template when wiring schedule, redis, httpRequest, microsoftTeams — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "New Ticket Alerts to Teams" exposes 8 configured nodes. Trigger type: scheduled/triggered. Integrations: schedule, redis, httpRequest, microsoftTeams. Set your credentials on the schedule node, then verify each downstream node picks them up. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "New Ticket Alerts to Teams" JSON into a plain-English runbook, node by node. It can flag where schedule rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for schedule, redis, httpRequest, microsoftTeams. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "New Ticket Alerts to Teams" — extract schedule IDs and secrets into environment variables without changing the 8-node structure.

Frequently asked questions

How do I import "New Ticket Alerts to Teams" into n8n?: Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "New Ticket Alerts to Teams" use?: It uses: schedule, redis, httpRequest, microsoftTeams. The flow diagram above shows how each service connects across the 8 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?: Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own schedule and redis credentials in n8n after import.
What trigger type does "New Ticket Alerts to Teams" use?: Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "New Ticket Alerts to Teams" free to use?: OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for schedule, redis, httpRequest, microsoftTeams.