AMQP
AMQP Trigger – Start Workflows from AMQP Messages
Summary (SEO Meta Description):
The AMQP Trigger in WeHub starts workflows when messages are received from an AMQP broker.
Supports multiple variations: Standard, Transformation Field Format (TFS), and Process Raw Data.
Configure connection, subject, schema, and truncation options for flexible event-driven workflows.
Overview
The AMQP Trigger is part of the AMQP Integration and is available as a standalone Trigger plugin.
It allows workflows to start when messages are published to an AMQP broker.
WeHub provides three variations of the AMQP Trigger:
- AMQP Trigger → Standard message ingestion.
- AMQP Trigger (TFS – Transformation Field Format) → Messages are validated and transformed against a schema.
- AMQP Process Raw Data → Messages are ingested as raw payloads, optionally truncated or minimally validated.
1️⃣ AMQP Trigger (Standard)
The standard AMQP Trigger listens for messages and starts workflows with minimal configuration.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the trigger node. |
| Select Connection | Connection (AMQP) | Choose or create an AMQP connection. |
| Subject | String | The subject (or routing key) to listen for. |
| Header(s) | Key/Value (String) | Optional headers for filtering or enriching incoming messages. |
2️⃣ AMQP Trigger (TFS – Transformation Field Format)
The TFS variation applies a schema-based transformation to incoming AMQP messages.
It also supports field truncation for performance optimization.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the trigger node. |
| Select Connection | Connection (AMQP) | Choose or create an AMQP connection. |
| Subject | String | The subject (or routing key) to listen for. |
| Truncate Fields | Boolean (Toggle) | If enabled, long field values are truncated. |
| Truncate Level | Integer | (Visible only if Truncate Fields = true). Defines the maximum allowed field size. |
| Schema | Schema (Dropdown) | Select a schema to validate and transform incoming messages. |
| Header(s) | Key/Value (String) | Optional headers for filtering or enriching incoming messages. |
3️⃣ AMQP Process Raw Data
This variation delivers unmodified raw AMQP payloads, useful for debugging or custom workflows.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the trigger node. |
| Select Connection | Connection (AMQP) | Choose or create an AMQP connection. |
| Subject | String | The subject (or routing key) to listen for raw messages. |
| Truncate Fields | Boolean (Toggle) | If enabled, long field values are truncated. |
| Truncate Level | Integer | (Visible only if Truncate Fields = true). Defines the maximum allowed field size. |
| Schema | Schema (Dropdown) | Optional schema for basic validation (payload remains raw). |
| Header(s) | Key/Value (String) | Optional headers for capturing additional metadata. |
💡 Example Use Cases
- AMQP Trigger (Standard) → Start workflows for task queues, job scheduling, or message-driven events.
- AMQP Trigger (TFS) → Normalize HL7, JSON, or XML data against a schema before processing.
- AMQP Process Raw Data → Debugging raw payloads or high-performance workflows that skip transformation.
FAQ
Q: What’s the difference between AMQP Trigger and AMQP Client?
A:
- AMQP Trigger (this page) → Listens for incoming messages and starts workflows.
- AMQP Client (Processor) → Sends/publishes messages to AMQP brokers.
Q: When should I use TFS instead of Raw Data?
A:
- TFS → Use when you need schema validation and transformation.
- Raw Data → Use when you need exact unmodified payloads or lightweight processing.
Q: What happens if I enable Truncate Fields?
A: You can define a Truncate Level (integer). Field values longer than this limit are truncated, improving performance in workflows with large payloads.
Keywords: WeHub AMQP Trigger, AMQP Trigger TFS, AMQP Process Raw Data, AMQP Workflow Automation, AMQP Messaging Trigger