← All N8N workflows
AI & researchAgentHTTP RequestIfLM Chat Open RouterMicrosoft One Drive

MiniBear Webhook

Configured with Agent, HTTP Request, LM Chat Open Router, Microsoft One Drive, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
TriggerLine WebhookWebhookWeb / APILine Loading AnimationHTTP RequestRoutingSwitchSwitchWeb / APIGet ImageHTTP RequestWeb / APILine Reply (image)HTTP RequestWeb / APILine Reply (Text)HTTP RequestWeb / APILine Reply (NotSupported 2)HTTP RequestWeb / APILine Reply (NotSupported 1)HTTP RequestAI & modelsOpenRouter Chat ModelLM Chat Open RouterAI & modelsImage RouterAgentMessagingMicrosoft TeamsMicrosoft TeamsIntegrationMicrosoft To DoMicrosoft To DoWeb / APILine Reply (Text)1HTTP RequestRoutingIf namecardIfAI & modelsOther ImagesAgentMessagingMicrosoft Teams1Microsoft TeamsAI & modelsOpenRouter Chat Model2LM Chat Open RouterFiles / mediaMicrosoft OneDriveMicrosoft One DriveFiles / mediaMicrosoft OneDrive1Microsoft One DriveWeb / APIGet Image2HTTP RequestIntegrationMicrosoft To Do1Microsoft To DoWeb / APIHTTP RequestHTTP RequestAI & modelsOpenRouter Chat Model3LM Chat Open RouterAI & modelsNamecardExtractAgentTransformStructured OutputParserOutput Parser StructuredWeb / APILine Reply NamecardHTTP RequestWeb / APIGet Image3HTTP Request

Node categories in this workflow

  • Trigger
  • Web / API
  • Routing
  • AI & models
  • Messaging
  • Integration
  • Files / media
  • Transform

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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Line WebhookTriggerWebhookSee node parameters
Line Loading AnimationWeb / APIHTTP RequestPOST
SwitchRoutingSwitchSee node parameters
Get ImageWeb / APIHTTP RequestSee node parameters
Line Reply (image)Web / APIHTTP RequestPOST
Line Reply (Text)Web / APIHTTP RequestPOST
Line Reply (Not Supported 2)Web / APIHTTP RequestPOST
Line Reply (Not Supported 1)Web / APIHTTP RequestPOST
OpenRouter Chat ModelAI & modelsLM Chat Open RouterSee node parameters
Image RouterAI & modelsAgentSee node parameters
Microsoft TeamsMessagingMicrosoft TeamschannelMessage
Microsoft To DoIntegrationMicrosoft To Docreate
Line Reply (Text)1Web / APIHTTP RequestPOST
If namecardRoutingIfSee node parameters
Other ImagesAI & modelsAgentSee node parameters
Microsoft Teams1MessagingMicrosoft TeamschannelMessage
OpenRouter Chat Model2AI & modelsLM Chat Open RouterSee node parameters
Microsoft OneDriveFiles / mediaMicrosoft One DriveSee node parameters
Microsoft OneDrive1Files / mediaMicrosoft One Driverename
Get Image2Web / APIHTTP RequestSee node parameters
Microsoft To Do1IntegrationMicrosoft To Docreate
HTTP RequestWeb / APIHTTP RequestPOST
OpenRouter Chat Model3AI & modelsLM Chat Open RouterSee node parameters
NamecardExtractAI & modelsAgentSee node parameters
Structured Output ParserTransformOutput Parser StructuredSee node parameters
Line Reply NamecardWeb / APIHTTP RequestPOST
Get Image3Web / APIHTTP RequestSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

  • httpHeaderAuth
  • microsoftOneDriveOAuth2Api
  • microsoftTeamsOAuth2Api
  • microsoftToDoOAuth2Api
  • openRouterApi

Workflow notes

Sticky Note1

Webhook from Line

You need to set-up this webhook at Line Manager or Line Developer Console

You'll need to copy Webhook URL from this node to put in Line Console

Also, don't forget to remove 'test' part when going for production

https://developers.line.biz/en/docs/messaging-api/receiving-messages/

Sticky Note2

Line Loading Animation

This node is to only give ... loading animation back in Line.

It seems stupid but it actually tells user that the workflow is running and you are not left waiting without hope

To authorize, you can fill in the Line Token in the node here, or you can you header authorization (shown at the 'reply message' node)

https://developers.line.biz/en/docs/messaging-api/use-loading-indicator/

Sticky Note5

Router for Tasks (Text started with 'T'), other texts, images and others

Sticky Note9

Line Reply To reply that message is not supported

Sticky Note

Line Reply To send feedback that the task has been added

Sticky Note3

Line Reply To send feedback message has been saved

Sticky Note4

Tasks To add in MS 'To Do' List

Sticky Note6

MS Teams Save this message in MS Teams

Sticky Note7

Tasks To add in MS 'To Do' List to follow-up with this namecard

Sticky Note10

HTTP Request This is to trigger another workflow to add new rows in MS Excel 365

Sticky Note13

Identify Image First we'll get the image from Line and we will use Tool Agent to query OpenRouter to identify whether this is namecard or not?

Sticky Note14

Namecard Information Extraction First we'll get the image from Line and we will use Tool Agent to query OpenRouter to extract the namecard information in the structured format

Sticky Note15

Router Namecard or not

Sticky Note16

Text Extraction First we'll get the image from Line and we will use Tool Agent to query OpenRouter to identify image content such as what is written

Sticky Note17

Upload to OneDrive This is to upload the file to OneDrive. Due to some bug I faced, we need to rename the file again.

MiniBear Webhook

MiniBear Webhook

Purpose and structure

This folder contains the MiniBear Webhook workflow. Its executable nodes use agent, httpRequest, if, lmChatOpenRouter, microsoftOneDrive, microsoftTeams, microsoftToDo, outputParserStructured, switch, 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

Line 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/Microsofttodo/1494_Microsofttodo_Webhook_Automation_Webhook.json MIT; preserve source notices.

More in AI & research