superglue offers multiple interfaces for different workflows. Choose based on
your use case, team, and deployment requirements.
Quick Decision Guide
Use UI/Chat When
β
Prototyping new integrationsβ
Exploring APIs and data sourcesβ
Testing integration ideas quicklyβ
Collaborating with non-technical usersβ
Learning whatβs possible with an APIβ
One-off data extraction / analysis tasks
Use MCP/SDK When
β
Production deploymentsβ
Automated workflows and pipelinesβ
Custom error handling and retry logicβ
Integration with existing systemsβ
CI/CD and version controlβ
Scale and performance requirements
UI/Chat Interface Deep Dive
What Makes It Powerful
The UI/Chat interface is like having a data engineer AI assistant that understands APIs:Instead of reading API docs and writing code:Traditional approach:superglue UI approach:
βGet all Stripe customers created in 2024, show me their email, subscription status, and total revenueβThatβs it. superglue handles the API calls, pagination, transformations, and formatting.
Best UI/Chat Use Cases
Data Exploration
Data Exploration
Scenario: You need to understand what data is available in a new system.
Traditional: Read API docs, write test scripts, examine responses With
superglue UI: > βShow me what data is available in our Salesforce
instanceβ > βWhat are the different types of HubSpot deals and their
properties?β > βGive me a sample of our PostgreSQL customers tableβ Get
immediate answers with actual data samples.
Stakeholder Demos
Stakeholder Demos
Scenario: You need to show business stakeholders what data integration is
possible. Demo in real-time: > βLet me show you what customer data we can
pull from Stripeβ¦β > βHereβs how we could sync this with our CRMβ¦β > βAnd
we could automatically generate reports like thisβ¦β Non-technical
stakeholders can see exactly whatβs possible without looking at code.
Quick Data Fixes
Quick Data Fixes
Scenario: You need to extract or fix data quickly. Emergency data
request: > βI need all customers who signed up yesterday but didnβt receive
welcome emailsβ > βUpdate all HubSpot contacts missing phone numbers with data
from our databaseβ > βExport all Jira tickets created this week for the
security teamβ Get results in minutes, not hours.
Learning & Training
Learning & Training
Scenario: Team members need to learn about APIs and integrations.
Natural learning progression: 1. Start with simple queries in natural
language 2. See how superglue translates them to API calls 3. Understand the
data structures and transformations 4. Graduate to using the SDK for
production Perfect for onboarding new team members.
SDK Deep Dive
Production-Grade Features
Programmatic Control
Error Handling
Integration Patterns
CI/CD Integration
SDK Use Cases
Automated Data Pipelines
Automated Data Pipelines
Requirements:
- Runs on schedule (hourly, daily, etc.)
- Handles large datasets reliably
- Integrates with monitoring and alerting
- Version controlled and deployable
Real-time Event Processing
Real-time Event Processing
Requirements:
- React to webhooks and events
- Low latency processing
- Conditional logic and branching
- Integration with message queues
Custom Business Logic
Custom Business Logic
Requirements:
- Complex conditional workflows
- Custom validation and business rules
- Integration with internal systems
- Advanced error handling and recovery
Migration Path: UI to SDK
Phase 1: Prototype in UI
1
Start with Natural Language
Use the UI to rapidly prototype and test your integration: > βGet all
Salesforce opportunities closed this month with contact detailsβ
2
Refine and Test
Iterate on the query until you get exactly the data you need: > βActually, I
need opportunities over $10k with the primary contactβs email and phoneβ
3
Save the Workflow
Once it works perfectly: > βSave this as βmonthly-sales-reportββ
Phase 2: Productionize with SDK
1
Export Workflow Definition
2
Add Production Features
3
Deploy and Monitor
Team Collaboration Patterns
Business Analyst (using UI):
βI need a report showing customer churn patterns from our subscription dataβCreates and tests the workflow in UIData Engineer (using SDK):
Performance Considerations
UI/Chat Performance
Optimized for:
- Interactive response times (< 30 seconds)
- Small to medium datasets (< 10k records)
- Exploratory workflows
- Real-time feedback
- Not suitable for large batch processing
- No parallel execution control
- Limited customization of timeouts/retries
SDK Performance
Optimized for:
- Large datasets (millions of records)
- Parallel workflow execution
- Custom timeout and retry strategies
- Webhook-based async processing
Cost Optimization
Use UI/Chat for cost-effective development:
- Rapid prototyping without engineering time
- Validate integrations before committing to development
- Business stakeholders can test ideas directly
- Reduce back-and-forth between business and engineering
Next Steps
Try Both Approaches
Start with the UI to prototype your first integration, then see how to
productionize it with the SDK
API Ranking Benchmark
See concrete performance comparisons between superglue and traditional
approaches
Data Pipeline Patterns
Learn common patterns for different types of data integration projects
Production Examples
See real examples of UI workflows productionized with the SDK