OpenRuna
Sign in
← Workflows

1084_Sse_Automation_Triggered

1 nodes · sse

Engine
n8n
Nodes
1
Trigger
scheduled/triggered
Source file
1084_Sse_Automation_Triggered.json

Workflow flow

IntegrationsSSE
100%
TRIGGER

SSE Trigger

SSE

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

Browse by integration

sse
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

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: 1084_Sse_Automation_Triggered. 1 nodes across sse, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"1084_Sse_Automation_Triggered" automates a sse-to-sse flow in n8n across 1 nodes. 1 nodes · sse It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

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

Example output

Imported into n8n, "1084_Sse_Automation_Triggered" exposes 1 configured nodes. Trigger type: scheduled/triggered. Integrations: sse. Set your credentials on the sse 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

Paste the exported JSON for "1084_Sse_Automation_Triggered" into Claude and ask it to explain each of the 1 nodes. Claude is good at suggesting credential mappings for sse, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "1084_Sse_Automation_Triggered" to your accounts — which sse 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 1 nodes.

Frequently asked questions

How do I import "1084_Sse_Automation_Triggered" 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 "1084_Sse_Automation_Triggered" use?
It uses: sse. The flow diagram above shows how each service connects across the 1 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 sse and sse credentials in n8n after import.
What trigger type does "1084_Sse_Automation_Triggered" 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 "1084_Sse_Automation_Triggered" 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 sse.

Related resources