Skip to main content

Workflow Automation

Workflows are the logical blueprints of Arrotech Hub. They define a sequence of "Atomic Steps" that transform data from one platform and push it to another.

The Anatomy of a Workflow​

A workflow consists of four primary components:

1. Triggers​

The event that starts the execution.

  • Manual: Triggered via the POST /workflows/{id}/execute API.
  • Scheduled: Managed by an Autonomous Agent.
  • Event-Driven: (Beta) Triggered by incoming webhooks or inbox notifications.

2. Atomic Steps​

Each step represents a single action performed by a tool.

  • Tool Selection: Every step maps to an MCP Tool.
  • Parameters: Configuration sent to the tool (e.g., channel_id, message_text).
  • Description: A human-readable intent for the AI to understand the step's purpose.

3. Dynamic Variables​

Arrotech uses a double-brace syntax {{step_n.field}} to pass data between steps. This allows you to:

  • Take a customer's email from a HubSpot step and use it in a Slack message.
  • Use a calculated value from a spreadsheet and post it to social media.

4. Conditional Branches​

Workflows can include logic gates. For example:

  • IF step_1.status is closed-won THEN Proceed to Step 2.
  • ELSE Stop execution.

Advanced Features​

  • Retry Policies: Configure how many times a step should retry on failure.
  • Timeouts: Ensure a workflow doesn't hang on slow external APIs.
  • Version Control: Track changes to your workflow logic over time.

API Integration​

Explore these endpoints in our API Reference: