Automations

Overview

Automations is a live workflow runner for Umney Connect. Create workflows with triggers and skill steps, set active=true, then run them manually, on a schedule, on Live Chat events, or from third-party webhooks. Create an Automations token with automations:manage.

Get started

1. Enable Automations in Dashboard → Billing. Enable other products your skills need (AI Agent, Business Email, Marketing, Live Chat).
2. Dashboard → Developers → create token → product Automations → automations:manage.
3. POST /v1/automations/workflows with triggerJson, stepsJson, active:true.
4. POST /v1/automations/workflows/{id}/run with optional context from your third-party system.
5. GET /v1/automations/runs/{runId} until status is succeeded or failed.

API tokens

Authorization: Bearer umk_live_automations_<prefix>_<secret>
API base: https://umneyconnect.com/api

Concepts

Triggers

{
  "schemaVersion": 1,
  "type": "schedule",
  "schedule": { "kind": "cron", "cron": "0 9 * * 1-5" }
}

{
  "schemaVersion": 1,
  "type": "event",
  "event": { "type": "conversation.created" }
}

{
  "schemaVersion": 1,
  "type": "schedule",
  "schedule": { "kind": "interval", "everySeconds": 900 }
}

{
  "schemaVersion": 1,
  "type": "webhook",
  "webhook": { "token": "replace-with-long-secret-min-16-chars" }
}

Skills (live)

Channel inbound requires config_json.inboundSecret (min 16). channel.deliver supports slack, telegram, whatsapp, webhook, and email (via Business Email).

Step types: skill | deliver | log | agent (tool-calling loop) | approval (pause for human). Agent steps use TOOL_CALL:skillId|{json} / FINAL:text.

[
  {
    "type": "skill",
    "skillId": "ai.invoke",
    "input": {
      "input": "Summarize this lead for the agent",
      "context": "{{context}}"
    }
  },
  {
    "type": "skill",
    "skillId": "webhook.deliver",
    "input": {
      "url": "https://partner.example.com/hooks/umney",
      "body": { "summary": "{{last.outputText}}", "payload": "{{payload}}" }
    }
  }
]

Third-party systems

Same model as AI Agent: Connect never crawls external systems. Your Nest Safety, CRM, ERP, or custom backend authenticates to those systems, then injects knowledge into Automations.

1. Fetch third-party data with that system's API credentials (never store them in Connect unless you choose to).
2. Call POST /v1/automations/workflows/{id}/run with { context: "…", payload: { … } } using your Automations token.
3. Or POST /v1/automations/hooks/inbound with workflowId + context, using the Automations token or X-Umney-Automation-Token matching trigger_json.webhook.token.
4. Reference injected fields in skill inputs via {{context}} / {{payload.*}}.
5. Push results back out with webhook.deliver to any https endpoint.

curl -X POST "https://umneyconnect.com/api/v1/automations/hooks/inbound" \
  -H "Authorization: Bearer $AUTOMATIONS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "workflowId": "YOUR_WORKFLOW_UUID",
    "event": "nest.case.updated",
    "context": "Case #441 status=open priority=high customer=Acme",
    "payload": { "caseId": "441", "priority": "high" },
    "idempotencyKey": "nest-441-open"
  }'

Public Automations API (token — live)

curl -X POST "https://umneyconnect.com/api/v1/automations/workflows" \
  -H "Authorization: Bearer $AUTOMATIONS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Lead enrich",
    "active": true,
    "triggerJson": { "schemaVersion": 1, "type": "manual" },
    "stepsJson": [
      { "type": "skill", "skillId": "ai.invoke", "input": { "input": "Draft a follow-up", "context": "{{context}}" } },
      { "type": "skill", "skillId": "log.write", "input": { "message": "{{last.outputText}}" } }
    ]
  }'

curl -X POST "https://umneyconnect.com/api/v1/automations/workflows/{id}/run" \
  -H "Authorization: Bearer $AUTOMATIONS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "context": "Lead from Nest: priority high", "payload": { "leadId": "99" } }'

Dashboard Growth API (JWT — live)

Dashboard → Automations is the Control UI (chat/sessions/runs/approvals/agents/SLO).

Errors

• 403 — Automations (or skill product) not entitled / wrong token
• 401 — inbound webhook token mismatch
• 400 — inactive workflow, empty steps, missing skill input
• 404 — workflow/run not found
• 502 — skill failed (e.g. email provider / partner webhook)

Agent recipe

1. Enable Automations (+ skill products) → mint automations:manage token.
2. Create active workflow with real skills — not empty steps.
3. Inject third-party knowledge via context; deliver out via webhook.deliver.
4. Poll GET /v1/automations/runs/{id} for status and stepsResultJson.
5. Do not invent shell/browser skills or claim Connect crawls partner APIs.

Related services

• AI Agent — ai.invoke skill + /v1/ai/runs
• Business Email — email.send skill
• Marketing — marketing.campaign_send skill
• Live Chat — event triggers + chat.post_message