Skip to main content
This guide gets you from a fresh account to a live, running workflow as quickly as possible. You’ll create a simple automation that triggers on a schedule and sends a summary email — a pattern you can adapt to almost any use case. By the end, you’ll understand how the core pieces of RCB Automation fit together and have a workflow you can build on.
If you haven’t created an account yet, go to rcbautomation.com and sign up. The free plan includes everything you need to follow this guide.

Build your first workflow

1

Log in and open your dashboard

Go to rcbautomation.com and log in with your credentials. You’ll land on the Dashboard, which shows an overview of your workflows, recent activity, and connected integrations.If this is your first time logging in, the dashboard will be empty. That’s expected — you’re about to change that.
2

Create a new workflow

In the left sidebar, click Workflows, then click New workflow in the top-right corner.Give your workflow a descriptive name — for example, Daily summary email. A clear name makes it easier to find and manage your automations as you build more of them.Click Create to open the workflow builder canvas.
3

Add a trigger

Every workflow starts with a trigger — the event that kicks it off. On the canvas, click Add trigger to open the trigger picker.For this guide, select Schedule from the trigger list. This lets you run the workflow on a repeating time interval.Configure the schedule:
  • Set Frequency to Daily
  • Set Time to 08:00 AM
  • Set Timezone to your local timezone
Click Save trigger. The trigger node appears on the canvas.
Other common trigger types include Form submission, Webhook received, Record created, and Inbound email. You can swap the trigger type at any time without rebuilding the rest of your workflow.
4

Add an action

With the trigger in place, click the + button below the trigger node to add your first action.Select Send email from the action list. The action panel opens on the right side of the canvas.Fill in the email action fields:
  • To: Enter the recipient address (your own email is fine for testing)
  • Subject: Daily automation summary
  • Body: Add a short message, such as Your daily workflow ran successfully at {{trigger.time}}.
The {{trigger.time}} placeholder is a dynamic variable — RCB Automation replaces it with the actual trigger time when the workflow runs. You can insert variables from any previous step using the {{ }} syntax.Click Save action. The action node appears connected to the trigger on the canvas.
The Send email action uses RCB Automation’s built-in email delivery. To send from your own domain or through a third-party provider like SendGrid or Postmark, connect that integration first under Integrations.
5

Test the workflow

Before activating the workflow, run a test to confirm it works as expected.Click Test workflow in the top toolbar. RCB Automation executes the workflow immediately using sample data, bypassing the schedule trigger.A results panel opens showing each step’s status. Check that:
  • The trigger step shows Passed
  • The Send email action shows Success
  • The test email arrives in your inbox
If a step fails, click on it in the results panel to see the error details and adjust the configuration.
Test runs send real emails and perform real actions in connected systems. Use test accounts or sandbox environments when testing workflows that write data.
6

Activate the workflow

Once the test passes, click Activate in the top-right corner of the canvas.The workflow status changes from Draft to Active. RCB Automation will now run it automatically according to the schedule you defined.
Your workflow is live. It will run every day at 8:00 AM and send a summary email to the address you specified.
7

View the activity log

To see a record of every run, click Activity in the left sidebar, or open the workflow and click the Runs tab.The activity log shows:
  • Run time — when the workflow executed
  • StatusSuccess, Failed, or Skipped
  • Duration — how long the run took
  • Step details — expandable view of each step’s inputs, outputs, and any errors
Use the activity log to monitor your workflow’s health over time and to investigate any failures.

What to build next

Now that you have a working workflow, you can extend it or start building something new.

Core concepts

Learn about workflows, triggers, actions, conditions, and runs in depth.

Integrations

Connect your existing apps to use as triggers or action targets.

Conditions

Add branching logic so your workflow behaves differently based on data.

Webhooks

Trigger workflows from external systems using inbound webhooks.