n8n orchestrates APIs. API Butler creates them.
Use API Butler to publish CSV-backed REST endpoints, then call them from n8n HTTP Request nodes.
Quick answer
If your automations need structured data from CSV exports, API Butler provides the API and n8n orchestrates the workflow.
Why this works
API Butler creates stable endpoints from CSV
n8n can call the same endpoint across recurring runs.
n8n HTTP Request node handles API calls
GET requests return JSON that downstream nodes can transform.
Workflow orchestration stays flexible
Use n8n for routing, enrichment, and multi-step automation.
Example workflow
Publish
Upload CSV and create API in API Butler
GET /v1/apis/leads
Trigger
Start n8n workflow on schedule or event
Cron / Webhook
Request
HTTP Request node calls API Butler endpoint
Method: GET
Process
Use JSON output in n8n logic
filter + branch + actions
Step-by-step guide
01
Create dataset API in API Butler
Publish your CSV as a REST endpoint.
02
Add HTTP Request node in n8n
Configure Method GET and endpoint URL.
03
Run and inspect JSON response
Validate fields for downstream workflow steps.
04
Map response into automation actions
Use returned data to trigger updates, notifications, or sync jobs.
API request example
n8n HTTP Request target
curl "https://api.getapibutler.com/v1/apis/leads/items?status=new&limit=100"
Response payload sample
{
"data": [
{ "id": "L-1002", "status": "new", "owner": "growth" }
],
"total": 124
}
Use this with an AI coding agent
When your tool needs custom glue code, paste your endpoint into this prompt and run it in Cursor, Claude Code, Codex, or another assistant.
You are acting as a senior engineer wiring a read-only API Butler GET endpoint into my project.
Phase 1 — Do not write implementation code yet.
Ask me exactly 2–3 focused questions you must have answered to integrate safely. Strong options include:
- The full GET URL for my API Butler endpoint, and whether X-API-Key is required or optional for this API
- Which route, screen, or component should consume this data (or the file path if you already infer it)
- How you should surface failures (inline message, toast, dedicated error state) and whether pagination or filters matter for this UI
Stop and wait for my replies before coding.
Phase 2 — After I answer:
- Fetch with GET only; parse JSON with a "data" array and "meta" containing limit, offset, count, total (see API Butler API usage docs)
- Implement loading, empty, and error states; do not swallow HTTP or JSON errors silently—surface enough context to debug (status, safe excerpt of body when reasonable)
- Reuse existing HTTP helpers, composables, hooks, and UI primitives; match established patterns for lists or tables
- Keep secrets out of committed source (env or existing config patterns only)
Negative prompts — do not:
- Refactor unrelated modules, rename public APIs, upgrade frameworks, or introduce new global state libraries unless the repo already uses them
- Assume POST, PATCH, or mutation semantics—this integration is read-only
- Hardcode mock rows, fake pagination totals, or strip query parameters without confirming with me
- Commit or log raw API keys
Add or extend automated tests only if the repository already has a test runner and conventions for this layer.
More prompts: AI agent prompts
Use cases
Lead ops
Route lead data to downstream systems
Query fresh rows and branch workflows by status.
Reporting
Scheduled data sync
Pull API data into analytics and notifications.
RevOps
Cross-tool enrichment flows
Combine CSV-backed API data with other API sources.
FAQ
Integration questions.
Can n8n call API Butler endpoints?
Yes. Use an HTTP Request node with Method GET and your API Butler endpoint URL.
Why combine n8n with API Butler?
API Butler publishes the CSV-backed API; n8n orchestrates how and when that API data is used.
What problem does this solve?
It replaces manual CSV processing in automation pipelines with endpoint-driven workflow steps.
Do I need custom code for this?
Not necessarily. A standard n8n HTTP Request node and field mapping is enough for many workflows.
Next step
Create your API in API Butler, orchestrate it in n8n.
Start with one CSV endpoint and wire it into an n8n HTTP Request node.