Skip to main content

​
Thnks Data Model

​
Thnks Object

Thnks Salesforce Object

​
Thnks Record Creation

The following events trigger a change on the Salesforce side (either creating or updating records):
  • A new Thnks is sent, whether from the ‘Send a Thnks’ iframe button, the Thnks Request/Approval Process workflow, or the Send Thnks Apex Action in Flows (new in v1.9)
  • The status of an existing Thnks is changed (e.g. opened, undelivered, redeemed, etc.)
Send Thnks Apex Action (new in v1.9): The Apex action sends directly to the Thnks platform via API, bypassing the Thnks Request object and Approval Process entirely, no Thnks Request record is created. The resulting Thnks record in Salesforce is still created through the same organic sync used for web, mobile, and extension activity (see Tracking Thnks Activity below), and goes through the same Contact/Lead/Opportunity matching logic described on this page. This happens asynchronously, the record is not created at the same moment the Flow runs. Separately, the Apex action creates or updates a Task, for its own follow-up (on failure) and completion (on success, via the Source Record Id input), independent of the organic Thnks record’s own Task Syncing behavior.
Upon creation, this is the general flow of what is occurring (note that a Task being created is possible at the very end, but this is not being shown in this diagram):
Thnks Creation Flowchart
So as you can see, when a Thnks record is being created, Salesforce is checking the following:
  • Is there a Contact to match?
  • If no Contact is found, is there a Lead to match?
  • If a Contact is found, is there an open Opportunity to match?

​
Thnks Record Updates

After the initial Thnks is sent and the subsequent Thnks record in Salesforce is created (and potentially a Task), there will be no additional new records being created. Instead, all that will be changing is the Status field (API name of thnksdev1__RecipientTransactionStatus__c) on the Thnks record whenever the status on the Thnks side is updated

​
Task Logging for Thnks

If you have enabled “Task Syncing” in the Configuration tab, then every time a Thnks is sent, a Task will be automatically generated. There are two standard fields on Tasks for association with other records: Name and Related To (API Names of WhoId and WhatId, respectively). The WhoId (Name) field can only be related to Leads or Contacts. The WhatId (Related To) can be related to any other object. For our purposes, the WhatId will always be related to the Thnks record.
  • If the Thnks is associated with a Lead, then the Task will only be associated with the Thnks record via the Related To field (WhatId). The WhoId cannot be used in this scenario due to Salesforce limitations.
Thnks Creation Flowchart

Task for a Thnks Record Associated with a Lead

  • If the Thnks is associated with a Contact, then the Task will be associated with the Thnks record via the Related To field (WhatId), as well as the Contact via the Name (WhoId) field.
Thnks Creation Flowchart

Task for a Thnks Record Associated with a Contact

  • If the Thnks is not associated with a Lead nor a Contact, then the Task will only be associated with the Thnks record via the Related To field (WhatId).
Task Syncing vs. Apex Action follow up Tasks (new in v1.9): The Task Syncing setting above governs Tasks created automatically whenever any Thnks is sent, and is unrelated to the Send Thnks Apex action’s own Task behavior. The Apex action instead marks a Flow supplied Source Record Id (often a Task) as complete on success, or creates a separate follow up Task on failure, independent of whether Task Syncing is enabled. See the Install Guide for details on configuring the Apex action.