HYBRID-CHAINDEVELOPERS
DOCUMENTATIONv2
POST

Automations

Create automation

/api/v2/automations
AUTHENTICATIONBearer token · automations:writeAUTHORITATIVE OWNERautomation-serviceCONTRACT AUTHORITYCapability registry · plannedSTATUSPlanned · not executable
PLANNING CONTRACT · NOT CALLABLE

This page describes intended capability and integration boundaries so people and agents can prepare safely. Do not send this request or register it as an executable tool. Wait until the capability registry marks it implemented-contract, then re-fetch the deployed OpenAPI document and build the request from that machine contract.

PURPOSE + BUSINESS CONTEXT

Planned capability: create an automation with explicit trigger, action, callback, and policy boundaries.

WHEN THIS CALL IS USEFUL

Do not call or register this operation as an executable agent tool yet. Use this page to plan the future automation workflow; enable it only after the status becomes implemented-contract and the exact operation appears in deployed OpenAPI.

OUTCOME · Planned · Create or advance

What changes

None today: this route is not executable. Its intended behavior is: when promoted, creates configuration and evidence only. The automation remains DRAFT, admits no trigger, stores no reusable domain credential, and authorizes no underlying action.

WHY IT MATTERS

  • Lets people and agents prepare for automation without falsely presenting roadmap scope as a live capability.
  • Gives people and agents a contract-backed way to advance automation.
  • Makes triggers, execution attempts, callback destinations, delivery evidence, and retry behavior explicit without granting the automation ambient access to another domain.

ISOLATION + AUTHORITY

Tenant, workspace, automation definition, trigger, run, callback endpoint, secret version, delivery attempt, receipt, retry policy, and target-domain authority remain distinct. Creating or running an automation does not bypass the authorization, idempotency, policy, or lifecycle gates of any action it requests. This planning record grants no runtime authority, and only deployed OpenAPI can define an executable public contract.

BEFORE YOU CALL

  • First confirm that this operation is marked implemented-contract and exists in the currently deployed OpenAPI document; until then, no production request is valid.
  • Its capability-registry profile is provisional integration guidance, not an executable request schema.
  • Authenticate at the documented boundary: bearer+scope.
  • Treat the proposed name (body), trigger (body), action_profile_id (body), execution_policy (body), step_up_token (body) as planning input only; re-generate the request from deployed OpenAPI before making a call.
  • Use one Idempotency-Key only for retries of the same byte-equivalent logical mutation.

WHAT TO DO NEXT

  • Keep this operation disabled in clients, agents, SDKs, and workflow automation while it remains planned-contract.
  • Use the stated owner, lifecycle, authority boundary, and provisional automation profile to prepare requirements and conformance tests without sending a request.
  • Monitor the capability registry for implemented-contract, then re-fetch deployed OpenAPI and validate its exact security, parameters, schemas, responses, and agent metadata before enabling the integration.

AGENT GUIDANCE

  • Never call this planned contract, include it in an executable tool registry, or infer runtime availability from this readable page.
  • Its capability-registry profile is provisional integration guidance, not an executable request schema.
  • Use automation only for the purpose and lifecycle stage described by this operation; do not treat it as authority for an adjacent action.
  • Treat the proposed name (body), trigger (body), action_profile_id (body), execution_policy (body), step_up_token (body) as planning input only; re-generate the request from deployed OpenAPI before making a call.
  • Distinguish definition state, enablement, trigger admission, run creation, execution outcome, callback delivery, receipt, retry, and the authoritative state of any referenced business resource.
  • After a timeout or conflict, read authoritative state before deciding whether an equivalent retry is safe.
  • When implementation lands, discard generated requests based on this planning record and rebuild them from the deployed OpenAPI operation.
MACHINE CONTRACT

This operation is a non-executable planning contract. Its capability-registry record defines the intended owner, parameters, responses, and integration boundary until an implemented Rust OpenAPI operation replaces it.

EXTENDED INTEGRATION GUIDANCE

Readable request and response reference

Examples describe the reviewed planning contract and remain non-executable until promoted into OpenAPI.

PARAMETERS

Headers, path, query, and body

NAMELOCATIONPRESENCETYPE / RULES / PURPOSE
AuthorizationheaderRequired

Bearer tokenCredential containing automations:write authority.EXAMPLEBearer hc_live_…

Idempotency-KeyheaderRequired

ASCII string · 1–128Caller-generated stable key reused for retries of the same logical mutation.EXAMPLEpost-api-v2-automations-request-001

namebodyRequired

string · 2–120Workspace-visible automation name; it is presentation metadata, not an authority key.EXAMPLEInvoice evidence follow-up

descriptionbodyOptional

string · max 500Non-secret business purpose and operator context.EXAMPLERequest document review after an invoice evidence event.

triggerbodyRequired

discriminated objectExactly one MANUAL, SCHEDULE, or EVENT trigger. Schedule triggers require a bounded cadence and timezone; event triggers require an allowlisted topic and typed filters.EXAMPLE[object Object]

action_profile_idbodyRequired

server-owned action profile identifierApproved action class resolved from the automation catalog. Arbitrary URLs, code, API paths, scopes, or shell commands are rejected.EXAMPLErequest-document-review

input_bindingsbodyOptional

allowlisted binding objectTyped mappings from trigger fields or constants into the approved action profile; secrets and executable expressions are forbidden.EXAMPLE[object Object]

callback_endpoint_uuidbodyOptional

32-character identifier | nullOptional active workspace-owned callback endpoint for signed outcome delivery. Null means no callback.EXAMPLE9128ab9dc2d64d85a0123613fce29afd

execution_policybodyRequired

bounded policy objectConcurrency, timeout, retry, deduplication, and failure posture within platform limits; it cannot weaken the underlying domain policy.EXAMPLE[object Object]

step_up_tokenbodyRequired

purpose-bound tokenFresh AUTOMATION_CONFIGURATION authorization bound to the workspace and configuration commitment.EXAMPLEhcsu_…

REQUEST

JSON body example

{
  "name": "Invoice evidence follow-up",
  "description": "Request document review after an invoice evidence event.",
  "trigger": {
    "type": "EVENT",
    "topic": "invoice.evidence.received",
    "filters": {
      "status": "ACCEPTED"
    }
  },
  "action_profile_id": "request-document-review",
  "input_bindings": {
    "evidence_reference": "$.event.reference"
  },
  "callback_endpoint_uuid": "9128ab9dc2d64d85a0123613fce29afd",
  "execution_policy": {
    "max_concurrency": 1,
    "timeout_seconds": 30,
    "max_attempts": 3,
    "deduplication_window_seconds": 3600
  },
  "step_up_token": "hcsu_…"
}

RESPONSES

Status and payload examples

201A DRAFT automation revision and immutable configuration commitment returned; no trigger is active and no domain action is authorized.Not executable · JSON RESPONSE+
{
  "result": "See the operation's authoritative OpenAPI response schema."
}
INTEGRATION DECISION
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from the future automation definition, trigger, schedule, run, action, and retained receipt lifecycle through an implemented operation.
ESCALATE WHEN
Escalate readiness questions rather than approximating a planned automation with ungoverned repeated calls.
400A typed field, version, reason, step-up token, request signature, or idempotency key is malformed.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "A typed field, version, reason, step-up token, request signature, or idempotency key is malformed."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from the future automation definition, trigger, schedule, run, action, and retained receipt lifecycle through an implemented operation.
ESCALATE WHEN
Escalate readiness questions rather than approximating a planned automation with ungoverned repeated calls.
401The bearer credential is missing, expired, or invalid.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "The bearer credential is missing, expired, or invalid."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from the future automation definition, trigger, schedule, run, action, and retained receipt lifecycle through an implemented operation.
ESCALATE WHEN
Escalate readiness questions rather than approximating a planned automation with ungoverned repeated calls.
403The principal lacks automations:write, workspace ownership, fresh configuration authority, or the underlying action-specific authority required for execution.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "The principal lacks automations:write, workspace ownership, fresh configuration authority, or the underlying action-specific authority required for execution."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from the future automation definition, trigger, schedule, run, action, and retained receipt lifecycle through an implemented operation.
ESCALATE WHEN
Escalate readiness questions rather than approximating a planned automation with ungoverned repeated calls.
404The automation, endpoint, delivery, action profile, or referenced owner-scoped resource does not exist in the authenticated workspace.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "The automation, endpoint, delivery, action profile, or referenced owner-scoped resource does not exist in the authenticated workspace."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from the future automation definition, trigger, schedule, run, action, and retained receipt lifecycle through an implemented operation.
ESCALATE WHEN
Escalate readiness questions rather than approximating a planned automation with ungoverned repeated calls.
409The expected version, lifecycle, endpoint key epoch, delivery eligibility, deduplication state, or Idempotency-Key conflicts.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "The expected version, lifecycle, endpoint key epoch, delivery eligibility, deduplication state, or Idempotency-Key conflicts."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from the future automation definition, trigger, schedule, run, action, and retained receipt lifecycle through an implemented operation.
ESCALATE WHEN
Escalate readiness questions rather than approximating a planned automation with ungoverned repeated calls.
422Trigger, action profile, input binding, callback, retry, SSRF, secret-safety, concurrency, schedule, event, or domain policy rejected the request.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "Trigger, action profile, input binding, callback, retry, SSRF, secret-safety, concurrency, schedule, event, or domain policy rejected the request."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from the future automation definition, trigger, schedule, run, action, and retained receipt lifecycle through an implemented operation.
ESCALATE WHEN
Escalate readiness questions rather than approximating a planned automation with ungoverned repeated calls.
503Automation orchestration, endpoint delivery, Identity, policy, evidence, or the owning domain is unavailable; no unverified transition is inferred.Not executable · JSON RESPONSE+
{
  "code": "request_failed",
  "message": "Automation orchestration, endpoint delivery, Identity, policy, evidence, or the owning domain is unavailable; no unverified transition is inferred."
}
INTEGRATION DECISIONrequest_failed
CALLER ACTION
Do not send this request or register it as an executable agent tool. Use the implemented alternatives linked by the module guide.
RETRY SAFETY
Do not retry on a timer. Re-fetch production OpenAPI and proceed only after this exact operation appears there.
STATE RECONCILIATION
No runtime state exists to reconcile for this planning contract. Continue from the future automation definition, trigger, schedule, run, action, and retained receipt lifecycle through an implemented operation.
ESCALATE WHEN
Escalate readiness questions rather than approximating a planned automation with ungoverned repeated calls.

OPERATIONAL NOTES

Security and lifecycle guarantees

  • The Rust gateway validates the public contract and routes only to the authoritative owner; clients never address internal services directly.
  • Mutations are retry-safe only when the same Idempotency-Key and canonical request body are reused.
DOCUMENTATION STATUS

This planned contract now defines its public parameters, authorization boundary, replay behavior, responses, and authoritative owner. It remains non-executable until its owner adapter and conformance tests are promoted into the Rust gateway.

Return to the V2 directory ↗