Skip to main content
If you’re new to RCB Automation or evaluating whether it fits your use case, this page answers the questions we hear most often. For step-by-step guides, see the links within each answer. If your question isn’t covered here, reach out to support@rcbautomation.com.
RCB Automation is a SaaS business automation platform that lets you connect apps, systems, and services so they work together automatically — without manual intervention. You build workflows that listen for events (a new row in a spreadsheet, an incoming form submission, a scheduled time), apply logic, and take actions (send an email, update a CRM record, post to Slack, call an API).Common use cases include syncing data between systems, sending notifications when conditions are met, generating reports on a schedule, routing leads through approval processes, and triggering actions in one tool based on events in another. If a task is repetitive, rule-based, and involves moving or transforming data, RCB Automation can likely handle it.
No. RCB Automation is designed to be used without writing code. The visual workflow builder lets you drag, drop, and configure steps using point-and-click interfaces. You can map data between steps, set conditions, and build branching logic entirely through the UI.That said, if you are comfortable with code, you can use the Custom Code action step to write JavaScript that runs inline within your workflow — useful for data transformation, complex calculations, or building custom logic that the visual builder doesn’t cover. The REST API is also available for programmatic workflow management.
The fastest way to get started is to follow the quickstart guide, which walks you through creating your first workflow in under ten minutes. You’ll connect an integration, configure a trigger, add an action, and activate your workflow.After that, explore the core concepts page to understand how triggers, actions, conditions, and runs fit together. From there, you can build on pre-built templates in the workflow library or start from scratch.
RCB Automation supports a growing library of integrations covering popular business tools across categories including CRM, email, spreadsheets, project management, customer support, communication, e-commerce, and developer tools. You can browse the full list on the integrations overview page.For services not yet in the library, you can connect to any app that exposes a REST API using the HTTP Request action, or receive data from any service that can send an HTTP POST request using the Webhook trigger. This means almost any modern web service can be integrated, even without an official connector.
The number of workflows available depends on your plan. All plans support multiple active workflows, and higher-tier plans increase the limits on active workflows, team members, and run volume. You can view your current limits and usage under Settings > Usage.Workflows in Draft status do not count against your active workflow limit, so you can build and iterate on workflows before activating them without worrying about hitting your cap.
A run is a single execution of a workflow — from the moment a trigger fires to the moment the last step completes (or fails). Each time your workflow is triggered, whether by a schedule, a webhook, or a manual test, that counts as one run.Run limits reset on a monthly billing cycle. If a workflow fails and you use the Retry step feature, that retry counts as part of the same run and does not consume an additional run from your quota. A full restart of the workflow from the beginning does count as a new run. You can monitor your monthly run consumption in Settings > Usage.
Yes. RCB Automation supports team workspaces where multiple members can view, edit, and manage workflows together. You can invite team members under Settings > Team and assign them roles that control what they can access.Available roles include Admin (full access), Editor (can build and edit workflows but not change billing or team settings), and Viewer (read-only access to workflows and activity logs). This makes it safe to give stakeholders visibility into automations without granting them edit access. See the teams and permissions guide for full details.
RCB Automation encrypts all stored credentials — including OAuth tokens and API keys — at rest using AES-256 encryption. Credentials are never stored in plain text and are not exposed in logs or run history.Data processed by your workflows (payloads, step outputs) is transmitted over TLS and is retained in run logs for a rolling period defined by your plan. You can configure data retention settings under Settings > Account. RCB Automation does not sell or share your data with third parties. For enterprise compliance requirements including SOC 2, GDPR, and data residency, contact support@rcbautomation.com.
When a workflow run fails, RCB Automation records the failure in the Activity log with the full error detail, including which step failed and the error message returned. You can inspect this at any time to understand what went wrong.You can configure failure notifications under Settings > Notifications. Options include email alerts for failed runs, daily digest summaries, and (on higher plans) Slack or webhook notifications. Notifications can be scoped to specific workflows or applied workspace-wide.
Yes. Every workflow can be tested without activating it. Use the Test trigger button to simulate an incoming event with sample data, or click Run now to execute the workflow immediately using a previously received payload.Individual steps can also be tested in isolation using the Test step button within the workflow editor — useful for verifying that an API call returns the data you expect before wiring it into a larger automation. Runs performed during testing are counted against your monthly run quota but are clearly marked as test runs in the Activity log.
To pause a workflow so it no longer responds to triggers, open the workflow and click Pause in the top-right corner. The workflow remains intact and can be re-activated at any time. Runs that are already in progress when you pause will complete.To cancel a run that is actively executing, go to Activity, find the in-progress run (marked with a spinning indicator), and click Cancel run. This stops the run immediately at its current step. Completed steps are not undone — any actions that already executed (such as sent emails or created records) will not be reversed.
Cancelling a run does not undo any actions that have already completed. If a step sent an email or created a record before you cancelled, that action remains in effect.
Start with the troubleshooting guide, which covers the most common issues and their fixes. The Activity log is also one of the best diagnostic tools — it shows exactly what happened during every run, including full error messages.If you can’t find an answer in the documentation, reach out to the support team at support@rcbautomation.com. Include a description of what you’re trying to do, the name of the affected workflow, and any error messages you’ve seen — this helps the team resolve your issue as quickly as possible.