--- title: Enterprise Integration Patterns (EIPs) description: See the available EIPs in Integrations documentId: ipaas-eips locale: en-US --- Enterprise Integration Patterns (EIPs) are reusable solutions for common integration challenges between systems. They enable you to create message processing flows in a clear, efficient, and scalable way. Here are two practical examples of using EIPs: - **Choice**: suppose you need to send messages to different systems depending on the content type. With the Choice EIP, you can create logic similar to _if-else_: - If type = "payment", send to the financial system. - If type = "registration", send to the CRM system. - **Set Header**: to add or modify information in the message header, such as setting the content type: - Set the "Content-Type" header to "application/json". These examples show how EIPs can be used to create flexible and robust integrations, adapting to different business scenarios. You can combine several patterns to build complete routes, automate processes, and ensure integration quality. ## Most Used EIPs Click a card to access the documentation for each EIP. Routes messages based on conditions, similar to an _if-else_ structure. Attempts to execute a block of code, handling exceptions if they occur. Logs messages for monitoring and debugging. Converts a message to a specific data format. Sends a message to multiple destinations. Adds custom logic within an integration flow, such as attaching or removing files when sending emails or uploading files to a URL using _multipart/form-data_. Sets or modifies the message body. Sets or modifies a message header. Sets or modifies multiple message headers at once. Sets or modifies a message property. Splits a message into multiple smaller messages. Interrupts the route flow and throws a specific exception. Converts a message from a specific data format.