Skip to main content

Connecting Tools

Rilo connects to your tools through three methods: Slack integration, email, and browser-based access. This guide covers how to set up each.

Slack Integration

Slack is the primary way to communicate with Rilo. Once connected, you can assign tasks by mentioning Rilo in any channel.

Setup

  1. An admin from your organization installs the Rilo Slack app from the customer portal
  2. Authorize the app for your workspace
  3. Invite Rilo to the channels where you want it to operate

How It Works

  • Rilo listens for mentions (@Rilo) in channels it has been invited to
  • Messages are validated using Slack’s signature verification (X-Slack-Signature + X-Slack-Request-Timestamp)
  • Tasks are queued and processed within your organization’s context
Rilo only processes messages in channels where it has been explicitly invited. It does not read messages in other channels.

Email

Rilo can receive tasks and communicate via email using your organization’s dedicated Rilo email address.

Setup

  1. Your organization is assigned a Rilo email address: rilo@<your-company>.mail.riloworks.com
  2. No additional configuration is needed — email ingestion is automatic

How It Works

  • Send an email to your Rilo address with the task in the subject line or body
  • Rilo processes the task and replies in the same email thread
  • Attachments are supported for providing context documents

Browser-Based Tools

Rilo accesses web applications through browser automation. This is how Rilo works with tools that don’t have direct API integrations — if the tool has a web UI, Rilo can use it. Rilo uses invite flows and secure credential submission — it never requests OAuth redirects during task execution.

Credential Setup Methods

Best for: Tools that support email invites — Slack workspaces, GitHub organizations, and most SaaS apps.
  1. From the tool’s admin settings, send an invite to Rilo’s dedicated email: rilo@<your-company>.mail.riloworks.com
  2. Rilo receives the invite and self-registers into your workspace or organization
  3. No credentials need to be shared — Rilo manages its own account
This is the simplest setup path and the most common for team-based SaaS tools.
Best for: Tools that require an account to be created before an invite can be sent, or tools where you want direct control over the account.
  1. Create an account in the tool using Rilo’s email address: rilo@<your-company>.mail.riloworks.com
  2. Navigate to the Credentials section in your customer portal
  3. Select the tool you want to connect
  4. Fill in the required fields (username/password, API key, or SSO details)
  5. Credentials are encrypted and stored securely — Rilo’s team never sees plaintext values
Never share credentials via Slack messages or email. Always use the secure credential portal.
Best for: Standalone accounts or tools with organization management (e.g., GitHub, independent SaaS accounts).
  1. Rilo self-registers an account using your organization’s dedicated Rilo email address
  2. You invite the Rilo account into your organization or workspace from the tool’s admin settings
  3. Rilo’s account is then available for task execution within your org context
This method is common for developer tools and platforms where org membership is managed separately from account creation.

Browser Session Isolation

Each organization’s browser sessions are fully isolated. Rilo never reuses browser sessions across organizations — each task gets a fresh, sandboxed browser environment.

What’s Next