The HappyFox connector correctly normalizes the updates array from the HappyFox Tickets API into the TICKET_UPDATE table. However, the most critical part of each update—the message object (the actual text/body of the update)—is not synced to the destination.

Because this field is missing, it is not possible to reconstruct a full ticket thread. Only the very first message on a ticket is available, which prevents any analysis or retrieval of subsequent ticket replies or internal notes.

Request:

Please add support for syncing the full message object for each update returned by the HappyFox Tickets API. This could be added to TICKET_UPDATE or another appropriate table as long as every update’s message text becomes queryable.

Business Impact:

Missing update messages prevents essential use cases, including:

• Reconstructing full customer–agent conversation threads

• Running NLP, sentiment, or topic analysis across all updates

• Performing ticket quality reviews and compliance audits

• Differentiating meaningful agent/customer interactions from system events

The inability to access the majority of ticket messages severely limits downstream analytics and operational visibility.

Expected Outcome:

Fivetran should sync the message content for every ticket update so that all messages in a HappyFox ticket thread are available in the destination.