Deep dive · module 88 of 100
Orchestration with Make, n8n or code
Connect AI steps with other tools in an automated flow.
After this lesson
You understand what orchestration is and when it is useful.
In view · Working together towards one result
Connect steps, monitor the action
An agreed event starts the flow with permitted data.
Process the information in a small, controllable chain.
Have a human approve before the flow performs an external action.
Part 1 of 3 · Trigger and input
Your preference for less movement is on. Choose each part yourself.
What is orchestration?
Linking different steps and tools so that a process runs automatically.
Tools
Make, n8n or custom code can combine AI calls with email, spreadsheets, or databases.
Start small
First, automate a simple, well-understood flow with a human checkpoint.
New practice example
From explanation to a usable result.
An automation platform connects steps; it does not take responsibility for errors and duplicate actions.
Fictional practice situationA fictitious workflow receives a form, creates a draft response, and waits for approval. After sending, the connection is lost before the confirmation returns.
View a possible solution
This is how it can be done
Use the task number to check if the message has already been sent. Mark the status as uncertain until that check is complete. Do not blindly resend. In the event of missing approval, keep the workflow at the draft stage.
Why this works
An extra attempt can cause a duplicate customer email. A neat flowchart is not proof that the error handling is correct.
Make it slightly more difficult
Add a duplicate form submission and record how the same request is recognised before two drafts or messages are created.
Extra practice, at your own pace. You do not need to submit anything. This does not count towards an automatic assessment.
Your workplace · learning by doing
Make something. See what changes.
Checking the AI connection… You can already view the written example.
Present your assignment to Ende.
Read the answer, change one thing, and compare.
Previously held
New version
You remain in control
What do you want to improve in your next attempt?
On this device only. AI answers remain only in this page memory. This is self-review, not a grade.
Why this approach works
An extra attempt can cause a duplicate customer email. A neat flowchart is not proof that the error handling is correct.
A step further
Add a duplicate form submission and record how the same request is recognised before two drafts or messages are created.
Try & discover · no obligation
Control an agent with a control port
Try to send before the check. Then also test a missing source or a malfunction.
- Retrieve source
- Check draft
- Execute action
What is happening?
- No source has been retrieved yet. Feel free to try the submit button first.
All tools, queues and submissions have been simulated. No message is sent and no external service is called.
This trial works locally with fictitious data and does not count towards your lesson completion. It starts anew with a new lesson or reload.
A prompt to get you started
Describe a simple automated flow in which an incoming email is summarised by AI and the summary is placed in a spreadsheet.
Apply it
A workflow from support email to ticket is automatically re-executed after an error.
Which approach best fits this situation?
- Create a new ticket for every repetition.
- Use a unique message ID and check if the ticket already exists.
- Silently skip every error.
With JavaScript, you can check your approach and receive immediate feedback.
Test your insight
What is important when automating a AI flow?
- A human checkpoint for steps with consequences.
- Letting everything run completely automatically.
- Only choosing the fastest tool.
Extra practice
Note a process you would like to orchestrate and where the human checkpoint is located.
Incoming support email → AI summary → into ticket system → human approves answer.
