Tools & Integrations
Tools give your agents superpowers - the ability to fetch data, perform actions, and connect with external services.
What Are Tools?
Tools are functions your agent can call to:
- Fetch live data from websites
- Search databases
- Create/update content in external systems
- Perform calculations
- Access APIs
Example: A customer support agent with WordPress integration can check order status, update tickets, and fetch product information.
Two Types of Tools
1. Native Tools (Built-in)
Three core tools available to all agents:
search_web- Search the internet for real-time informationfetch_url- Retrieve content from any web pageget_current_time- Get current date/time in any timezone
These tools are always available and require no configuration.
2. Custom Integrations (MCP Protocol)
The platform is built like Lego blocks - highly scalable and modular. We can integrate ANY public API or data source as a custom MCP server.
Currently available:
- WordPress - Full WordPress REST API integration (posts, pages, custom post types, users)
Coming soon:
- GitHub, Shopify, Stripe, Slack, and more
Bespoke integrations:
- Your internal CRM or database
- Industry-specific APIs
- Custom business systems
- Any public API with documentation
How it works: If an API exists and has documentation, we can build a custom MCP integration for you or your client. Each integration becomes a reusable Lego block in your toolkit.
Enabling Tools for Your Agent
Step 1: Navigate to Integrations
- Go to workspace ā agent page
- Click Integrations tab
- Browse available tools
Step 2: Enable a Tool
- Find the tool you want
- Toggle the switch to enable it
- Tool is now available to your agent
That's it! For native tools, no further configuration needed.
Step 3: Configure (If Needed)
Some tools require configuration:
For MCP Tools:
- Click "Configure" button
- Enter credentials (API key, username, etc.)
- Save configuration
- Test in playground
For Tool Permissions (advanced):
- Click "Tools" button (MCP tools only)
- Select which specific functions to allow
- Example: WordPress has 10+ functions - you can enable only "list posts" and "create post"
Currently Available: WordPress Integration
Connect your WordPress site to let agents:
- List posts, pages, and custom post types
- Create new content
- Update existing content
- Delete content (with proper permissions)
- Manage users and site settings
Authentication: Application Password (generated in WordPress admin)
Setup steps:
- Enable WordPress tool in Integrations tab
- Click "Configure"
- Enter:
- WordPress site URL (https://example.com)
- WordPress username
- Application Password
- Click "Save"
- Test in playground
Use cases:
- Auto-publish blog posts
- Customer support checking order status (WooCommerce)
- Content management assistant
- FAQ bot pulling from WordPress pages
Request Bespoke Integrations
The platform is like Lego - we can add any integration as a modular block.
What We Can Integrate
ā Any public API with documentation:
- E-commerce: Shopify, WooCommerce, Magento
- Communication: Slack, Discord, Microsoft Teams
- Payments: Stripe, PayPal, Square
- CRMs: Salesforce, HubSpot, Pipedrive
- Project management: Asana, Jira, Monday
- Marketing: Mailchimp, SendGrid, ActiveCampaign
- Social media: Twitter, LinkedIn, Instagram
- Custom internal APIs and databases
How to Request
Contact us with:
- API documentation - Link to the API docs
- Your use case - What do you need the agent to do?
- Authentication type - API key, OAuth, Basic Auth?
- Priority endpoints - Which API calls are most important?
Timeline: Most integrations take 1-2 weeks to build and test.
Cost: Bespoke integrations may have a development fee depending on complexity. Once built, they become reusable Lego blocks for all your clients.
Why This Approach Works
š§± Modular - Each integration is a separate MCP server š Reusable - Build once, use across multiple agents/clients š Scalable - Add unlimited integrations as your needs grow š Secure - Each client has their own credentials āļø Flexible - Control which functions each agent can access
Managing Tool Access
Viewing Enabled Tools
Integrations tab shows:
- Tool name and description
- Status - Enabled, Disabled, Needs Config
- Connection status - Connected, Not Connected, Error
- Actions - Configure, Manage Permissions
Disabling Tools
- Find tool in list
- Toggle switch to off
- Agent can no longer use this tool
Testing Tools
Use Playground to test if tools work:
- Go to agent page ā Test in Playground
- Ask a question that would use the tool
- Watch the tool being called in real-time
- Verify the response
Example: "What are my latest WordPress posts?" should trigger WordPress tool.
Tool Permissions (Advanced)
For MCP tools, you can control exactly which functions an agent can use.
Why Limit Permissions?
- Safety - Prevent accidental deletions
- Cost control - Some functions are expensive
- Compliance - Limit data access
How to Set Permissions
- Enable the MCP tool
- Click "Tools" button
- See list of available functions
- Check/uncheck functions to allow
- Save
Example: WordPress has functions like:
- ā
list_posts(safe, read-only) - ā
get_post(safe, read-only) - ā
delete_post(dangerous, maybe disable) - ā
update_user(risky, probably disable)
Costs & Pricing
Native Tools
- Free - No additional cost beyond AI token usage
- Included in platform
MCP Tools
- Connection: Free to connect
- Usage: Costs vary by service
- WordPress: Free (uses your WordPress API)
- Future integrations: May have API costs
Web Scraping
fetch_urltool costs ~$0.01 per page scraped- Charged from your credit balance
Troubleshooting
Tool not appearing?
- Ensure it's enabled (toggle on)
- Check agent has access to workspace
- Verify configuration is complete
Authentication errors?
- Double-check credentials
- Ensure API key/password is valid
- Check URL format (https required)
Tool not being used?
- Ask specific questions that need the tool
- Check system instructions don't prevent tool use
- Test in playground with verbose mode
Connection failed?
- Verify external service is online
- Check firewall/IP restrictions
- Try re-saving configuration
Best Practices
ā Do:
- Enable only tools your agent needs
- Test tools in playground before deployment
- Use tool permissions to limit risky functions
- Keep credentials secure
ā Don't:
- Enable all tools "just in case"
- Share API credentials insecurely
- Grant delete/update permissions unnecessarily
- Forget to test after configuration changes
Next Steps
Your agent now has tools and integrations:
- Managing AI Models - Configure model access
- Credits & Billing - Understand costs
- Deploy Your Agent - Go live