Automation library · Customer support

Create Jira tickets from Streamlit forms with REST API

Started by another system calling it. It calls services over plain HTTP rather than through connectors. 10 steps, 1 branch: a working afternoon to understand properly.

Medium

Download free
10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 8Service 1

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

  1. 1Webhook streamlitWebhookStarts it
  2. 2anti doubleCodeLogic
  3. 3raw data from streamlitSetLogic
  4. 4Process streamlit dataCodeLogic
  5. 5if for doublesIfLogic
  6. 6Processed dataSetLogic
  7. 7blocked requestCodeLogic
  8. 8Jira HTTP requestHttp RequestService
  9. 9jira responseSetLogic
  10. 10ResultCodeLogic

How it's built

Starts on
Another system calling it
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

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. 10 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 10 steps before you point it at anything that matters.