Integration · Operations and Data

Connect Apache Pulsar events to Salesforce Agentforce

Apache Pulsar is the cloud-native, multi-tenant message streaming platform used by organisations building high-throughput, geo-distributed event-driven architectures — combining durable messaging, stream processing, and multi-tenant topic namespacing in a single system. For SaaS platforms and enterprise applications that use Pulsar as their event streaming backbone, the real-time event stream — subscription events, usage signals, processing milestones, error conditions — represents commercial intelligence that should flow into Salesforce. When a Pulsar topic carries signals about customer behaviour, account state changes, or platform health events, those signals should be available to Agentforce in real time rather than batched into a next-day report. When Emerge Digital connects Apache Pulsar to Agentforce, the real-time event stream from Pulsar is available to trigger Salesforce actions — and Salesforce commercial events can publish to Pulsar topics to coordinate downstream platform workflows.

All integrations

What this unlocks

Real-time customer behaviour signals from Pulsar trigger Salesforce actions: high-value usage events — a customer first activating a key feature, a usage threshold crossed, a processing job completing successfully for a major enterprise account — are published to Pulsar topics and can trigger Agentforce workflows: creating Salesforce tasks, updating health score fields, or notifying the account team in real time.
Multi-tenant event namespacing maps cleanly to Salesforce account structure: Pulsar's multi-tenant namespace model — tenant/namespace/topic — naturally maps customer-separated event streams to Salesforce accounts. An integration designed around Pulsar's namespace hierarchy can attribute events to the correct Salesforce account without a separate customer identifier lookup, leveraging the namespace isolation already built into the Pulsar architecture.
Geo-distributed platform events reach Salesforce from any region: Pulsar's geo-replication propagates events across data centres — an enterprise customer's event stream originating in an Asia-Pacific region reaches the Salesforce integration point through Pulsar's replication, ensuring global enterprise accounts receive the same real-time Agentforce treatment regardless of which region their data originates.
Salesforce commercial events publish to Pulsar for platform workflow coordination: when a Salesforce deal closes or a subscription tier changes, an Agentforce agent can publish an event to the appropriate Pulsar tenant namespace — triggering the platform's provisioning workflow, entitlement update, or billing system notification without a synchronous API call from the Salesforce side.

In the customer journey

Feature adoption event in Pulsar triggers account team expansion conversation

A SaaS platform publishes a feature_first_use event to a Pulsar topic when an enterprise customer activates a feature that correlates strongly with expansion revenue. The Agentforce integration consumes the event from the customer's namespace topic, identifies the Salesforce account, and creates a task for the account manager: the customer has activated the data export feature — the entry point to the enterprise tier. The account manager has the signal to start the expansion conversation before the customer is aware they need a plan upgrade.

Processing failure event creates customer-attributed service case

A data processing platform publishes a job_failed event to a Pulsar topic when a customer's processing job fails after the maximum retry threshold. The event includes the job identifier, the customer tenant namespace, and the failure reason. The Agentforce integration consumes the event, creates a Salesforce service case with the failure details attributed to the correct enterprise account, and assigns it to the on-call support team. The customer support case is created before the customer notices the failure and contacts support.

Subscription cancellation event in Pulsar triggers Salesforce churn workflow

A subscription management service publishes a subscription_cancelled event to a Pulsar topic when a customer initiates a cancellation. The Agentforce integration consumes the event, identifies the Salesforce account, and creates a Salesforce churn case with the cancellation reason from the event payload. The integration triggers a Salesforce flow that assigns a customer success manager, queues a retention call, and flags the account in the churn analysis report. The churn response workflow starts within seconds of the cancellation event.

Why not using Kafka rather than Pulsar for the Agentforce integration?

For organisations already using Apache Pulsar as their event streaming platform, integrating Agentforce through Pulsar is the natural choice — the events that matter commercially are already in Pulsar, and routing them to Salesforce through the existing event bus preserves the delivery guarantees and namespace isolation the architecture already provides. Organisations using Kafka would integrate through Kafka instead. The pattern — real-time event consumption into Agentforce, Salesforce events published to the message bus — is the same; Emerge builds to the streaming platform the organisation's architecture runs on.

Apache Pulsar's Agentforce integration is most valuable for SaaS and enterprise platform organisations that have adopted Pulsar as their primary event streaming infrastructure — where the commercial intelligence embedded in the real-time event stream should drive Salesforce actions, and where Pulsar's multi-tenant namespace model maps naturally to the Salesforce account hierarchy. It is the event streaming counterpart to the operational database integrations.

How Emerge integrates Apache Pulsar

Emerge Digital connects Apache Pulsar to Salesforce Agentforce as a consulting engagement. We identify which Pulsar tenant namespaces and topics carry Salesforce-relevant events, design the Pulsar consumer configuration that routes events to Agentforce with appropriate topic filtering and subscription type selection, configure the Salesforce actions triggered by each event type, and implement the Pulsar topic publishing for Salesforce commercial event coordination. The integration is designed around your Pulsar deployment — self-hosted or StreamNative Cloud — and your Salesforce commercial model.

How we structure an engagement

Related integrations

FAQ

Which Pulsar subscription type does the integration use — exclusive, shared, or key-shared?

The subscription type depends on the event volume and ordering requirements. For ordered processing of per-customer events — where a single customer's events must be processed in sequence — key-shared subscription preserves per-key ordering while allowing parallel processing across keys. For high-throughput unordered event processing, shared subscription distributes messages across multiple consumers. Emerge selects the subscription type for each topic based on the event semantics.

We use StreamNative Cloud (managed Pulsar) rather than self-hosted — does the integration work?

Yes. StreamNative Cloud is the managed Pulsar service and exposes the same API as self-hosted Pulsar. The integration is compatible with both StreamNative Cloud and self-hosted Pulsar deployments. The connection and authentication configuration differs; the consumer and producer logic is the same.

Does the integration support Pulsar Functions for event pre-processing before Salesforce?

Yes. Pulsar Functions can pre-process events — enriching, filtering, or transforming the message payload — before the output topic is consumed by the Agentforce integration. This is useful when the raw event payload requires transformation or enrichment from another system before it can be used to create a Salesforce record. Emerge can design the Pulsar Function layer as part of the integration.

How long does an Apache Pulsar + Agentforce integration take?

A focused engagement typically runs five to seven weeks: mapping the relevant Pulsar tenant namespaces and topics to Salesforce record types, designing the consumer configuration and subscription type for each topic, configuring the Salesforce action triggers, implementing Pulsar publishing for Salesforce commercial events, and testing delivery reliability and geo-replication scenarios.

Ground your agents in Apache Pulsar.

Tell us what your agents need to read and write in Apache Pulsar, and we'll design the integration and the governance around it.

Talk to the practice

Prefer email? Write to the practice instead.