Sign inStart your trial

Integrations

Connect external services to your workflows

Integrations are how Rills connects to your tools. Connect once, then use the integration in any workflow as a trigger or an action.

#How to connect

  1. Open Integrations in the sidebar.
  2. Browse or search the catalog. Integrations are organized by category, communication, CRM, payments, e-commerce, productivity, accounting, project management, and more.
  3. Click an integration and hit Connect.
  4. Authorize via OAuth (you’ll log in to the service and grant permissions) or paste an API key for services that use one.

Once connected, the integration shows up in the workflow builder. You can use it as:

  • A trigger (Integration Event node): your workflow runs when the service emits an event
  • An action (Integration Action node): your workflow performs an operation in the service

#Auth types

TypeWhen it’s used
OAuth 2.0Most major services (Google, Slack, Stripe, HubSpot, Notion).
API keyDeveloper tools, analytics, services without OAuth support.
Basic authSome legacy or self-hosted services.
NonePublic APIs that don’t require credentials.

OAuth handles token expiry and refresh automatically. API key integrations are simpler, paste, save, done.

#Multiple accounts

You can connect more than one account for the same service, personal Gmail and work Gmail, two Stripe accounts for different products. Each connection is independent. Workflow nodes pick which connection to use.

#Catalog

For the full list of currently-available integrations and their categories, browse the integration catalog .

#When a connection breaks

Tokens expire, services revoke access, scopes change. When something stops working, look at the integration page, connections that need attention are flagged with a warning.

Most fixes are: click Reconnect and re-authorize. Workflow configurations are preserved across reconnections, only the underlying credential is updated.

Common reasons for breaks:

  • Token expired and refresh failed: usually because the refresh token aged out. Reconnect.
  • Access revoked: someone removed Rills from the service’s authorized apps page. Reconnect.
  • Service changed required scopes: the service updated its API and needs new permissions. Reconnect with broader scopes.
  • Rate limited: a workflow sent too many requests. The step fails with a retryable error; configure a retry policy or reduce frequency.

See troubleshooting for specific errors.

#Trigger mechanisms

Different integrations push events to Rills in different ways:

  • Webhook: the service POSTs events as they happen. Instant, no credit cost. Most major services support this.
  • Scheduled: Rills queries on a fixed cron. Useful for batch work like “sync new contacts every morning.” Schedule itself is free; only the operations the workflow runs cost credits.

Webhooks are preferred where available.

#Custom integrations

Business and Enterprise plans can build custom integrations against any API. Define a base URL, auth, and the operations you need. Custom integrations are workspace-private, only the workspace that created them can see or use them.

Setup steps:

  1. Define the base URL (e.g. https://api.yourservice.com/v1).
  2. Pick auth (API Key, Basic Auth, OAuth 2.0, or None) and configure it.
  3. Define operations: HTTP method, path, parameters, request/response schemas.
  4. Optionally define an integration-level config schema for any settings the user provides at connect time.

Once defined, custom integrations behave exactly like built-in ones in the workflow builder.

#Scopes

When you connect an OAuth integration, you grant specific scopes. Each operation declares the scopes it needs. If you connect with a narrower set than an operation needs, that operation fails with a permissions error, other operations keep working.

Fix by reconnecting with broader scopes. Existing workflow configurations are preserved.

#See also