Automation library · Research and reporting

Assign Jira Service Management reporter from forwarded emails

Started by an event in a connected app, and works across Jira. 9 steps, 2 branches: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 4Service 4

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

  1. 1Jira Trigger1Jira triggerStarts it
  2. 2Filter Forwarding EmailsIfLogic
  3. 3Set Description VariableSetLogic
  4. 4Parse Details From DescriptionCodeLogic
  5. 5Search for Existing CustomerHttp RequestService
  6. 6If Customer ExistsIfLogic
  7. 7Update Reporter (Existing Customer)JiraService
  8. 8Create Customer1Http RequestService
  9. 9Update Reporter (New Customer)JiraService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Jira account. 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. 9 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 9 steps before you point it at anything that matters.