Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

RabbitMQ

RabbitMQ integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.1.6
Published scopes0 published scopes
Last updatedSeptember 30, 2026

Overview

Connect RabbitMQ with Flows360

RabbitMQ integration for Flows360 workflows.

Use the RabbitMQ connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 2 actions and 1 trigger.

Available actions

  • sendMessageToExchange
  • sendMessageToQueue

Available triggers

  • Message Received

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: RabbitMQ
  • Package: @activepieces/piece-rabbitmq@0.1.6
  • Exact artifact digest: sha256:413d8ddff7e71a19b6174d4ea2090ef7f6a4cd903d04e9a24a928406274b3e01
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • sendMessageToExchange (sendMessageToExchange), Send a message on a RabbitMQ exchange Classification: read.
  • sendMessageToQueue (sendMessageToQueue), Send a message on a RabbitMQ queue Classification: read.

Trigger contracts

  • Message Received, polling.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects3
Supported actions2
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Host Required
  • Username Required
  • Password Required · protected credential
  • Port Required
  • Virtual Host Optional

Supported objects

ObjectReadWriteNotes
sendMessageToExchange Yes No Send a message on a RabbitMQ exchange
sendMessageToQueue Yes No Send a message on a RabbitMQ queue
Message Received Yes No polling trigger declared by the pinned package.

Supported actions

sendMessageToExchange · Read

Send a message on a RabbitMQ exchange

send_message_to_exchange · Risk: low · Retry: safe

Inputs

  • exchange · string · Required, The name of the exchange to send the message to
  • routingKey · string · Optional, The routing key to use when sending the message
  • data · object · Required, The data to send
sendMessageToQueue · Read

Send a message on a RabbitMQ queue

send_message_to_queue · Risk: low · Retry: safe

Inputs

  • queue · string · Required, The name of the exchange to send the message to
  • data · object · Required, The data to send

Triggers

Message Received · Poll

Triggers when a message is received on a RabbitMQ queue

Inputs

  • queue · string
  • maxMessagesPerPoll · number

Setup

Setup

  1. Add the RabbitMQ connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Host (host), required.
  • Username (username), required.
  • Password (password), required; stored as a sensitive connection value.
  • Port (port), required.
  • Virtual Host (vhost), optional.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-rabbitmq@0.1.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 2 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required RabbitMQ connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-rabbitmq@0.1.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com