AMQP (RabbitMQ) Source

Install

See the Install guide for the full setup, including Windows PowerShell.

curl -fsSL https://install.skippr.io/install.sh | shClick to copy

Consumes messages from an AMQP queue.

Configuration

source:
  kind: amqp
  connection_string: ${AMQP_CONNECTION_STRING}
  queue: events

Field	Default	Description
connection_string	(required)	AMQP connection URI
queue	(required)	Queue name
exchange		Exchange to bind to
routing_key		Routing key for binding
prefetch_count	10	Prefetch count
mode	stream	stream or batch

Namespace: amqp.{queue}

CLI

skippr connect source amqp \
  --connection-string 'amqp://guest:guest@localhost:5672' \
  --queue my-queue \
  --exchange events \
  --routing-key output \
  --prefetch-count 10 \
  --mode stream

Flag	Description
--connection-string	AMQP connection URI
--queue	Queue name
--exchange	Exchange to bind to
--routing-key	Routing key for the binding
--prefetch-count	Number of unacknowledged messages to prefetch
--mode	Consumption mode

Authentication

Authentication is provided through the AMQP connection URI. For security best practices, we strongly advise against storing the connection string in skippr.yaml. Use environment variable interpolation instead: replace the connection_string value with your own ${ENV_VAR} reference.

The relevant part of skippr.yaml looks like this:

source:
  kind: amqp
  connection_string: ${AMQP_CONNECTION_STRING}

Set the env var before running skippr:

macOS / Linux

export AMQP_CONNECTION_STRING="amqp://guest:guest@localhost:5672"

Windows PowerShell

$env:AMQP_CONNECTION_STRING = "amqp://guest:guest@localhost:5672"

Windows Command Prompt

set AMQP_CONNECTION_STRING=amqp://guest:guest@localhost:5672

Permissions or Network Requirements

The AMQP user must be allowed to connect to the broker and consume from the selected queue. If you use exchange and routing_key, make sure the broker binding already exists or is created by your messaging workflow.

Troubleshooting

Symptom	Fix
authentication or connection failures	Verify the AMQP URI, broker hostname, port, and vhost permissions.
no messages arrive	Check the queue name, exchange and routing key, and whether publishers are sending to the expected path.

Next steps

• Pair this source with a destination from Destination Connectors.
• See How It Works for the end-to-end pipeline flow.

Install

See the Install guide for the full setup, including Windows PowerShell.

curl -fsSL https://install.skippr.io/install.sh | shClick to copy