The flow
Starts it 1Model 2Logic 7Service 12
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Anthropic Chat ModelLm Chat AnthropicModel
- 3Google search in SerpApiSerp Api ToolService
- 4Jira SoftwareJiraService
- 5AI AgentAgentModel
- 6HTTP Request - Get Form IDHttp RequestService
- 7Set SAP BP payloadCodeLogic
- 8Code AI Agent outputCodeLogic
- 9HTTP Request - Get Form DetailsHttp RequestService
- 10SAP BP createHttp RequestService
- 11Jira Software Update Status & AIJiraService
- 12Split OutSplit OutLogic
- 13Set BP NumberSetLogic
- 14Send Form to VendorEmail SendService
- 15HTTP Request, download each file from JiraHttp RequestService
- 16Split AttachmentsCodeLogic
- 17HTTP Request - JiraHttp RequestService
- 18Upload a fileAws S3Service
- 19Code - Jira issue payload and downloads + base64-encodesCodeLogic
- 20SAP BP create DocumentsHttp RequestService
- 21WaitWaitLogic
- 22Delete the files from S3Aws S3Service
How it's built
- Starts on
- A clock
- Steps
- 22, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Email, Jira, S3
- Model
- Claude
Questions
What does it need to run?
An n8n account, plus your own Email, Jira and S3 accounts, and a key for Claude. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
Yes. It calls Claude. Model calls are billed by the provider, not by n8n.
How long does it take to set up?
Take your time. At 22 steps it is large: read it before trusting it with anything live.
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 itNothing 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 22 steps before you point it at anything that matters.