telegram and send assign alert and webhook
Configured with Switch, Telegram, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Code
- Routing
- Messaging
- Trigger
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| telegram account | Code | Code | See node parameters |
| check tg account exists | Routing | If | See node parameters |
| check type | Routing | Switch | See node parameters |
| Send Update | Messaging | Telegram | See node parameters |
| Send Create | Messaging | Telegram | See node parameters |
| Send Assign Alert | Messaging | Telegram | See node parameters |
| check issue body, assignee and hook type | Routing | If | See node parameters |
| jira-webhook | Trigger | Webhook | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
httpHeaderAuthtelegramApi
Workflow notes
telegram and send assign alert and webhook
telegram and send assign alert and webhook
Purpose and structure
This folder contains the telegram and send assign alert and webhook workflow. Its executable nodes use code, if, switch, telegram, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
jira-webhook
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Webhook/0683_Webhook_Telegram_Create_Webhook.json MIT; preserve source notices.