Runwork
8,000+ Recipes See integrations in action

Browse automation recipes that combine 3,200+ integrations in real-world patterns.

Browse recipes
All Features

Integrations

Connect 3,200+ services in one click

HubSpot, Stripe, Slack, GitHub, Google Sheets, and more. Connect once at the workspace level, and every app has access. Integrations automatically become AI agent tools.

Capabilities

3,200+ Pre-Built Connectors

CRM, payments, communication, storage, analytics. All major platforms covered.

Workspace-Level Auth

Connect once, use everywhere. No need to re-authenticate for each app.

OAuth & API Keys

Support for OAuth2 flows and API key authentication. Secure credential storage.

Auto-Generated AI Tools

Integrations automatically become tools your AI agents can use. HubSpot connected? Your agent can create contacts.

Real-Time Proxy

API calls proxied through Runwork with rate limiting, retries, and error handling.

Integration Scoping

Control which apps can access which integrations. Keep sensitive connections locked down.

Use Cases

Sync CRM with internal tools Payment processing Slack notifications GitHub automation Email campaigns Analytics pipelines

Why It Matters

How It Works

Integrations in Runwork connect your workspace to external services like CRMs, payment processors, communication tools, and databases. Unlike traditional integration approaches where each application manages its own connections, Runwork handles authentication at the workspace level—connect once, and every app, automation, and AI agent can use that connection.

Adding an integration takes seconds. Navigate to your workspace settings, find the service you need, and complete the OAuth flow or enter your API credentials. Runwork securely stores these credentials and manages token refresh automatically. No more dealing with expired tokens or OAuth callback URLs in your application code.

The real power comes from how integrations work with the rest of the platform. Connected services automatically become available as tools for your AI agents. If you've connected HubSpot, your agents can create contacts, update deals, or query your pipeline—just by asking. If you've connected Slack, agents can post messages or create channels. There's no additional configuration required.

For automations and workflows, integrations provide trigger sources and action destinations. Receive a webhook from Stripe when a payment succeeds, then update your internal entities and send a Slack notification—all in one flow. The integration layer handles the API complexity while you focus on business logic.

Security is built in. You control which apps can access which integrations through scoping rules. Sensitive connections (like payment processors) can be restricted to specific apps. All API calls are proxied through Runwork with automatic rate limiting, retry handling, and error logging. You get enterprise-grade reliability without building it yourself.

Want to see integrations in action? Browse our recipe library with over 8,000 automation patterns that combine multiple integrations in real-world workflows. From syncing HubSpot with Slack to processing Stripe payments with automated follow-ups—find proven patterns and deploy them as complete apps.

Frequently Asked Questions

How many integrations does Runwork support?
Runwork supports 3,200+ pre-built integrations covering CRM (HubSpot, Salesforce), payments (Stripe, PayPal), communication (Slack, Discord, email), storage (Google Drive, Dropbox), development tools (GitHub, GitLab), and many more categories. New integrations are added regularly.
How does workspace-level authentication work?
When you connect an integration in Runwork, the credentials are stored at the workspace level. This means you authenticate once, and every app, automation, and AI agent in your workspace can use that connection. No need to re-authenticate for each app or manage OAuth flows in your application code.
Can AI agents use integrations automatically?
Yes. Connected integrations automatically become tools available to your AI agents. If you connect HubSpot, agents can create contacts, update deals, or query data. If you connect Slack, agents can post messages. There is no additional configuration—agents understand available integrations and can use them when relevant.
How does Runwork handle API rate limits and errors?
All integration API calls are proxied through Runwork with built-in rate limiting, automatic retries with exponential backoff, and comprehensive error handling. If an external API is temporarily unavailable, Runwork handles retries automatically. You get enterprise-grade reliability without building it yourself.
Can I restrict which apps access certain integrations?
Yes. Integration scoping lets you control which apps can access which integrations. Sensitive connections like payment processors can be restricted to specific apps, while general-purpose integrations like Slack can be available workspace-wide. This gives you fine-grained security control.
Are there examples of how integrations work together?
Yes! Browse our recipe library with 8,000+ automation patterns that combine multiple integrations. See real-world examples like syncing CRM data with Slack notifications, processing payments with automated follow-up emails, or connecting your entire marketing stack. Each recipe can be deployed as a complete app.

Related Features

See How Teams Use Integrations

Ready to try Integrations?

Start vibe-coding with Runwork today.