Connectors

Messaging & Event Streaming

Apache Pulsar

Event streaming: send, receive, and acknowledge messages on topics and subscriptions
Signs in with
Connection details
Runs on
Cloud or On-Prem Worker
Operations
10
Ready-made triggers
0

Connect Apache Pulsar

  1. In Neblex open Connect › Connections and click New Connection.
  2. Search for Apache Pulsar and give the connection a clear name.
  3. Fill in the fields. Secret values are encrypted and never shown again.
  4. Click Test, then Create Connection.
If the system is only reachable inside your network, choose an On-Prem Worker under Test from and run the flow on that Worker. See On-Prem Workers.
FieldWhat to enter
Service URLRequiredpulsar+ssl:// for an encrypted connection or pulsar:// without encryption. Several hosts may be listed, separated by commas.Example: pulsar+ssl://pulsar.example.com:6651
Sign-inRequired
TokenOptionalSecretThe JSON Web Token the cluster issued for this client.
Issuer URLOptionalThe OAuth 2.0 issuer; its token endpoint is found from the issuer's discovery document.Example: https://auth.example.com/
Client IDOptional
Client secretOptionalSecret
AudienceOptionalThe audience the cluster expects in its tokens, if it names one.
ScopeOptional
UsernameOptional
PasswordOptionalSecret
Check the certificate nameOptionalRequire each broker certificate to name the broker's host. Turn off only for clusters whose certificates do not; the certificate is still checked against the trusted authorities.
Server CA certificate (PEM)OptionalOptional private certificate authority that signed the broker certificates. Leave empty for publicly trusted certificates.
Client certificate (PEM)OptionalFor clusters that require client certificates; enter the private key below as well.
Client private key (PEM)OptionalSecret
Advertised listenerOptionalThe broker listener to use when the cluster advertises several, for example an external one.

Use it in a flow

  1. Open a flow, open the node library and search for Apache Pulsar.
  2. Drag it onto the canvas and choose an Operation and your connection.
  3. Map the operation's fields from earlier steps, or click Map with Matt.
  4. Use Test this step to see what it returns, then save.

To start a flow from Apache Pulsar without a ready-made trigger: a Poll for changes trigger can check one of its list operations on a schedule and pass on only what is new; if Apache Pulsar can send webhooks, a Webhook trigger receives them at its own URL.

Operations

10 operations in 4 groups. Each one is a step you can add to a flow.

Connection1
Test the connectionpingConnect to the cluster, sign in and return the broker's version and its maximum message size.
Messages4
Acknowledge messagesacknowledgeAcknowledge received messages on a subscription so they are not delivered again.
Deliver messages againnegativeAcknowledgeAsk the broker to deliver received messages again (a negative acknowledgement).
Receive messagesreceiveReceive up to the maximum number of messages from a subscription, from every partition.
Send a messagesendPublish one message per input record and wait for the broker's receipt.
Subscriptions2
Delete a subscriptionunsubscribeDelete a subscription and its position on every partition.
Move a subscriptionseekMove a subscription to a message, a publish time, or the oldest or newest message, on every partition.
Topics3
Get the last message IDgetLastMessageIdReturn the ID of the newest message of a topic, one record per partition.
Get topic partitionsgetPartitionedMetadataReturn how many partitions a topic has.
List topicslistTopicsList the topics of a namespace, filtered by the broker with a pattern and by name.