Skip to main content
The Automations is RelayHub’s workflow automation engine. It lets you build flows that connect triggers (webhooks, schedules, chat) to actions (external services, AI steps, chat messages, skills) without writing code.
Not sure where to start? The Automation Wizard builds an automation for you from a plain-language description, right inside Automations. Use the Build with the Wizard tab.

​
Accessing Automations

Click Automations in the left sidebar. The hub page lists your flows as cards showing each flow’s name, trigger type, step count, status badge (Active or Inactive), and last update. Admins see all flows grouped by owner; everyone else sees their own.
Automations access is on by default for all users, but your administrator can disable it per user. If you do not see it in your sidebar, contact your admin.

​
Creating a Flow

Flows are built in the visual automation editor.
1

Open the editor

Click Open Editor in Automations header. The flow builder opens in a new tab, already signed in with your RelayHub context.
2

Choose a trigger

Every flow starts with a trigger: a webhook that accepts HTTP requests, a schedule, or another supported trigger type.
3

Add steps

Chain steps after the trigger. The step catalog includes hundreds of external services (Slack, Salesforce, HubSpot, Gmail, Stripe, and more) plus RelayHub-specific steps:
  • RelayHub Chat: Create posts a message into a user’s RelayHub chat
  • RelayHub Workspace Chat: Create posts into a workspace conversation
  • Skill: Run triggers one of your RelayHub skills from the flow
Each step can reference data from the trigger or from earlier steps.
4

Publish

Click Publish in the editor. The flow goes Active and appears back in Automations (use the refresh button if needed).

​
Triggering Flows from Chat

The settings icon on a flow card opens the Trigger Configuration modal. This is what lets the AI run your flow from a conversation:
  • Description: tells the AI what the flow does so it knows when to use it
  • Parameters: the inputs the flow accepts, each with a name, type, and AI-facing description. Parameters can auto-inject context like the current conversation ID, user ID, email, or workspace ID
  • Synchronous mode: off by default (fire and forget). Turn it on if the flow has a Return Response step and chat should wait for the result
  • Quick start presets fill in common parameter sets, like “user query + round-trip”
Once configured, just ask in chat: “Run the daily report workflow now” or “Show me my active automations.” The AI lists, triggers, and checks the status of flows on your behalf.

​
Triggering Flows from Outside

Every published flow with a webhook trigger has a URL external systems can call:
  • Send a JSON body; it is available inside the flow as trigger data
  • The call returns immediately by default; in synchronous mode it waits (up to 30 seconds) and returns the flow’s response
  • The flow ID acts as the secret, so treat the URL like a credential
Click the ? icon in Automations header for your instance’s exact webhook base URL and a copy-paste example.
Anyone with a flow’s webhook URL can trigger it. Do not share webhook URLs with untrusted parties, and rotate the flow if a URL leaks.

​
Monitoring Runs

Open a flow in the editor to view its run history: the trigger payload, each step’s input and output, status, and duration. Failed steps show the exact error, which is usually an incorrect URL, an authentication failure on an external service, or a malformed body.

​
Automation to Chat

Flows can push results back into RelayHub using the chat steps above. Common patterns:
  • A morning schedule queries your CRM and posts a lead summary into a team workspace
  • A monitoring system calls a webhook flow that relays alerts into a RelayHub conversation
  • A pipeline ingests documents and notifies the team when analysis completes

​
Next Steps

  • Automation Wizard — Build and change automations by describing them in plain language
  • Schedules — Run flows and skills on a recurring schedule
  • Skills — Build the skills your flows can run
  • Files — See how ingested files are managed