How to Setup Response Saving Mechanism?
Overview
The Save Response Configuration feature enhances the Webhook module by allowing users to automatically capture values returned in webhook responses and store them into Meritto system fields. This configuration ensures that any data sent back by an external system—such as IDs, status values, or reference codes—can be saved instantly, enabling seamless two-way syncing.
This feature is introduced as a new accordion in Step 4 of the webhook setup flow and supports defining success conditions along with flexible key-to-field mapping. It helps teams automate data updates without additional manual actions or custom integrations.
Plan & Permissions
Though there is no explicit permission to use this feature, the following are the pre-requisite permissions for webhook creation and Edit.
- Ensure Webhook add-on is Subscribed for your institute.
- Required permissions:
- View Webhook: Post Application Manager > ERP Manager
- Create / Edit Webhooks: Post Application Manager > Configure ERP
- View push logs: API/Integration Logs
Note: The feature is available for all the Meritto webhook users but only handled for Dynamic Activity module currently, this will be handled in all other modules in the upcoming release.
Step By Step Guide
Step 1: Introduction of New Section – Save Response Configuration
A new section called Save Response Configuration has been added in Step 4 of the webhook setup.
The earlier “Request” and “Response” sections have been renamed for better clarity, and this new Section helps you decide which values from the webhook response should be captured and stored in Meritto.
Step 2: Save Key Response Value Configuration
This part allows you to map specific values coming from the webhook response directly into Meritto fields.
There are 2 Input Columns in this configuration.
Key
- This is the exact key from the webhook call response whose value you want to save.
- If the key is inside another key (Nested JSON) , you can mention it using dot notation (for example, Data.ID).
Field
- This is the field in Meritto where you want the selected key’s value to be saved.
- The dropdown will show only the fields that are relevant to the module selected in Step 1.
Step 3: Fields in which you can save the response value:
The fields available in the dropdown depend on which module you selected in Step 1:
Module Selected | Fields You Can Map To | Field Type |
Lead (Future Scope) | Custom Lead fields created by the user | Text only |
Application (Future Scope) | Text fields in the selected Application Form (Admin-created) | Text only |
Opportunity (Future Scope) | Custom fields created in the selected Opportunity List | Text only |
Dynamic Activity (Already Handled) | Custom fields created under Dynamic Activity | Text only |
This ensures that only relevant and permitted fields are shown for mapping.
Points to Keep in Mind:
To prevent mistakes, the system checks the configuration and ensures everything is valid before saving:
- A single response key cannot be assigned to more than one field.
- Once a field is selected for one entry , that field will not appear again in any other row’s dropdown.
- The system will not allow saving if any Key or Field is left empty.
- If the webhook saves values into Lead fields, the system follows the existing Leadupdate rules:
- Update Mode: The value is saved only the first time and will not be overwritten later.
- Override Mode : The value is updated every time the webhook returns a new value.
This ensures your existing Lead fields behaviour continues to work smoothly and consistently.
Conclusion
The Save Response Configuration feature strengthens Meritto’s Webhook module by enabling true bi-directional data integration. Institutions can now map response data to internal fields with complete control, validations, and observability. With consistent behavior across modules and seamless UI support, the feature ensures accuracy, automation, and alignment with operational workflows.