Automation library · Documents and files

Automated Slack-to-Jira issue creation

Started by an event in a connected app, and works across Jira and Slack. 11 steps, 2 branches, 1 loop or waits: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
2Branches: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Logic 5Service 5

The steps in the order they run, from what starts it.

  1. 1Slack TriggerSlack triggerStarts it
  2. 2checking messageIfLogic
  3. 3Parse Message into Jira FormatCodeLogic
  4. 4Create Jira IssueJiraService
  5. 5Check AttachmentsIfLogic
  6. 6Prepare Files for ProcessingCodeLogic
  7. 7Reply to Channel On SlackSlackService
  8. 8Split Files into BatchesSplit In BatchesLogic
  9. 9Get File InfoHttp RequestService
  10. 10Download AttachmentHttp RequestService
  11. 11Upload Attachment to JiraJiraService

How it's built

Starts on
An event in a connected app
Steps
11, with 2 branches, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Jira, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Jira and Slack accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an event in a connected app.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 11 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 11 steps before you point it at anything that matters.