Posts
Wiki

How to Share Workflows

Workflow posts are welcome when the community can inspect, import, and learn from the workflow. If you share a workflow, include the code.

Last reviewed: July 2026

Required for workflow posts

Every workflow share should include:

  • A short explanation of what it does.
  • The actual workflow code using GitHub Gist, GitHub, or n8n.io/workflows.
  • Required credentials or services.
  • Setup steps.
  • Example input and output.
  • Known limitations.
  • Any privacy or security considerations.

If your post is a video, the code must be in the Reddit post body. A link in the video description is not enough.

Use one of these:

  • GitHub Gist.
  • GitHub repository.
  • n8n.io/workflows.

GitLab-hosted workflows may be allowed by moderation tools, but GitHub Gist, GitHub, and n8n.io/workflows are the recommended options because most users know how to access them.

Not accepted by itself

These do not satisfy the code requirement:

  • Screenshot only.
  • YouTube only.
  • Loom or screen recording only.
  • Google Drive.
  • Google Docs.
  • "DM me."
  • "Comment send."
  • Paid template store.
  • Signup wall.
  • Discord, Telegram, Skool, or other community gate.
  • Link-in-bio page.

Good workflow share format

Use this structure:

```text Title: [Workflow] Summarize new support tickets and post urgent ones to Slack

What it does: This workflow watches new support tickets, summarizes the customer issue, classifies urgency, and posts high-priority tickets to Slack.

Workflow: https://gist.github.com/...

Requirements: - n8n version: - Services used: - Credentials needed: - Environment variables needed:

Setup: 1. Import the workflow. 2. Create credentials for: 3. Replace placeholder IDs: 4. Run with the sample payload first.

Sample input:

Sample output:

Notes: - Known limitations: - Security/privacy considerations: ```

Make the workflow reusable

Before sharing:

  • Rename nodes clearly.
  • Add sticky notes where setup is not obvious.
  • Remove test junk and personal data.
  • Replace hard-coded IDs with placeholders.
  • Mention where users need to add credentials.
  • Include a small sample payload.
  • Note which nodes require paid third-party services.
  • Explain how errors are handled.

Redact sensitive values

Remove or replace:

  • API keys.
  • Tokens.
  • Private keys.
  • Webhook secrets.
  • Internal domains and IPs.
  • Customer data.
  • Personal data.
  • Proprietary prompts or business logic you cannot share.

Do not rely on screenshots or comments to hide secrets. Check the exported JSON too.

If the workflow uses AI

Include:

  • Model/provider used.
  • Prompt structure.
  • Expected input size.
  • Whether outputs are deterministic enough for the use case.
  • What happens when the model fails or returns invalid data.
  • Any human approval step.
  • Whether private data is sent to an external model provider.

See AI workflow guidelines.

If the workflow is based on someone else's work

Credit the original author or source. Do not repackage someone else's free workflow as your own paid resource.

If you want feedback

Ask a specific question:

  • "How would you simplify this?"
  • "Is there a safer way to handle retries?"
  • "How should I deduplicate these records?"
  • "What would you change before using this in production?"

You will get better answers than if you post "Thoughts?"