Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »


The Principles of Actionflows

  • Only map in the minimal amount of data, e.g., primary key, which is then used to access the remaining data.
  • All Actionflows require an input, such as data, user interaction, scheduled task or API call.


  • Only map in the minimal amount of data, e.g., primary key, which is then used to access the remaining data.

  • All Actionflows require an input, such as data, user interaction, scheduled task or API call.

  • Action nodes receive data as Input Parameters and return data to the Actionflow as Output Attributes.

  • To use data within an action node it must be mapped in.

  • Data not mapped into an action node will pass through and is available at later points in the Actionflow.

  • Reuse Actionflows by connecting in different inputs. Each reuse is referred to as an instance.



  • No labels