Overview
Automated activities execute system actions without creating user tasks. They are configured via Automation Flows and can trigger external integrations (Power Automate) or built-in actions (ProcessPro Automate).
Quick Steps
Power Automate — Send Payload
An activity is configured with an Automation Flow: Engine=Power Automate, Type=Send Payload.
When the workflow reaches this activity, an outbound HTTP POST is sent to the configured endpoint.
The payload includes submission context, process metadata, and workflow details.
If the endpoint returns a transient failure (429, 500, timeout), the system retries per configuration.
Each attempt is logged in the audit trail with payload/response metadata.
Permanent failures are surfaced as workflow errors.
ProcessPro Automate — Built-in Actions
ProcessPro Automate actions run without external calls.
Examples include Save Managed Document, which generates a PDF and saves it under a configured Managed Document Type.
The action completes automatically and leaves an audit entry with actor=system.
Configuration
Automation Flows are configured in the company settings. Each flow requires:
Engine — Power Automate or ProcessPro Automate
Flow Type — determines the action (Send Payload, Save Managed Document, etc.)
Configuration JSON — flow-specific settings (endpoint URL, document type, etc.)
Important: The engine and flow type must be compatible. For example, Send Payload requires Power Automate, while Approve By Role requires ProcessPro Workflow. Mismatched combinations are rejected during configuration.