Integrations

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. Your AI agent can search the catalog, list connections, and call integration APIs on your behalf. From the terminal, runwork integrations call lets you proxy API requests through any connected service.

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.

Integrations get useful when they meet each other. HubSpot syncing to Slack, a Stripe payment triggering its own follow-up, a whole marketing stack answering to one agent. Describe the one you need and it deploys as a complete app, not a connection you have to babysit.