Setyenv · Docs
  • English
  • Spanish
  • Chinese
  • Japanese
  • Arabic
  • German
  • French
  • Hindi
  • Indonesian
  • Italian
  • Dutch
  • Portuguese
  • Russian
  • Turkish

Management integration nodes

WP-PFWorkflow can call out to other systems, expose its own inbound endpoints, and read/write Management records — using integrations you define in WP-PFManagement and run in Workflow. See the concept page Define in Management, run in Workflow for the rationale; this section is the practical surface.

Four building blocks, each a node family in the Workflow editor:

  • REST Message — an outbound HTTP call defined once in Management, invoked as a node. (wp-pfworkflow/nodes/rest-message)
  • Scripted REST route — an inbound endpoint that triggers a workflow or returns entity data. (wp-pfworkflow/nodes/scripted-rest)
  • Table nodes — per-entity Get / Create / Update / … nodes for Management records. (wp-pfworkflow/nodes/table-nodes)
  • OAuth outbound — authenticated connections whose tokens live in Management. (wp-pfworkflow/nodes/oauth)

All four resolve their definition Management-first, with a local fallback so a workflow keeps running while Management is being adopted. All four inherit the Workflow engine (queue, retry, replay, timeline) and, where they touch records, the inherited moat.