# Messaging Bridge

Imagine that you have multiple messaging systems used in your organization. How can multiple messaging systems be connected so that messages available on one are also available on the others?

A **Messaging Bridge**, is a connection between messaging systems, to replicate messages between systems.

It is very easy to implement this pattern with Ylem. You just need to create a pipeline that begins with the "**External\_trigger**" task accepts the input message from one system and then uses the "**API\_call**" to publish the input message to the API of another system.

<figure><img src="/files/jNpRw7OAoOQGVvsZiEbK" alt=""><figcaption></figcaption></figure>

It is a very simple pipeline that just forwards the message to the second messaging system. But of course, your real use case might be as complicated as you want, containing [conditions](/pipelines/tasks-ip/condition.md), [filters](/pipelines/tasks-ip/filter.md), [processors](/pipelines/tasks-ip/processor.md), [transformations](/pipelines/tasks-ip/transformers.md), and other tasks that prepare the input data to be accepted by the second messaging system.

<figure><img src="/files/2rYzvTD7kzHe9D2AZpk2" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ylem.co/use-cases/messaging-patterns/messaging-bridge.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.