Final Actions

Introduction

Final Actions extend Campaign Audience Builder beyond its built-in Campaign, Account Engagement, and Marketing Cloud destinations. Administrators and developers can pass audience results to an Autolaunched Flow or custom Apex class to update records, create related records, call another service, or run organization-specific processing.

Flow integration

Use an Autolaunched Flow when the action can be built and maintained in Flow Builder. CAB passes the configured audience results and input values to the Flow.

See Flow Integration for an example.

Apex integration

Use an Apex Final Action for custom logic that requires code.

For every new Apex Final Action, implement lb.FinalAction_ManagedAsync_Interface. Your class provides one runSync method, while CAB owns asynchronous batching, audience-scope loading, and applicable completion notifications. This is the recommended heap-safe path for large audiences.

lb.FinalAction_Interface is the legacy alternative. Use it only when you explicitly need maximum control over async orchestration and are prepared to own record loading, batching or Queueable chaining, retries, limits, and notifications. It remains supported for backward compatibility, but its query-locator helper is not safe for large cache-backed audiences.

See Apex Integration for the managed interface example, execution contract, setup instructions, and legacy migration guidance.