تخطَّ إلى المحتوى الرئيسي

سير العمل

سير العمل أتمتة يجريها المنتج نيابة عنك: مشغل ورسم من الخطوات وتشغيلات تتقدم مع وصول الأحداث. المسودة والنشر منفصلان، فما تنفذه الحركة دائما إصدار شحنه شخص عن قصد.

At a glance

Shape
A trigger, a graph of steps, published versions
Triggers
Manual fire, or a cohort signal
Operate
fireWorkflow, signalWorkflow, cancelWorkflow
Live updates
workflow.run on the project room
Auth
Access token; runs execute server-side
  • المشغلات إطلاق يدوي أو إشارة مجموعة، فيكون «من» مجموعة لا شرطا مكتوبا يدويا.
  • تغطي الخطوات الإجراءات والتأخيرات والتفرعات والقفزات المحروسة؛ والرسم الذي سيرفضه المحرك يُسمى قبل النشر.
  • كل تشغيل يحتفظ بسببه: الانتظار يسمي إشارته، والفشل يحمل خطأه.

كيف يعمل

A definition holds a draft graph and its published versions. The draft is edited freely and saved as it changes; publishing validates the graph and makes that version the one runs execute, so an edit in progress can never leak into traffic. A run advances node by node: actions do work, delays hold, branches choose a case or the otherwise, and a waiting node parks the run until its named signal arrives, from the product or by hand. Runs, their steps and their errors are all kept, which is what the console's runs tab and the Home screen's Needs you list read.

كيفية الوصول إليه

SurfaceOperation
RESTNone: workflows are authored and operated, not ingested
GraphQLworkflowDefinitions, workflowRuns queries · publishWorkflowVersion, fireWorkflow, signalWorkflow, cancelWorkflow mutations
Realtimeworkflow.run on the project room, as a run advances
MCPprodantix.workflows.list

مثال

Bash
curl "https://api.prodantix.com/graphql" \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "mutation ($p: String!, $d: String!) { fireWorkflow(projectId: $p, definitionId: $d) { runId } }",
    "variables": { "p": "'$PROJECT_ID'", "d": "'$DEFINITION_ID'" }
  }'