Skip to main content
Before you can use an app inside a workflow, you need to connect it to RCB Automation. The connection process varies slightly depending on whether the app uses OAuth or an API key, but both take only a few minutes. Once connected, the app is available as a trigger or action source across all of your workflows.

​
Find an integration

1

Open the integrations marketplace

In the left navigation, click Integrations, then click Add integration in the top-right corner.
2

Search or browse by category

Use the search bar to find a specific app by name, or browse by category: Productivity, CRM, Communication, Databases, E-commerce, or Developer tools.
3

Select the app

Click the app you want to connect. A detail panel opens showing what the integration supports and what authentication method it uses.

​
Connect with OAuth

OAuth is used by most major apps, including Google Workspace, Slack, HubSpot, and Salesforce. The connection flows through that app’s own sign-in page — RCB Automation never handles your password.
1

Click Connect

In the app detail panel, click Connect. If the app supports OAuth, you’ll be redirected to that app’s authorization page.
2

Sign in to the app

Log in with the account you want to connect. If you’re already signed in, the app may skip directly to the permissions screen.
3

Review and grant permissions

The app shows you a list of permissions RCB Automation is requesting — for example, read access to your calendar or the ability to send messages on your behalf. Review the list and click Allow (the exact button label depends on the app).
4

Name your connection

After authorizing, you’re returned to RCB Automation. Give the connection a descriptive name — for example, Marketing Slack workspace or Sales HubSpot account — and click Save.
Some apps scope OAuth tokens to a specific account or workspace. If you need to automate actions across two different Slack workspaces, for example, create a separate connection for each one.

​
Connect with an API key

Apps that don’t support OAuth — including many databases, developer tools, and niche SaaS products — use an API key that you generate inside that app’s settings, then paste into RCB Automation.
1

Open the app's settings

Log in to the app you want to connect and navigate to its developer or API settings. Common locations include Settings → API, Account → Integrations, or Developer → API keys. RCB Automation shows you where to look in the connection panel.
2

Generate an API key

Create a new API key (or copy an existing one). Use a name that identifies the key’s purpose — for example, RCB Automation — so you can revoke it later if needed.
3

Enter the key in RCB Automation

Back in RCB Automation, paste the API key into the API Key field in the connection panel. Some apps also require a base URL or additional credentials — fill in any other required fields.
4

Name and save your connection

Give the connection a descriptive name and click Save. RCB Automation validates the key before saving.
Treat API keys like passwords. Don’t share them or commit them to source control. If a key is exposed, regenerate it in the connected app immediately, then update your RCB Automation connection with the new key.

​
Rename and label connections

You can connect the same app multiple times — useful if you manage accounts for multiple clients or environments. To tell them apart, give each connection a specific name. To rename an existing connection:
  1. Go to Integrations in the left navigation.
  2. Find the connection and click the … menu next to it.
  3. Select Rename, enter a new name, and click Save.
Clear names like Client A — Salesforce or Staging — PostgreSQL make it easier to pick the right account when building workflows.

​
Test a connection

Before using a connection in a workflow, confirm that it’s working:
  1. Go to Integrations and find the connection you want to test.
  2. Click the … menu and select Test connection.
  3. RCB Automation sends a lightweight request to the connected app and reports whether the credentials are valid.
A green checkmark means the connection is active. A red error means the credentials have expired or are incorrect — see reconnecting a connection below.

​
Reconnect or refresh credentials

OAuth tokens and API keys can expire or be revoked. When this happens, any workflow using that connection will fail until the credentials are refreshed.
If a connection expires while a workflow is running, that workflow will log an authentication error and stop. Reconnect the integration to resume normal operation. Workflows do not automatically retry runs that failed due to an expired connection.
To reconnect:
  1. Go to Integrations and find the connection showing an Expired or Error status.
  2. Click the … menu and select Reconnect.
  3. For OAuth apps, you’ll be sent through the sign-in flow again. For API key apps, paste in the new or refreshed key.
  4. Click Save. The connection status updates immediately.

​
Disconnect an integration

Disconnecting removes the stored credentials and makes the connection unavailable in the workflow builder. Any workflow steps that use the connection will fail until you reconnect or replace it with a different account. To disconnect:
  1. Go to Integrations and find the connection you want to remove.
  2. Click the … menu and select Disconnect.
  3. Confirm the removal when prompted.
Disconnecting an integration in RCB Automation does not revoke the permissions you granted in the connected app. If you want to fully remove access, also revoke the token or delete the API key in the connected app’s settings.