Skip to content

Workflow Connectors: Automate Actions Across Your Enterprise

A data platform that only shows you what happened in the past is useful. A platform that tells you what is happening right now is powerful. But a platform that can automatically trigger an action in another system based on what is happening right now—that is transformative. Most organizations suffer from informational latency; a critical event occurs, but by the time the right person sees it on a dashboard, it's too late to act.

Arkham's Workflow Connectors are engineered to eliminate this latency. This feature acts as the central nervous system for your digital twin, allowing you to configure simple, powerful rules that connect events within the Arkham platform to actions in the external applications your teams rely on. From sending a Slack alert when a data pipeline fails to creating a Salesforce task when a new high-value customer is identified, Workflow Connectors bridge the gap between insight and immediate, automated action.

How It Works: If This, Then That, for Your Enterprise

Workflow Connectors allow you to build event-driven automations through a simple, UI-based configuration. You define a trigger based on an event in your Ontology, and then specify the action to take in a connected third-party service.

graph TD
    subgraph "Arkham Platform: The Trigger"
        A[Ontology Event]
        A_Desc["e.g., Data Pipeline Fails,New Object Created,Metric Exceeds Threshold"]
        A --> A_Desc
    end

    subgraph "Workflow Connector Service"
        B{Rule Engine: IF Trigger -> THEN Action}
    end

    subgraph "External Systems: The Action"
        C(Slack Alert)
        D(Microsoft Teams Message)
        E(PagerDuty Incident)
        F(Custom Webhook)
    end

    A -- "Fires" --> B
    B -- "Executes Action" --> C
    B -- "Executes Action" --> D
    B -- "Executes Action" --> E
    B -- "Executes Action" --> F

    style A fill:#A9DFBF,stroke:#333,stroke-width:2px,color:#000
    style B fill:#FAD7A0,stroke:#333,stroke-width:2px,color:#000
    style C fill:#D6EAF8,stroke:#333,stroke-width:1px,color:#000
Press "Alt" / "Option" to enable Pan & Zoom

The configuration is code-free: 1. Select the Trigger: In the Ontology Manager, choose the event you want to monitor. This can be a dataset update, the creation of a new object, or a metric crossing a defined threshold. 2. Choose the Connector: Select the target application from our library of pre-built connectors (e.g., Slack, PagerDuty, Microsoft Teams). 3. Configure the Message: Customize the payload. You can dynamically insert properties from the triggering Ontology object directly into your message, providing rich context for the recipient. For example, Alert: Pipeline {{pipeline_name}} failed at {{timestamp}}.

Use Cases for Every Team

Workflow Connectors are a versatile tool used by technical and business teams to improve operational awareness and automate routine tasks.

  • Problem: A data engineer needs to know immediately when a critical production pipeline fails so they can begin debugging.
  • Workflow:
    • Trigger: On a pipeline status change to FAILED for any pipeline in the production Project.
    • Action: Send a message to the #data-ops-alerts Slack channel and create a high-priority incident in PagerDuty.
  • Result: The on-call engineer is notified within seconds of the failure, dramatically reducing mean time to resolution (MTTR).
  • Problem: A sales manager wants to be alerted when a new Customer object is created with a predicted_ltv (Lifetime Value) over $50,000.
  • Workflow:
    • Trigger: On the creation of a new @Customer object where predicted_ltv > 50000.
    • Action: Send a message to the #major-accounts Microsoft Teams channel with the customer's name and key details.
  • Result: The sales team can immediately engage with high-potential new leads, ensuring no major opportunity is missed.
  • Problem: An inventory manager needs to know when the stock_level property of any @Warehouse object drops below the safety_stock_level.
  • Workflow:
    • Trigger: On an update to any @Warehouse object where stock_level < safety_stock_level.
    • Action: Call a custom webhook that triggers a re-order process in their external ERP system.
  • Result: Inventory is managed proactively and automatically, preventing stockouts and reducing the need for manual monitoring.

Key Features

  • Code-Free Configuration: Build powerful automations through a simple, intuitive UI with no coding required.
  • Rich, Dynamic Payloads: Embed data directly from your Ontology objects into notification messages to provide immediate, actionable context.
  • Extensible Library: Leverage a growing library of pre-built connectors for popular business tools. For custom needs, use the generic webhook connector to integrate with any system that can receive a POST request.
  • Audited and Governed: Every workflow execution is logged and auditable, providing a clear trail of all automated actions originating from the platform.
  • Ontology: The source of all events, objects, and metrics that can be used to trigger automated workflows.
  • Pipeline Monitoring: Provides the real-time status updates on data pipelines that are often used as triggers for operational alerts.
  • Metric Store: The hub where custom business metrics are defined, which can then be used to trigger workflows when they cross critical thresholds.