Connectors
Messaging & Event Streaming
AMQP 1.0
Enterprise messaging: send and receive from queues and topics over AMQP 1.0
AMQP 1.0 specificationAPI checked August 18, 2026
- Signs in with
- Connection details
- Runs on
- Cloud or On-Prem Worker
- Operations
- 3
- Ready-made triggers
- 0
Connect AMQP 1.0
- In Neblex open Connect › Connections and click New Connection.
- Search for AMQP 1.0 and give the connection a clear name.
- Fill in the fields. Secret values are encrypted and never shown again.
- 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.
| Field | What to enter |
|---|---|
| Connection setupRequired | |
| HostRequired | |
| PortOptional | Example: 5671 |
| UsernameOptional | Supply together with Password to select SASL PLAIN; omit both to use no SASL layer. |
| PasswordOptionalSecret | Sealed SASL PLAIN password; Username and Password are all-or-nothing. |
| Use TLSOptional | Turning this off sends traffic and credentials without transport encryption. Use plaintext only for a customer-controlled endpoint that explicitly requires it. |
| Connection stringRequiredSecret | Paste an amqp:// or amqps:// connection string without a path or query options. |
Use it in a flow
- Open a flow, open the node library and search for AMQP 1.0.
- Drag it onto the canvas and choose an Operation and your connection.
- Map the operation's fields from earlier steps, or click Map with Matt.
- Use Test this step to see what it returns, then save.
To start a flow from AMQP 1.0 without a ready-made trigger: a Live stream trigger with AMQP 1.0 as the stream source starts a run for each message as it arrives (see Streaming triggers).
Operations
3 operations in 2 groups. Each one is a step you can add to a flow.
Connection1
Test connectionping | Open an AMQP 1.0 connection and session, proving transport and authentication. |
Messages2
Receive messagesreceive | Receive a bounded delivery page, project every AMQP message section, then apply one explicit terminal outcome per delivery. | |
Send a messagesend | Send one complete AMQP 1.0 message and succeed only after an accepted terminal outcome. |