Codika icon

Codika

Interact with Codika platform - initialize executions, submit results, upload files, handle errors, and manage data ingestion.

Actions6

Initialize Execution → Init Workflow

AI-generated

Summary

Initialize a Codika workflow execution by either extracting execution metadata from an HTTP trigger payload or, for non-HTTP triggers, sending required identification and trigger information to Codika's API to obtain execution authentication details.

Inputs

  • Member Secret — Required for non-HTTP triggers to authenticate execution; use placeholder {{MEMSECRT_EXECUTION_AUTH_TRCESMEM}}.
  • Organization ID — Required for non-HTTP triggers; the Codika organization ID, e.g., use placeholder {{USERDATA_ORGANIZATION_ID_ATADRESU}}.
  • User ID — Required for non-HTTP triggers; the Codika user ID, e.g., use placeholder {{USERDATA_USER_ID_ATADRESU}}.
  • Process Instance ID — Required for non-HTTP triggers; Codika process instance ID, e.g., use placeholder {{USERDATA_PROCESS_INSTANCE_UID_ATADRESU}}.
  • Workflow ID — Required for non-HTTP triggers; the workflow template identifier.
  • Trigger Type — Required for non-HTTP triggers; the type of trigger that initiated the workflow (e.g., gmail, calendly, schedule).

Output shape

a single record

Returns an object containing executionId, executionSecret, callbackUrl, errorCallbackUrl, processId, processInstanceId, userId, workflowId, start time, and mode. For HTTP trigger workflows, these values are extracted from the webhook payload's executionMetadata; for non-HTTP triggers, they are obtained from Codika's API response after sending the required parameters. The operation stores executionId and executionSecret in the execution context for use by downstream nodes.

Examples

Example 1: HTTP trigger with executionMetadata in payload

No parameters needed; workflow input must contain executionMetadata with executionId, executionSecret, and callbackUrl fields; the node extracts and saves these for subsequent use.

Example 2: Non-HTTP trigger such as schedule or service trigger

Set Member Secret, Organization ID, User ID, Process Instance ID, Workflow ID, and Trigger Type parameters appropriately. The node sends these to Codika to initialize execution and obtains authentication details.

Links

Discussion