# Code for thinking, n8n for plumbing

Keep reasoning in code (a LangGraph agent behind an API). Keep triggers and app integrations in n8n.

AI developers · Part 08: n8n · Card 13 of 13 · Last updated 2026-10-13

## Analogy

Business logic in services, glue in config. Nobody wants their domain model in a YAML file.

## In an agent

Bonus: non-developers can change the n8n workflows without touching the agent.

## Practice

### Flashcards

- **Interview: where does n8n fit next to an agent?** Triggers and integrations. Reasoning stays in code; plumbing stays in n8n.

### Interview questions

**Where does n8n fit?**

- Triggers and integrations.
- n8n starts the agent on webhooks or schedules.
- The agent calls n8n webhooks as tools for Slack and Jira actions.
- Reasoning stays in code; plumbing stays in n8n.

## Questions people ask

### What should live in code and what in n8n?

Keep the thinking in code: the agent's reasoning, tools, prompts and tests, behind an API. Keep the plumbing in n8n: triggers, schedules and connections to apps like Slack, Jira and email. It is like business logic in services and glue in configuration.

### Why split agent reasoning from integrations?

Each part then uses the right tool. Code gives you tests, version control and type safety for the hard reasoning. n8n gives you ready-made integrations and a visual editor that non-developers can change. You can update a Slack channel or schedule without redeploying the agent.

## Related concepts

- [n8n as the trigger](https://studyvisually.com/learn/tech/ai-developers/n8n/n8n-calls-agent)
- [n8n as the hands](https://studyvisually.com/learn/tech/ai-developers/n8n/agent-calls-n8n)
- [Trigger node](https://studyvisually.com/learn/tech/ai-developers/n8n/trigger-node)
- [n8n](https://studyvisually.com/learn/tech/ai-developers/n8n/n8n)

Web page: https://studyvisually.com/learn/tech/ai-developers/n8n/thinking-vs-plumbing
Study this card in the app: https://studyvisually.com/app/learn?category=ai-developers&card=thinking-vs-plumbing