Developer Overview

AI Editor Integration (MCP)

AI Editor Integration (MCP)

Glow implements the Model Context Protocol  for users with an Admin, Manager, or Member role. Click Connect AI tool in the Workflow Assistant header or open Your account → MCP to connect via OAuth 2.1 or a personal token.

• Direct building & live companion canvas: Query component schemas in batches and apply atomic edits through update_workflow. An open Glow tab follows and frames your changes automatically.
• In-chat account handoff: When a Step needs an app connection, get_connections returns a direct connectUrl (?source=mcp&connectStep=<n>) that opens that Step’s connection dialog.
• Run traces & version checkpoints: Inspect past runs and traces (list_workflow_executions, get_workflow_execution) and list or save revision checkpoints (list_workflow_versions, save_workflow_version).
• Testing: Run single-Step (test_step) or whole-automation (run_workflow_test) tests with their dedicated execution grants; see Testing Automations with MCP.

Follow Connecting AI Apps & Editors to connect your client, then use the MCP Tool Reference to build and validate.

Custom Python Logic

Custom Python Logic

When visual steps do not cover your transformations or business rules, insert a Code editor Step:

• Python execution: Run scripts for calculations, transformations, and validation. See Code editor for runtime details and limits.
• Data packages included: Use numpy and pandas out of the box without package installation.
• Typed references: Upstream data arrives as native Python objects (dict, list, int) rather than raw string interpolations.
• Real-time diagnostics: The editor underlines unclosed brackets and syntax errors as you type.

Replace the sample values below with upstream references once you confirm their output shape:

import json
 
order_items = [{"price": 100.0}, {"price": 50.0}]
customer_tier = "enterprise"
 
total_discount = sum(
    item["price"] * 0.15
    for item in order_items
    if customer_tier == "enterprise"
)
 
# The final line must be JSON for downstream structured output.
print(json.dumps({"discount_applied": total_discount}))

If this Code editor is Step 3, downstream Steps read {{ 3.result.output.discount_applied }}. See the Code Editor Guide for reference syntax.

Inbound & Outbound APIs

Inbound & Outbound APIs

Connect Glow to your microservices and web services:

• Webhook triggers: Send events to the URL copied from your Webhook Step. A 202 Accepted response confirms receipt, not run completion.
• Correlation IDs: Send x-glow-correlation-id as an HTTP request header rather than inside the JSON body.
• Execution queries: Query /api/v1/flows/{flowId}/executions with both x-glow-api-key and the matching x-glow-correlation-id header.
• Outbound HTTP requests: Configure custom auth (Bearer, Basic, API Key), query parameters, and request bodies.

Set GLOW_WEBHOOK_URL to your Webhook Step’s URL and publish the automation before sending requests. If webhook signature verification is enabled, include the required signature header and keep the webhook URL secret:

curl -X POST "$GLOW_WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -H "x-glow-correlation-id: req_982347abc" \
  -d '{
    "event": "deployment_succeeded",
    "commit": "4e64b03",
    "author": "[email protected]"
  }'

Review REST API & Webhooks for authentication and query parameters.