01
Turn a data request into a pipeline
Tell your assistant what you want to move and where it should go. It can inspect your connections, explore source objects, and prepare the pipeline for review.
Agentic data pipelines
Tell Supaflow what data you need and where it should go. Your assistant can explore your connections, prepare a pipeline, run a sync, investigate failures, and manage schedules—all in ChatGPT or Claude.
Works with your Supaflow account, existing connections, and workspace permissions.
You
Plan a Salesforce-to-Snowflake pipeline for Accounts and Opportunities. Show me the plan before creating it.
I’ll check your workspace, connections, and Salesforce catalog first.
Source: Salesforce Destination: Snowflake Selected objects: Account, Opportunity
Here is the pipeline plan. Would you like me to create it with these objects?
Keep working with your Supaflow sources, destinations, and pipelines.
Move from discovery to a plan, or from a requested run to its job outcome.
Review pipeline scope and get explicit confirmation for destructive actions.
More than a pipeline suggestion
Pipeline work often means finding a connection, checking objects, setting up a run, and interpreting its result. Give your assistant the task and let it work through those steps with Supaflow.
01
Tell your assistant what you want to move and where it should go. It can inspect your connections, explore source objects, and prepare the pipeline for review.
02
Ask for fresh data from an existing pipeline. Your assistant can start the run, check its progress, and summarize the outcome reported by Supaflow.
03
Bring job details and available logs into the conversation. Understand the reported error and review the next action before changing your setup.
04
Inspect a pipeline’s current selection, explore the source catalog, and update the scope when your reporting needs change.
05
Set a cadence and timezone, review the schedule, and manage recurring runs once your pipeline is ready.
06
Find your connections and pipelines, inspect their configuration, and check recent jobs without assembling the context yourself.
See the work in conversation
These illustrative conversations show supported workflows. Names, responses, and progress are examples; your assistant uses the resources and results returned from your own workspace.
Workflow 1
Start with the data you need. Your assistant can look at the available source objects and destination, then prepare a concrete plan.
Choose the source, destination, and object scope before creating the pipeline.
You
Plan a Salesforce-to-Snowflake pipeline for Accounts and Opportunities. Show me the plan before creating it.
I’ll check your workspace, connections, and Salesforce catalog first.
Source: Salesforce Destination: Snowflake Selected objects: Account, Opportunity
Here is the pipeline plan. Would you like me to create it with these objects?
Workflow 2
Use the pipeline you already have. Follow the run through its actual job status, then see the reported outcome in the conversation.
Follow a requested run from its initial status through to the reported outcome.
You
Run my Salesforce-to-Snowflake pipeline and monitor it to completion.
I’ll verify the pipeline and start a normal sync using its current object selection.
Example job progression: queued → running → completed
The job is complete. I’ll summarize the result and any metrics returned by Supaflow.
Workflow 3
Ask about the failed job instead of searching through dashboard pages. Your assistant can inspect reported errors and explain what needs attention.
Review the diagnosis and recommended action before changing a connection or running the pipeline again.
You
Why did my latest pipeline run fail? Explain the error and recommend the next action.
I’ll inspect the failed job and the available details before recommending a change.
Example error: the destination connection needs attention.
Check the destination connection in Supaflow first. Once it is working, we can review whether to run the pipeline again.
Workflow 4
Describe when the pipeline should run. Your assistant can inspect existing schedules and prepare the requested cadence and timezone for review.
Make the schedule explicit so recurring runs match the way your team works.
You
Schedule this pipeline every weekday at 7 a.m. America/Los_Angeles. Show me the schedule before saving it.
I’ll check the pipeline’s existing schedules, then prepare the requested timing.
Cadence: Monday–Friday Time: 07:00 Timezone: America/Los_Angeles
Would you like me to save this schedule for the selected pipeline?
The conversation stays grounded in the platform you use for data movement. Your assistant works with Supaflow’s connections, source catalogs, pipeline configuration, and job results.
The assistant can inspect accessible resources before planning a change. It does not need to guess what connections or objects exist.
Review the source, destination, and selected objects. Account permissions apply, and destructive operations require explicit confirmation.
Supaflow executes the requested work. Your assistant can check job status, inspect available details, and summarize the outcome it receives.
Start where you already work
Choose your assistant and follow its guide to install Supaflow, connect your account, and start with your workspace.
Install the Supaflow plugin from the public ChatGPT listing. Plan a pipeline, follow a sync, or investigate a failed job in chat.
Use Supaflow in ChatGPTConnect Supaflow to Claude. Explore your available connections and source objects, then work through your next pipeline task.
Use Supaflow in ClaudeNew to Supaflow? Create an account and configure your source and destination connections. Already using Supaflow? Connect your existing account and ask your assistant to inspect a pipeline or prepare your next one.
Supaflow service pricing and your AI client’s access requirements apply. See Supaflow pricing.
Agentic data pipelines use an AI agent to carry out multiple steps in pipeline work, such as inspecting connections, planning a pipeline, starting a run, and checking its outcome. With Supaflow, you request the task in your assistant while Supaflow provides the pipeline resources and execution.
Explore connections and source catalogs, prepare and create pipelines, change object selections, run syncs, inspect jobs and available logs, and manage schedules. Access follows the connected account’s workspace permissions.
These terms describe a broad category of AI-driven data work. Supaflow focuses on practical data integration workflows: building and operating pipelines through conversation. The examples on this page show the current scope rather than promising every data engineering task.
The workflows shown here run when you request them in your assistant. You can ask it to monitor a job, investigate failures, or review a change. This page does not describe an unattended monitoring or automatic repair service.
Yes. Connect your Supaflow account and select a workspace. Configure source and destination connections in Supaflow before creating or running a pipeline. Existing users can work with the connections and pipelines they already have.
The client guides cover separate Supaflow Code editions for local Codex and Claude Code. Install the matching edition from GitHub for private-agent workflows with a local shell and the Supaflow CLI. Hosted chat plugins cannot manage local agents. Guided development and testing of new connectors are coming soon.