Workflow and Service Hook Execution Throttling

The Conga Platform now automatically limits how often workflows and service hooks can run on the same record in a short period. This protects your organization from runaway automations and keeps the platform fast and reliable. In cases of excessive automation activity, the system will quietly pause the extra runs to keep everything running smoothly.

API Key Authentication Support for External Endpoint Configuration

The External Endpoint Auth Credentials API services now supports API key authentication for external integrations, alongside existing authentication methods. Administrators can create, update, and retrieve API key–based credentials, validate required fields such as key name and key value, and receive clear error messages for missing, duplicate, or unsupported authentication types.

Enhanced Get Record Activity Output Handling

You can now use the output of the Get Record activity as a Record datatype in subsequent workflow steps. You can access specific field values from the retrieved record and use them in assignments, updates, conditions, and more without any manual conversion. This simplifies passing record data between activities, mapping record attributes to workflow variables, and building workflow logic based on record values. For more details, see Get Records activity.

Skip Delete Sync UI Warning

Display a warning message when users enable or disable the Skip Delete Sync setting to explain how it affects deleted Salesforce records during synchronization. The following warnings appear based on the setting state:

• Disabled: Deleted records in Salesforce will be removed from <Object Name> object on platform on the next sync. Ensure delete tracking is enabled for this object in Salesforce.
• Enabled: Deleted Salesforce records will no longer be removed from <Object Name> object on platform during sync.

Scheduled Data Sync User Context Preservation

Scheduled data sync always runs in the context of the user who originally created the schedule. This behavior remains unchanged even if other users update Salesforce settings, platform configurations, or modify the schedule. Each schedule continues to use its original user context, ensuring consistent execution and reducing permission-related sync failures.