--- title: "FoundationNg Form Config (Mulesoft & MTCaptcha)" description: "In FoundationNg Form Config Mulesoft and MT Captcha can be configured. They are both needed for Forms." path: https://www.eonshowroom.eon.com/en/aem-basics/configuration-pages/foundationng-new-form-config.html lastModified: 2026-06-22T09:48:47.964Z --- # FoundationNg Form Config (Mulesoft & MTCaptcha) ![](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/EON_Pattern_7_4-4%3A2-1?fmt=webp-alpha) # FoundationNg Form Config #### New API for Form Data Handling Both the old and new solutions will work in parallel during the transition. However, the old solution will be shut down at the end of May 2025. ## Form Migration Guide ##### Introduction ###### Starting in Q2/2025, we will replace our current Mail interface. If you have web forms built with our Foundation component set using the **ActionType "An HTML Email"**, you’ll need to make a small update in your Context-Aware Config (CAConfig) to continue using them. ###### Good to know: Both the old and new solutions will work in parallel during the transition. However, the old solution will be shut down at the end of May 2025. ### Where to Update Your Configuration? Each solution typically has one configuration for mail sending. You’ll find it in your topmost Configuration page: - Look for the config named "FoundationNG Form Config (Homer & Captcha)", previously called “FoundationNG Form Config (Mulesoft & MtCaptcha)”. - Click it to open the dialog where the necessary changes must be made. ![](https://www.eonshowroom.eon.com/cdm-assets/is/image/eon/foundationNG_form_config_cac?fmt=webp-alpha) #### Overview: Migrating from Mulesoft to Azure To support the transition to our new mail interface, we are shifting from using **Mulesoft** (now deprecated) to a new **Azure-based solution** for form data handling. If your web forms are currently configured to use Mulesoft, you will need to update your configuration accordingly. The table below outlines the required changes in your **FoundationNG Form Config**. Updating these values ensures that your forms will continue to function correctly with the new infrastructure. Please review and apply the necessary changes as outlined to complete the migration to the Azure solution. | Property | Azure | Mulesoft (deprecated) | | --- | --- | --- | | Enable MuleSoft Email | ✔️ | ✔️ | | Enable Non-Production Email | Checked only in lower environments to prevent test emails from reaching production processes. | see Azure | | MTCaptcha API URL | Deprecated | https://api.eon.com/edt/aem/aem-api/v1/captcha/validate | | Mulesoft Api | https://homerprodapimgmt.azure-api.net/api/v1/inbound (**Prod and Stage**) https://homer-inbound.azurewebsites.net/api/v1/inbound (use only for **Dev**) | https://api.eon.com/edt/aem/aem-api/v1/forms/email | | Selector Value | Deprecated | sol-eon-*projectname* | | SiteKey | **Custom Key for Each Website** – If empty, the user must request a key from us; we will provide one. | see Azure | | Captcha Key | **Custom Key for Each Website** – If empty, the user must request a key from us; we will provide one. | see Azure | | Mail Relay Key Set | mailjet1, mailjet2, mailjet3, mailjet4 (see confluence page or Jira ticket for correct assignment) | not applicable | #### Final Check: Test Your Configuration A wrong setup can break your forms—always test after making changes. **Here’s how:** 1. Publish your configuration. 2. Submit a form with Captcha and check if the email arrives in your inbox. 3. If it fails or shows an error, roll back your changes and contact us. ## For reporting form bugs, please use the following link: [Create Bug Ticket for Forms Backend Issue](https://jira.eon.com/secure/CreateIssueDetails!init.jspa?pid=12522&issuetype=1&summary=Forms+Backend+Issue+for+%3CYOUR+SOLUTION-NAME%3E&components=17031&components=72534&customfield_11143=13811&customfield_11146=45650&labels=FNG_Bug&priority=3) This only concerns general issues with backend availability and email routing. #### Mail Relay Key Set This field tells the backend which Mailjet account to use for sending emails. We currently operate with four Mailjet accounts: **mailjet1**, **mailjet2**, **mailjet3**, and **mailjet4**. To ensure your forms send correctly, you need to assign the appropriate account identifier based on your site’s domain. The correct assignment for each domain can be found in our **Confluence documentation**. Please refer to that list and use the matching identifier in your configuration. [Find your Mail Relay Key in Confluence](https://confluence.eon.com/spaces/ddsmbfoun/pages/792343796/Form+Middleware+Replacement+Rollout) [Find your Mail Relay Key in Jira](https://jira.eon.com/browse/DDS_SUPPORT-40011) #### Captcha and Sitekey Contact ## Urs Kramer Contact for Mulesoft & MTCaptcha Integration [urs.kramer@eon.com](mailto:urs.kramer@eon.com) ### Step-by-Step Guide: Updating Your Form Configuration #### Mulesoft API Endpoint In the **"Mulesoft API"** section, replace the old API endpoint (likely something with api.eon.com) with the new one. We offer two endpoints: one for **development** and one for **production**. Unless you have a specific reason to use the development version, use the production endpoint: https://homer-api.eon.com/api/v1/inbound **Note: Different APIs to be used for Stage/Prod and for your Dev environment** ** #### Captcha Key The **Captcha Key** field stores the encrypted value used to validate captchas. This key is specific to your solution and typically already filled in. Since it’s encrypted, it won’t be readable in plain text. If the field is empty or missing, please contact us—we’ll provide the correct value. Also, remember: if your **siteKey** changes at any point, the Captcha Key will need to be updated as well. **Note: Different keys to be used for Stage/Prod and for your Dev environment** ** #### Mail Relay Key Set The **Mail Relay Key Set** tells our backend which Mailjet account to use for sending emails. We currently operate four Mailjet accounts identified as: - mailjet1, mailjet2, mailjet3, mailjet4 ###### To find the correct value for your project, please check our confluence page: [Find your Mail Relay Key in Confluence](https://confluence.eon.com/spaces/ddsmbfoun/pages/792343796/Form+Middleware+Replacement+Rollout) [Find your Mail Relay Key in Jira](https://jira.eon.com/browse/DDS_SUPPORT-40011) #### Obsolete Fields The fields **“MTCaptcha API URL”** and **“selector value”** are still visible in the form configuration, but they are now obsolete. These fields may be removed in a future version of FoundationNG, so for now, you can ignore them. ## #### Final Check: Test Your Configuration A wrong setup can break your forms—always test after making changes. **Here’s how:** 1. Publish your configuration. 2. Submit a form with Captcha and check if the email arrives in your inbox. 3. If it fails or shows an error, roll back your changes and contact us.