n8n workflow · one-time purchase

One form.
Jira, Slack, Drive — done.

Replaces 15–20 minutes of manual project setup with a single form submission. Fill in the client name, hit submit — Epic in Jira, channel in Slack, folders in Drive.

Get the workflow — $39 one-time · self-hosted · yours to modify
~15 seconds from form submit to fully configured workspace

Every new project starts the same way.

You open Jira and create an Epic. Then you remember you forgot to add the kickoff tasks, so you go back and add those. Then you open Slack and create a private channel — but you have to look up the naming convention you agreed on six months ago. Then you invite the team, but you always miss someone. Then you open Drive and create the folder structure — except you can't remember if it was "Client / Project" or "Project / Client" and the structure is different from the last three projects anyway.

Twenty, thirty, forty minutes later, the project exists. Nobody started working on it. You just did glorified admin.

Submit once. Everything else is automatic.

A self-hosted n8n workflow triggered by a form. Google Drive, Jira, and Slack all run in parallel — done in ~15 seconds.

project-kickoff.workflow
form submission
    │
    ├── Google Drive ─────────────────────────────────┐
    │     ├── find or create client folder          │
    │     ├── create project subfolder              │
    │     ├── share with team (writer access)       │  runs
    │     └── create 5 subfolders                   │  in
    │                                               │  parallel
    └── Jira + Slack ────────────────────────────────┤
          ├── Epic → kickoff tasks + due dates      │
          └── private channel → invite all          │
                                                    ▼
                                          ~15 seconds
Jira

Creates an Epic named after the client and project, then adds a set of kickoff tasks — schedule the kickoff call, send the welcome email, set up access, define DoR/DoD, start the backlog. Due dates calculated from your project start date.

Slack

Creates a private channel named after the project and invites all team members from the form.

Drive

Finds or creates the client folder, adds a project subfolder, shares it with the team, and creates five subfolders with a consistent structure.

Everything you need, nothing you don't.

Works with what you already use

Jira Cloud, Slack, Google Drive — runs through your existing n8n instance. Nothing new to sign up for.

Three project types out of the box

Standard kickoff (5 tasks), Discovery (4 tasks), Consulting (4 tasks). Each has its own task list with priorities and due dates relative to your project start date.

Fully customizable task templates

Add a new project type by editing two places in the workflow. Each task gets a summary, priority, due date offset, and optional assignee.

Consistent folder structure, every time

Five subfolders — Documentation, Design, Development, Client Communication, Resources — created automatically. Change the list once; every future project inherits it.

Resilient by default

Client folder already exists — reuses it. Channel name has non-ASCII characters — transliterated. Start date left blank — defaults to today. None of these require you to do anything.

Self-hosted — your data stays yours

Runs on your n8n instance. The code is yours — read it, modify it, keep it.

Three files. That's it.

No SaaS dashboard. No account to create. Import the workflow, follow the checklist, activate.

project-kickoff-automation/
├── workflow-jira.json     The n8n workflow — import and go
├── README.md              Full documentation and customization guide
└── SETUP.md               Step-by-step setup checklist (~20 min)

Built for teams that run projects.

Good fit

  • Agencies and software houses that start 2–20 projects per month
  • PMs and tech leads who want consistency without the manual work
  • Teams already using Jira Cloud + Slack + Google Drive
  • Anyone running n8n (self-hosted or cloud)

Not a fit

  • You need to create a new Jira project per client — this creates Epics and tasks in an existing project (creating Jira projects requires admin permissions most users don't have)
  • You don't use all three tools — the workflow does Jira, Slack, and Drive together or not at all

Questions.

You need to be comfortable with n8n basics — importing a workflow, creating credentials, editing node parameters. If you've used n8n before, setup takes about 20 minutes. Full step-by-step instructions are included.
No. The workflow uses Jira Cloud REST API v3. Jira Server and Data Center use a different API and are not supported. Atlassian ended Server license sales in 2024 — if you're still on Server, migration to Cloud is the path forward.
Yes — paste your Shared Drive ID in the configuration node instead of a folder ID. The workflow works with both.
Yes, as many as you want. Instructions in README.md — it's two edits in two nodes.
Not out of the box — the workflow is designed as an all-in-one kickoff. You can disable individual nodes in n8n (right-click → disable) but you'll need to manually rewire the connections.
No. This is a one-time purchase. You get the workflow file and documentation. No ongoing fees, no accounts, no usage limits.
The documentation covers all common scenarios and error messages. If you run into something not covered, contact us directly.

Project Kickoff Automation

One purchase. Runs on your n8n. Yours to modify.

Get the workflow — $39

n8n 1.47+ · Jira Cloud · Slack · Google Drive