Top integrations for business operations teams building custom workflows in 2026

AI is only as good as the context you give it—and business operations teams have more of that context than anyone else in the organization. They sit closest to the business problems, understand where the bottlenecks are, and know exactly what needs to be fixed.

The manual data entry between Salesforce and Stripe. The copying and pasting of information from Jira into Notion. The requests that could be automated if someone just built the right tool. The problem isn't knowing what needs to be fixed—it's having the ability to fix it.

Traditionally, you've had three options: wait for engineering to build the needed tools (months of backlog), duct tape together some lightweight automations (brittle, limited logic), or force your process into another rigid SaaS tool (expensive, required workarounds).

Retool addresses this by giving operations teams the ability to build real, reliable tools your teams can actually depend on—not just prototypes that break under pressure. You can generate dashboards and approval workflows from natural language prompts, connect them to the SaaS tools you already use (Salesforce, Stripe, Slack, Notion, Jira), and deploy them with enterprise security built in.

Read on to learn which SaaS tools Ops teams are connecting to and what they're building with those connections.

First, what Ops teams need from integrations

Before diving into specific integrations, let's talk about what actually matters when you're building operational tools. Connecting to systems is table stakes. What separates a useful prototype from something your team relies on every day is security, reliability, and the ability to handle real business logic.

Features to look for when building operational tools

Security and compliance by default. When you're building tools that access customer data in Salesforce or payment information in Stripe, you need SSO integration with your company's identity provider, role-based access control to restrict who can see what, and audit logs that track every action for compliance. Retool handles this automatically. Your tools inherit your organization's security standards without requiring any configuration.
Reliability for business-critical workflows. You need query caching so repeated lookups don't hammer your CRM, error handling that doesn't break workflows when APIs are slow, and the ability to handle approval workflows that might take hours or days to complete. This is what separates automation that works during testing from automation that works when your team depends on it.
Real business logic, not just data passing. Ops workflows require conditional logic—if the deal is over $50k, route to VP approval; if the customer is in Europe, use GDPR-compliant templates. You need the ability to validate data, enforce business rules, and handle exceptions. Retool lets you build this logic without writing code, or drop into JavaScript when you need custom validation.
Building with AI without losing control. AI tools can generate a working app prototype in minutes. The problem is getting from prototype to something your team trusts with real customer data and real business decisions. Retool generates the scaffolding from a plain-language description—layouts, queries, and workflows included. From there, you're working with real, editable components, not a black box you're hoping holds together. The AI speeds up the start. You control the finish.
Multi-tool workflows that match reality. Ops work spans multiple systems. A customer escalation might query Salesforce for account details, check Stripe for payment history, create a Jira ticket, and send a Slack notification—all from one interface. Retool's 50+ pre-built integrations plus REST API support make this possible without maintaining separate tools for each system.

AI integrations for intelligent automation

The gap between AI prototypes and AI that actually works in your operations isn't capability—it's context and control. Retool bridges that gap by letting you embed AI directly into workflows that already have your business data, your approval logic, and your governance built in.

Model providers for operational intelligence

Retool connects to leading AI model providers, including OpenAI, Anthropic, and Google Gemini. For organizations with data residency requirements or proprietary models, Retool also supports custom AI provider configuration so you're never locked into a specific vendor or forced to send sensitive data to third-party APIs.

What teams are building

Customer email drafting tools. A support agent handling a billing dispute shouldn't spend 20 minutes crafting the right response. Build a tool where agents briefly describe the situation—customer tier, issue type, desired resolution—and the AI drafts a professional, on-brand email using your tone guidelines and the customer's Salesforce history. Agents review, adjust if needed, and send. Teams that have built this report cutting average response drafting time by more than half.
Support ticket classification and routing. When ticket volume spikes, manual triage creates a bottleneck. Build a workflow where incoming tickets are automatically analyzed by AI: issue type is classified, severity is assessed based on language and customer tier, and a routing recommendation is generated before a human ever reads it. Support ops reviews the suggestions rather than starting from scratch—accuracy improves and response times drop.
Meeting notes and action item extraction. After sales calls or customer check-ins, paste the transcript into your Retool tool. The AI pulls out action items with suggested owners and deadlines, flags key decisions, and creates follow-up tickets directly in Jira or Asana. What used to take 15–20 minutes of post-meeting admin happens in seconds, and nothing falls through the cracks.

Systems of record integrations

The systems your business runs on were built for administrators, not the operators who need them most. Direct access is often locked down, too complex, or both. Retool lets ops teams build controlled interfaces on top of these systems, so the right people can take action without needing raw database access or engineering support.

CRM and sales operations integrations

Revenue operations start with your CRM. Whether you're building customer lookup tools, deal review dashboards, or territory management interfaces, direct access to Salesforce, HubSpot, or Close enables you to create tools that don't just display data—they help your team take action.

Salesforce integration connects Retool to your CRM data, letting you build custom interfaces for accounts, opportunities, contacts, and custom objects. This integration uses OAuth for secure authentication and supports both reading and writing data.

HubSpot integration is built for teams running marketing and sales from a single platform. Query contacts, deals, and companies, and trigger HubSpot automation workflows directly from your Retool app.

For teams using Close or other CRM systems, Retool connects via native integrations or REST API connectivity to build custom workflows. For operations teams, the CRM is often the bottleneck – everyone needs data from it, but not everyone should have full access. These integrations let you build the right interface for each team, without opening up the whole system.

Finance and payment operations integrations

Finance operations require accurate data and careful controls. Whether you're reconciling payments, managing subscriptions, or investigating billing issues, you need tools that connect to payment systems while enforcing appropriate approval workflows.

Stripe integration gives your team controlled access to customer billing, subscription management, refund processing, and payment reconciliation. Rather than giving support or finance agents direct Stripe dashboard access, you decide exactly what actions are available, to whom, and with what approval requirements.

Project management and task tracking integrations

Operations teams coordinate work across engineering, operations, sales, and support. Project management integrations let you build tools that create, update, and track work without everyone needing full access to Jira, Linear, or Asana.

Jira integration connects to your engineering project tracking, letting you build interfaces that create tickets, update statuses, and query projects. This works with both Jira Cloud and Jira Server deployments.

Asana integration lets you build tools for teams coordinating work across departments, creating tasks, updating projects, and tracking progress.

Documentation and knowledge management integrations

Teams document processes, decisions, and runbooks across Notion, Google Docs, and wikis. These integrations let you build tools that reference documentation, update records, and maintain knowledge bases without manual copy-pasting.

Notion integration lets you query databases, create pages, and update records in your team's Notion workspace. You can build tools that reference runbooks, update process documentation, or maintain internal directories.

What teams are building

Deal review tools for sales leadership. Query Salesforce for all deals closing this quarter, group by stage and rep, and surface the ones that need executive review. Sales leaders can add approval notes, update close dates, or escalate deals to legal—all through a simplified interface that focuses on decision-making rather than navigating Salesforce fields.

Customer billing lookup for support teams. Support agents need to answer billing questions without exposing full Stripe access. Build lookup tools where they enter a customer email and see subscription status, payment history, and upcoming charges. Add buttons to process refunds or pause subscriptions—with approval workflows for amounts over $500—all without giving agents direct Stripe dashboard access.
Customer issue escalation tools. When support identifies urgent customer issues, they shouldn't need to understand Jira's complexity or engineering workflows. Build simple forms where support enters customer details, issue description, and severity. Your tool creates a properly-formatted Jira ticket with the right labels, assigns it to the appropriate team, sets priority based on severity, and sends a Slack notification to the on-call engineer—all from one click.
Customer runbook automation. Enterprise accounts often have custom processes—special billing terms, dedicated support contacts, unique SLA requirements. Instead of hunting through Notion for this information when issues arise, build customer lookup tools that pull the relevant Notion page automatically. Support and account management see the custom process, escalation contacts, and any special handling—right alongside CRM and billing data.

Database access for custom data needs

Not all data your teams need lives in SaaS tools. Custom application databases, internal systems, and data warehouses often hold the metrics and records that matter most—and accessing them safely requires the right controls.

PostgreSQL and relational databases

Retool supports all major relational databases: PostgreSQL, MySQL, Microsoft SQL Server, and Oracle. You can query production data, build admin panels, and expose specific records to the right teams – without giving anyone direct database access.

Data warehouses for analytics

When you need to build reporting dashboards or analyze historical data, Retool integrates with Snowflake, BigQuery, Redshift, and Databricks. Build dashboards and query interfaces that five business teams self-serve access to warehouse data – without spreadsheet exports or data team dependencies.

What teams are building

Revenue command center for leadership. A single dashboard that queries Stripe for MRR and recent charges, Salesforce for pipeline by stage and rep, and your application database for customer health scores—presented side by side in a single view. Leaders get the metrics they need on demand, without filing requests with engineering or waiting for a data team to pull a report.
User account admin panel for operations. A searchable table of user accounts where ops teams can update account status, change subscription tiers, or reset passwords—each action gated behind a confirmation step. A separate tab exposes a set of pre-approved bulk operations like re-syncing billing status from Stripe or clearing a stuck onboarding flag. Every action logs the admin's name, timestamp, and change to an audit trail, so teams can fix issues without ever touching the database directly.

Self-service metrics explorer for business teams. A query interface on top of your data warehouse where marketing, sales, or support select a metric, apply filters, and choose a time range from dropdowns. The tool generates and executes the SQL, then displays results in a chart or table—no spreadsheet exports, no waiting for data team availability, and no way to accidentally run a destructive query.

Messaging and collaboration integrations

When workflows complete or require approvals, the right people need to know. Messaging integrations automate notifications and enable teams to respond to operational events through the tools they already use.

Slack for team communication and workflows

Slack integration lets you send notifications, create approval workflows, and build operational tools that route through your team's communication channels. The integration uses OAuth for secure authentication.

Microsoft Teams for enterprise collaboration

Microsoft Teams integration provides similar capabilities for organizations using Microsoft's collaboration platform.

Email for stakeholder communication

For formal stakeholder communications or customer-facing nottications, Retool supports SendGrid and SMTP for email delivery.

What teams are building

Approval workflows through Slack. When operations needs to process refunds over $1,000, make bulk pricing changes, or update customer contracts, route these through approval workflows. The requester submits through your Retool app with context and justification. Notifications go to the appropriate approver in Slack. They review and respond directly in Slack. The operation only executes after approval, and everything logs to your audit trail for compliance.
Automated weekly business digest. A scheduled workflow that runs every Monday morning, pulling closed deals from Salesforce, revenue metrics from Stripe, and ticket resolution rates from Zendesk—then formatting and sending a tailored summary to each team. Finance gets a revenue snapshot via email, sales leadership sees closed deals in their Slack channel, and support gets ticket trends. No manual report assembly, no one getting left out.
Incident notifications with context. When operational issues occur—payment failures, system errors, or customer escalations—your team shouldn't have to hunt for context across multiple systems. Build incident notifications that fire automatically, include affected customer data from Salesforce or Stripe, and surface action buttons to investigate or remediate—all within the Slack channel where your team is already responding.

Customer support and service integrations

Support operations require quick access to customer information across multiple systems. These integrations let you build unified support tools that combine CRM data, payment history, and ticketing systems.

Zendesk for customer support

Zendesk integration connects to your support ticketing system, letting you build tools that query tickets, update statuses, and create customer views.

Front for team email management

Front integration enables teams using Front's shared inbox to build custom workflows around email management and customer communication.

What teams are building

Unified customer views for support agents. When customers contact support, agents need complete context—Salesforce account details, Stripe subscription status, recent tickets from Zendesk, product usage data. Build lookup tools where agents enter a customer email and see everything. They can process refunds, update account details, escalate to account management, or create follow-up tickets—all without switching between five different systems.

Ticket escalation router for support operations. A dashboard that monitors incoming Zendesk tickets and automatically flags ones that meet escalation criteria—high-value accounts, repeat contacts, or specific issue types. Each flagged ticket is enriched with Salesforce account tier and Stripe subscription data, then routed to the right team with SLA deadlines attached. Support ops sees every escalated ticket, its current owner, and time remaining in one view—rather than triaging manually across multiple queues.
CSAT follow-up automation. After support tickets close, build workflows that send CSAT surveys via email or Slack based on ticket type and customer tier. Responses flow back into Zendesk or your data warehouse. Low scores automatically create follow-up tasks for support leadership. You measure support quality without manual survey coordination.

Cloud storage and file management integrations

Ops workflows often involve files—contracts, reports, data imports, customer documents. Storage integrations let you build tools that upload, download, and manage files without everyone needing cloud console access.

Amazon S3 and Google Cloud Storage

S3 and Google Cloud Storage integrations let you build file management tools where teams can upload, organize, and retrieve documents through a simple interface—without needing cloud console access or technical knowledge to manage storage.

Google Sheets for collaborative data

Google Sheets integration enables teams to build tools that read from or write to spreadsheets, useful when stakeholders manage data in sheets but need that data in operational workflows.

What teams are building

Contract and document management for sales. Sales teams generate proposals, contracts, and statements of work that need to be stored, versioned, and accessible. Build tools where sales uploads documents to S3 with proper naming conventions and metadata. The tool organizes files by customer and deal, generates shareable links with expiration dates, and notifies legal or finance when review is needed—so everyone finds documents without hunting through shared drives.
Data validation and sync tool. When finance or operations manages data in Google Sheets, build a tool that pulls that data into a structured workflow, validates it against business rules, and syncs approved changes back to the sheet—so spreadsheets stay as the input method without becoming the system of record.
Audit documentation tracker for compliance teams. A centralized tool where compliance and finance upload audit artifacts—signed agreements, policy acknowledgments, evidence exports—to S3 with required metadata like document type, owner, and review date. The tool surfaces documents approaching their review deadline, sends automated reminders via email or Slack, and generates a summary view that shows coverage across compliance categories—so audit prep is a dashboard check rather than a last-minute scramble.

It's time to build the solutions your team actually needs

Business operations teams have always known what's broken. The friction has been execution—translating that knowledge into tools that actually work, without waiting months for engineering bandwidth.

Retool gives operations teams something they've never had before—the ability to build, own, and iterate on the tools their business actually needs, without waiting on engineering, without duct-taping automations together, and without forcing processes into software that wasn't built for them.

The teams getting the most value aren't just connecting systems. They're using AI to build the exact workflows their business needs, iterating as processes evolve, and freeing up engineering for the work only engineers can do. That's what it looks like when operations teams are finally equipped to move as fast as the problems they're solving.