OpenRuna
Sign in
← Workflows

MiniBear Webhook

45 nodes · webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams

Engine
n8n
Nodes
45
Trigger
scheduled/triggered
Source file
1494_Microsofttodo_Webhook_Automation_Webhook.json

Workflow flow

IntegrationsWebhookHTTPSwitchLmChatOpenRouterAgentMicrosoftTeamsMicrosoftToDoMicrosoftOneDriveOutputParserStructured@n8n/n8n-nodes-langchain.lmChatOpenRouter@n8n/n8n-nodes-langchain.agentIF+1 more
100%
TRIGGER

Line Webhook

Webhook

OpenRouter Chat Model

@n8n/n8n-nodes-langchain.lmChatOpenRouter

OpenRouter Chat Model2

@n8n/n8n-nodes-langchain.lmChatOpenRouter

OpenRouter Chat Model3

@n8n/n8n-nodes-langchain.lmChatOpenRouter

Structured Output Parser

@n8n/n8n-nodes-langchain.outputParserStructured

Line Loading Animation

HTTP

Switch

Switch

Get Image

HTTP

Line Reply (Not Supported 2)

HTTP

Line Reply (Not Supported 1)

HTTP

Microsoft Teams

MicrosoftTeams

Microsoft To Do

MicrosoftToDo

Line Reply (Text)

HTTP

Image Router

@n8n/n8n-nodes-langchain.agent

Line Reply (Text)1

HTTP

If namecard

IF

Microsoft OneDrive

MicrosoftOneDrive

Get Image3

HTTP

Microsoft OneDrive1

MicrosoftOneDrive

NamecardExtract

@n8n/n8n-nodes-langchain.agent

Get Image2

HTTP

Microsoft To Do1

MicrosoftToDo

Other Images

@n8n/n8n-nodes-langchain.agent

Line Reply Namecard

HTTP

Microsoft Teams1

MicrosoftTeams

HTTP Request

HTTP

Line Reply (image)

HTTP

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

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. 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: MiniBear Webhook. 45 nodes across webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams, microsoftToDo, microsoftOneDrive, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"MiniBear Webhook" automates a webhook-to-httpRequest flow in n8n across 45 nodes. 45 nodes · webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. 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 webhook to httpRequest before building your own variant.
  • Use it as a starting template when wiring webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams, microsoftToDo, microsoftOneDrive — adjust node parameters to your accounts and record IDs.
  • Import "MiniBear Webhook" into n8n, reconnect credentials for webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams, microsoftToDo, microsoftOneDrive, and run the same automation in your own workspace.
  • Benchmark it against your current webhook integration to spot missing steps or redundant nodes.

Example output

Imported into n8n, "MiniBear Webhook" exposes 45 configured nodes. Trigger type: scheduled/triggered. Integrations: webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams, microsoftToDo, microsoftOneDrive. Reconnect the webhook credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "MiniBear Webhook" into Claude and ask it to explain each of the 45 nodes. Claude is good at suggesting credential mappings for webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams, microsoftToDo, microsoftOneDrive, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "MiniBear Webhook" to your accounts — which webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams, microsoftToDo, microsoftOneDrive credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 45 nodes.

Frequently asked questions

How do I import "MiniBear Webhook" 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 "MiniBear Webhook" use?
It uses: webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams, microsoftToDo, microsoftOneDrive. The flow diagram above shows how each service connects across the 45 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 webhook and httpRequest credentials in n8n after import.
What trigger type does "MiniBear Webhook" 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 "MiniBear Webhook" 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 webhook, httpRequest, switch, lmChatOpenRouter, agent, microsoftTeams, microsoftToDo, microsoftOneDrive.

Related resources