What Are Recipes?
Recipes are pre-designed combinations of connectors that solve specific use cases. Instead of figuring out which connectors to combine and how to configure them, use a recipe to get started instantly.Think of recipes as “templates” or “blueprints” for building powerful AI agents.
Why Use Recipes?
Proven Patterns
Based on real-world production workflows used by teams
Save Time
Skip trial and error - start with working configurations
Best Practices
Optimized tool selections and permissions
Customizable
Use as starting point, adjust to your needs
Available Recipes
Triage Agent
Auto-investigate production issuesConnectors: Sentry + GitHub + Slack + RenderPerfect for: DevOps teams, SRE, incident response
Customer Support Agent
Handle support tickets intelligentlyConnectors: Linear + Slack + Notion + IntercomPerfect for: Support teams, customer success
DevOps Automation Agent
Deploy, monitor, and maintain servicesConnectors: GitHub + Render + Sentry + PagerDutyPerfect for: Development teams, DevOps engineers
Data Analysis Agent
Query, analyze, and report on dataConnectors: Supabase + Notion + SlackPerfect for: Data teams, analysts, product managers
How to Use a Recipe
1
Choose a Recipe
Browse recipes and select one that matches your use case
2
Click 'Use This Recipe'
In the recipe page, click the “Use This Recipe” button
3
Connect Services
Authenticate required connectors (OAuth, one-click)
4
Review Tools
See which tools are enabled by default. Adjust if needed.
5
Deploy
Your toolset is deployed and ready to use!
6
Test in Playground
Try example workflows to see it in action
7
Connect to AI
Add to Claude Desktop, Cursor, or your AI agent
Recipe Components
Each recipe includes:Connectors
List of pre-built integrations to connect:- Which services (Linear, GitHub, Slack, etc.)
- Why each is needed
- Alternative options (e.g., Jira instead of Linear)
Tools
Specific tools enabled from each connector:- Read operations (safe, always enabled)
- Write operations (carefully selected)
- Blocked tools (dangerous operations disabled by default)
Configuration
Recommended settings:- Tool permissions (allow, block, require approval)
- Optimization features (knowledge indexing, code indexing)
- Workflows (multi-tool automation sequences)
Example Workflows
Real-world scenarios showing the agent in action:- Step-by-step tool execution
- Expected outcomes
- Common edge cases
Customizing Recipes
Recipes are starting points. Customize them:Add More Connectors
Add More Connectors
Expand the recipe with additional services:
- Triage Agent + PagerDuty for alerting
- Support Agent + Salesforce for CRM
- DevOps Agent + DataDog for monitoring
Remove Connectors
Remove Connectors
Don’t need all connectors? Remove unused ones:
- Triage Agent without Slack (if you use Discord)
- Support Agent without Intercom (if you use Zendesk)
Adjust Tool Permissions
Adjust Tool Permissions
Change which tools are allowed:
- Block destructive operations (delete, archive)
- Require approval for sensitive actions (deploy, merge PR)
- Enable additional tools as you gain confidence
Add Knowledge/Code Indexing
Add Knowledge/Code Indexing
Enhance with search capabilities:
- Add company documentation (knowledge indexing)
- Add code repositories (code indexing)
- Agents can reference docs and code automatically
Recipe Comparison
| Recipe | Time to Setup | Complexity | Primary Use Case |
|---|---|---|---|
| Triage Agent | 10 min | Medium | Incident response |
| Customer Support | 10 min | Low | Ticket handling |
| DevOps Automation | 15 min | High | Deployment workflows |
| Data Analysis | 10 min | Low | Querying & reporting |
Success Stories
Triage Agent: 90% Faster Incident Response
Triage Agent: 90% Faster Incident Response
Company: TechCorp (50 engineers)Before: 30 minutes to triage production errors manuallyAfter: 3 minutes with Triage AgentImpact:
- 10x faster incident response
- Reduced MTTR from hours to minutes
- Engineers focus on fixes, not investigation
Support Agent: 50% Fewer Escalations
Support Agent: 50% Fewer Escalations
Company: SaaS Startup (10-person support team)Before: 40% of tickets escalated to engineeringAfter: 20% escalation rate with Support AgentImpact:
- Agents answer common questions automatically
- Engineering team freed up for development
- Faster customer response times
DevOps Agent: Automated Deployments
DevOps Agent: Automated Deployments
Company: E-commerce PlatformBefore: Manual deployment process, 30 minutes per deployAfter: Automated with DevOps Agent, 5 minutesImpact:
- 5x more frequent deployments
- Fewer human errors
- Automated rollback on errors
Best Practices
Start with One Recipe
Start with One Recipe
Don’t try to implement all recipes at once:
- Choose your biggest pain point
- Implement one recipe
- Test thoroughly
- Roll out to team
- Then add more recipes
Test in Playground First
Test in Playground First
Before deploying to production:
- Test each tool individually
- Test multi-tool workflows
- Test error handling
- Verify tool permissions
Use Test Accounts
Use Test Accounts
Connect test workspaces first:
- Linear: Test workspace
- Slack: Test channel (#testing)
- GitHub: Test repository
Monitor Analytics
Monitor Analytics
After deploying:
- Track tool usage
- Monitor error rates
- Review execution traces
- Optimize based on data
Share with Team
Share with Team
Creating Your Own Recipe
Have a unique workflow? Create a custom recipe:- Identify Use Case: What problem are you solving?
- Select Connectors: Which services do you need?
- Configure Tools: Enable relevant operations
- Test Workflows: Verify multi-tool sequences work
- Document: Write down the workflow steps
- Share: Export configuration, share with team
Need Help?
Contact support@tadata.com to discuss custom recipes for your use case.