Save Response Configuration | Product Guide

Save Response Configuration | Product Guide

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.
TThis feature is introduced as a new section in Step 4 of the webhook setup flow and supports 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. 
  1. Ensure Webhook add-on is Subscribed for your institute.
  2. Required permissions:
    1. View Webhook: Post Application Manager > ERP Manager
    2. Create / Edit Webhooks: Post Application Manager > Configure ERP
    3. View push logs: API/Integration Logs
Notes
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.

Core Functionalities

Introduction of New Accordion – 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 accordion helps you decide which values from the webhook response should be captured and stored in Meritto.

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
  1. This is the exact key from the webhook call  response whose value you want to save.
  2. If the key is inside another key, you can mention it using dot notation (for example, Data.ID).
Field
  1. This is the field in Meritto where you want the selected key’s value to be saved.
  2. The dropdown will show only the fields that are relevant to the module selected in Step 1.

Validations

To prevent mistakes, the system checks the configuration and ensures everything is valid before saving:

Duplicate Key Mapping
  1. A single response key cannot be assigned to more than one field.
Field Selection Restrictions
  1. Once a field is selected for one row, that field will not appear again in any other row’s dropdown.
Blank Entry Prevention
  1. The system will not allow saving if any Key or Field is left empty.
Server-Side Validations
  1. Even if something bypasses the on-screen checks, the server verifies the configuration again before saving.

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.

Timeline Logging

Whenever a field is updated through this configuration, Meritto records it in the timeline with the message:
“{Field name} updated via Webhook Save Response Configuration for Webhook: {Webhook Name} and Vendor Name: {Vendor Name}”
This provides complete visibility into when and how system fields were updated.

Support for Lead Field Update Modes

If the webhook saves values into Leadfields, the system follows the existing Leadupdate rules:
Update Mode
  1. The value is saved only the first time and will not be overwritten later.
Override Mode
  1. The value is updated every time the webhook returns a new value.
This ensures your existing Lead behaviours continue to work smoothly and consistently.

Benefits of the Functionalities

1. Automated Data Sync
Removes the need for manual entry to push values from response payloads into Meritto.

2. Clean, Controlled, and Secure Updates
Field restrictions ensure only meaningful and permitted fields are updated.

3. Better Operational Tracking
Timeline activities provide transparency into what was updated, when, and by which webhook.

4. Reduced Integration Effort
External systems can simply return the updated values without building reverse APIs; Meritto will save them directly.

5. Reliable and Error-Free Data Flow
Validations prevent accidental overwrites, duplication, or misconfiguration.

6. Works Across All Core Modules
Lead, Application, Opportunity, and Dynamic Activity data flows can benefit uniformly.

Special Business Use Cases

The Save Response Configuration becomes especially valuable when institutions work with external platforms and need to capture system-generated IDs, URLs, and status values for further processing within Meritto.

Assessment & Exam Platforms (Slot Details, Admit Card IDs, Test URLs)

Many assessment vendors return unique identifiers after a slot is booked or an admit card is generated. Institutions can automatically save these identifiers inside Meritto.
  1. Exam Slot / Admit Card ID: When an assessment partner sends back a slot confirmation ID or admit card ID, it can be stored in Meritto for reference, validation, and downstream workflows.
  2. Vendor Test-Taking URL: If the assessment platform returns a test URL (for online exams), Meritto can save it instantly and use it for communications—email, SMS, WhatsApp, candidate portal display, or counselor follow-ups.

Ticketing Systems 

When Meritto triggers a ticket creation via webhook/API, ticketing platforms usually respond with a unique ticket ID.
  1. The returned Ticket ID can be saved against the Lead, Application, or Opportunity record.
  2. This stored ID enables subsequent automated actions—for example:
    1. Updating the ticket status
    2. Adding replies or notes
    3. Triggering category-wise escalations
    4. Closing the ticket via an automation, if needed
This ensures the ticket lifecycle is seamlessly mapped within Meritto without manual lookup.

LMS Platforms (Post-Enrollment Integrations)

Institutions often push candidate data to a Learning Management System after successful enrollment or admission.
  1. LMS platforms typically generate a student profile ID or LMS Enrollment ID.
  2. Saving this ID in Meritto allows academic teams to:
    1. Trigger post-enrollment communication (orientation, onboarding, course access details)
    2. Track LMS-specific milestones within Meritto workflows
It eliminates any manual dependency in mapping Meritto records with LMS records.

Vendor-Specific Verification or Status Codes

External verification vendors often return unique status codes—for example:
  1. Identity verification status
  2. Document verification code
  3. Background check reference number
  4. These codes can be automatically stored and used to:
    1. Trigger follow-up processes
    2. Drive conditional workflows
    3. Power dashboards and reports related to vendor success rates or compliance

ERP Integrations (LPU Case or Similar – Enrollment Completion Flows)

In ERP integrations, once a candidate is officially enrolled, the ERP often returns a system-generated identifier.
  1. Examples include Registration Number, Roll Number, Admission ID, or Student Master ID.
  2. Saving this ERP-issued identifier back into Meritto enables seamless coordination between admissions teams, finance teams, academics, and downstream systems.
  3. This also allows Meritto to act as a single source of truth for any future communication (fee reminders, reporting, onboarding workflows).

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.

    • Related Articles

    • Referral Connect Product Guide

      Overview In many academic institutions and professional programs, recommendations from credible sources such as academic professors or former employers play a key role in evaluating an applicant’s eligibility for a particular course. Traditionally, ...

    • Webhook Data Push Troubleshooting Guide

      Overview If your webhook is not pushing data as expected, certain JSON keys are returning blank values, or the data push is delayed, follow this step-by-step troubleshooting guide to identify and resolve the most common issues. This guide helps you ...

    • Publisher Panel Overview: A Comprehensive Guide for Publishers

      Overview Imagine you're running a publishing agency, a third-party lead generation partner for educational institutes. Now, wouldn’t you want to know if the leads you're sending are actually converting? Well, welcome to the Publisher Panel by ...

    • All about Product Sales Performance Dashlet

      Overview The Product Sales Performance Dashlet provides insights into the total number of products sold, categorized into Single and Bundled sales. It helps you analyze the volume and type of product sales, enabling data-driven decisions to optimize ...

    • Configuring the Student Admission Portal (Applicant Flow Configuration)

      Overview The Student Admission Portal serves as a centralized platform that applicants can access upon registering or logging in via the registration page. It is designed to streamline the entire admission process by offering a user-friendly ...