Manage Cloudflare DNS records with AI-powered chat assistant
Needs changesWhat this workflow does
This AI workflow has 13 nodes and runs when a chat message arrives (plus 1 other trigger). Along the way it connects OpenAI Chat Model and Postgres Chat Memory. It also calls api.cloudflare.com over HTTP.
How it runs
Trigger: When a chat message arrives (plus 1 other trigger).
- Chat Agent (AI Agent): runs an AI agent, with model: OpenAI Chat Model; 1 tool (CloudFlare tool); memory: Postgres Chat Memory
- Json (Code): runs custom JavaScript code
- Switch: routes items into 3 branches
- Get TLDs (HTTP Request): calls api.cloudflare.com
- Getter (HTTP Request): calls an HTTP API
- Setter (HTTP Request): calls an HTTP API (PATCH)
- Host details (Split Out): splits a list into separate items
Services it uses
HTTP calls to: api.cloudflare.com
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- AI Agent v1 (old agent modes) in Chat Agent (v1.9): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| AI Agent v1 (old agent modes) Chat Agent (v1.9) | Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent. |
Nodes used (11)
- Chat Trigger
@n8n/n8n-nodes-langchain.chatTrigger - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - AI Agent
@n8n/n8n-nodes-langchain.agent - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - Switch
n8n-nodes-base.switch - Postgres Chat Memory
@n8n/n8n-nodes-langchain.memoryPostgresChat - Call n8n Workflow Tool
@n8n/n8n-nodes-langchain.toolWorkflow - No Operation, do nothing
n8n-nodes-base.noOp - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Split Out
n8n-nodes-base.splitOut
From the author
This n8n flow demos basic dev-ops operation task, dns records management. AI agent with light and basic prompt functions like getter and setter for DNS records. In this special case, we are managing remote dns server, via API calls - that are handled on…