Five steps from GitHub login to a published template in the builder’s library — and a contributor badge on every card that ships it.
The whole flow is one PR against the templates repo. Average turnaround: 48 hours.
Hit /auth/github to complete the OAuth round trip. FlowForge upserts your user row and sets is_contributor = TRUE automatically — no separate contributor application needed.
Describe your automation in plain English inside the builder. Tweak nodes and connections until the graph matches what you want contributors to see.
Drop the export in templates/<slug>.json. The shape maps directly onto the workflow_templates table — slug (unique, ≤ 128 chars), name (≤ 255), category (≤ 64), plus graph and n8n_json as JSONB:
{
"slug": "slack-new-lead",
"name": "Slack Notification on New Lead",
"description": "AI-qualifies inbound leads and posts to Slack.",
"category": "Notifications",
"graph": { /* FlowForge node graph */ },
"n8n_json": { /* n8n export */ }
}
Open the builder with your template slug, hit the share button, and save the PNG as templates/<slug>.png. Reviewers read the visual; users read the JSON — ship both.
Fork polsia/flowforge, commit your .json + .png, and open a PR. Once merged, your template and contributor badge (previewed below) appear inside /builder.
Skip to the import section below — any of the four trigger patterns works as a starting point.
This is exactly the markup that ships next to every template you publish.
These slugs already live in the library — open them in the builder to hydrate, then customize before re-exporting as your own template.
HTTP-webhook trigger, AI lead qualification, Slack channel delivery.
Try in Builder →Gmail trigger, AI summarization, priority labels, drafted replies for review.
Try in Builder →New-row trigger, firmographic enrichment, HubSpot contact sync.
Try in Builder →Cron trigger, AI-compiled narrative, polished morning report email.
Try in Builder →Have a JSON export from n8n? Paste it in /builder — FlowForge will parse it.