Build flows from a prompt
“Load Stripe charges into Snowflake daily” or “sync Salesforce contacts to HubSpot every 15 minutes.” Simba picks templates, configures connections, sets schedules.
Simba · the Etlworks AI agent
Build data flows by describing what you need.
Simba is the agent built into Etlworks. Tell it what you’re trying to do — “load Stripe charges into Snowflake daily,” “sync Salesforce contacts to HubSpot” — and it builds the flow. You stay in control; Simba does the typing.
- Build pipelines from a plain-English description
- Debug failing flows — reads errors, schemas, and configs
- Optimize slow pipelines — parallelization, batching, pushdown
- Migrate logic from SnapLogic, Talend, Airflow, or custom Python
- Answer ops questions — flow status, runs, lag, recent errors
- 200+ flow types Simba can build
- 3,979 templates Simba reaches for
- 270+ connectors
- BYOK use your own OpenAI key
The hard part
You shouldn’t have to know the platform to use it.
Most data integration tools require knowing the platform’s vocabulary before you can build anything. Which flow type? What template? Which connector? How does mapping work? That’s a learning curve before you ship anything.
What Simba does
Six things Simba can do today. Most of them are about turning English into working data pipelines.
Translate flow logic from your old tool
Paste in transformation logic from SnapLogic, Talend, Airflow, or custom Python — Simba converts it to a working Composer flow. Useful when migrating.
Debug and fix broken flows
Show Simba a failing flow. It reads the error, checks schemas and configurations, suggests fixes, and (with approval) applies them.
Optimize slow flows
Ask Simba to make a flow faster. It analyzes execution traces, suggests parallelization, batching, or pushdown ELT — explains the tradeoffs before changing anything.
Document what flows do
Generates plain-English descriptions of flows: what they read, what they write, on what schedule, with what transformations. Useful for handoffs, audits, and onboarding.
Answer questions about your data
“How many flows write to Snowflake?” “Which flows haven’t run in 30 days?” Simba reads the platform state and answers — no SQL required.
Three ways to use Simba
Same agent, three surfaces. Pick whichever fits the moment.
In the product
Inside Composer
Chat with Simba while building flows on the canvas. Drop two connections, ask Simba to wire them. Or describe the whole pipeline; Simba builds it. The default way most teams use it.
See ComposerConversational
Refine in plain English
“Add a daily summary email.” “Filter out test rows before loading.” “Run this only on weekdays.” Simba updates the flow and shows you what changed before applying.
Watch a demoProgrammatic
Agent API
Drive Simba from your own AI stack. REST API, Python and Bash clients. Use as a subagent in LangChain, CrewAI, or AutoGen. Streaming, multi-turn sessions, direct tool access.
Read the API docsWhat Simba is and isn’t
Honest about both. Simba is good at most things and a few things it deliberately leaves to you.
Simba is good at
- Building flows for known source-destination patterns (Salesforce → Snowflake, etc.)
- Translating SQL, Python, JS, and most pipeline definitions into Composer flows
- Reading schemas and inferring field mappings automatically
- Diagnosing flow errors and suggesting fixes
- Writing inline transformations in SQL, JavaScript, or Python
Simba isn’t trying to
- Translate proprietary closed-source formats — Informatica’s PowerCenter mappings, some legacy ETL XMLs, vendor-specific binary formats. Simba can take a description and rebuild the logic, but won’t parse formats we don’t have access to.
- Replace your data engineer for complex orchestration — multi-system distributed transactions, regulatory-grade audit chains, novel architectures with no precedent. Simba helps; it doesn’t lead.
How Simba handles your data
Simba runs on the same Etlworks infrastructure your flows do. Same data isolation, same SOC 2 controls, same retention policies.
No training on your data
When you bring your own OpenAI key, your data flows through your provider relationship — covered by the privacy terms you already negotiated. Etlworks doesn’t sit in the middle. When using the Etlworks-managed wallet, our provider contracts include opt-out from training, and conversations aren’t shared across customers.
Approval before changes
Simba shows you what it’s about to do before applying. Every flow change, every config edit, every credential update — you approve. Optional auto-apply for low-risk operations.
Full audit trail
Every Simba action is logged: who asked, what it built, what changed, when. Available in the audit log alongside human-driven changes.
See security detailsFAQ
Do I have to use Simba?
No. Composer supports drag-and-drop, code, and CLI building without Simba ever entering the picture. Simba is opt-in. Most teams use it for the parts they don’t already know how to build, and skip it for the parts they do.
What model powers Simba?
Etlworks runs Simba on the latest frontier OpenAI models — we pick and update them as new ones ship. Whether you bring your own key (BYOK) or use the Etlworks-managed wallet, you don’t choose the model; you always get the current best.
The intelligence sits in the toolchain wrapped around the model: knowledge base search, template lookup, schema introspection, CLI execution, and flow validation. The model handles language; the toolchain handles the platform-specific work.
Can I use Simba in my own AI app?
Yes. The Agent API exposes Simba as a REST endpoint with Python, Bash, and PowerShell clients. Use it as a subagent in LangChain, CrewAI, AutoGen, or any orchestration framework. Full developer docs
Does Simba work in on-premise deployments?
Yes. Simba ships with every Etlworks deployment — cloud, hybrid, and on-premise. For air-gapped on-prem environments, the language model can be configured to use a self-hosted inference endpoint instead of a hosted provider.
How is this different from generic AI assistants like ChatGPT or Claude?
Generic assistants don’t have access to your Etlworks platform. Simba does. It can read your existing flows, search 3,979 templates, inspect schemas in your connected systems, run CLI commands, and apply changes — all inside the Etlworks platform with your permissions and audit trail intact. A generic assistant can write you SQL; Simba can ship you a working pipeline.
What does Simba cost?
Most teams bring their own OpenAI API key — Simba uses it directly, and you pay your AI provider, not Etlworks. Configure once per organization, or per user if you want individual billing. There’s no Etlworks markup or middleware fee on the AI usage.
If you’d rather not manage your own provider relationship, Etlworks offers an AI wallet with auto-recharge — fund it once, set a monthly cap and a low-balance recharge trigger (the same model OpenAI uses directly). Wallet usage is billed at-cost.
Every plan also includes a small monthly Simba allowance for trying things out without configuring either option. See pricing
Try Simba.
14-day free trial includes Simba credits. Build your first flow by describing what you need. No credit card.