Queue, issue and remote access integrations

RabbitMQ

RabbitMQ uses AMQP queues and exchanges. Required data: AMQP or AMQPS URL and queue name. Exchange, routing key and prefetch are optional. Use RabbitMQ when the workflow should publish to or consume from a broker queue. Queue Trigger appears for RabbitMQ inbound messages. Queue Action supports publish, read messages and acknowledge message operations. RabbitMQ concepts are covered in the RabbitMQ tutorials.

ActiveMQ

ActiveMQ uses STOMP in this connector. Required data: broker URL and either a queue or a topic. Username and password must be provided together when the broker requires authentication. Use ActiveMQ when the existing system already publishes STOMP queue or topic traffic. Queue Trigger and Queue Action are visible for ActiveMQ in the same places as RabbitMQ.

AWS SQS

AWS SQS uses AWS queue URLs. Required data: region, queue URL, access key ID and secret access key. Endpoint is optional for local or compatible test environments. Queue Trigger can poll SQS messages with limits such as max messages per tick and visibility timeout. Queue Action can publish, read and acknowledge/delete messages. Use Amazon SQS getting started when creating the queue and credentials.

AWS SNS

AWS SNS publishes notifications to a topic. Required data: region, topic ARN, access key ID, secret access key and webhook secret. Endpoint is optional for local or compatible environments. Queue Action can publish to SNS. Queue Trigger is visible when SNS webhook delivery is configured for inbound notifications.

Jira

Jira integrations require base URL, account email and API token. Default project key and webhook secret are optional. Issue Trigger appears for Jira issue events and can filter by event type, labels, author or text. Issue Action can create, update, comment, read, list, close or reopen issues.

GitHub Issues

GitHub Issues requires token, owner and repository. Webhook secret is optional but recommended for inbound events. Use the GitHub Issues REST API docs to match token permissions to the operations needed by the workflow. Issue Trigger and Issue Action are visible for GitHub Issues with the same event filters and actions as Jira.

GitLab Issues

GitLab Issues requires token and project ID. For self-managed GitLab, enable custom server and provide the base URL. Webhook secret is optional but recommended. Issue Trigger and Issue Action are visible for GitLab Issues with the same issue event filters and issue actions as Jira and GitHub.

SSH

SSH integrations allow controlled remote commands. Required data depends on the connector mode, but production use should include strict host identity, private key or controlled credentials, and an allowed-command list. SSH Action is visible when an SSH integration is in scope for the project. It should be used for narrow operations such as restarting a service, checking a deployment or running a prepared script.