Writing JotX Comment Data into a Separate Database Table

This donor topic asked how to intercept name and email values from JotX comments and write them into a separate database table. That remains a useful pattern whenever comment or feedback data needs to feed another workflow.

Why Store Comment Data Separately

• Lead capture and follow-up become easier.
• Mailing and export workflows no longer depend on comment markup.
• Structured reporting becomes possible.

Implementation Direction

• Hook into the stage where JotX has validated and accepted the comment payload.
• Store only the fields the business actually needs, such as name and email.
• Keep the additional table independent from front-end templates.

The principle is the same as with eForm lead storage: once the data matters to operations, it should live in a structured table rather than only inside rendered comment content.