Workflows security and privacy
Workflows often touch other services, so the sign-in details they use are kept separately from the workflow itself, and steps can wait for a person’s approval before continuing.
Credentials and variables
The Credentials tab on the Workflows page holds the sign-in details that workflow steps use to reach other services. Variables holds values you reuse across workflows. Keep credentials there rather than typing them into a step, so they aren’t visible to everyone who opens the workflow.
Human approval
A workflow can include an approval step. The run pauses at that step until a person approves or rejects it, then continues or stops.
Calls to outside services
Workflow steps that call web addresses can only reach public addresses on the internet. Requests to private or internal network addresses are refused.
Run history
Past runs, including what ran, when and the result, are kept for at least a period set by the organization’s plan, from 7 days on Free to 10 years on Enterprise. After that they may be removed. Runs that are still waiting, for example on an approval, are not removed this way. See Data retention.
Model training
The organization compliance settings include a switch for whether agent and automation runs help improve Syntic agents. See Model training and your chats.