Skip to main content
michael_sweeney
michael_sweeney
Helper ⭐️
April 25, 2017
New Idea

Create email assist tokens from opportunity fields

  • April 25, 2017
  • 15 replies
  • 198 views
Right now we support only 6 objects for token mappings, Account, Contact, CustomerInfo, CSTask, CTA and User. Are there plans in the future to be able to add custom tokens from the opportunity field for example?

If I link the oppty to the CTA or figure out how to write these fields onto the CTA, could that allow me to pull these fields into the template? 

    15 replies

    Show previous replies
    Gainsight Employee ⭐️
    hitesh_sharma
    Gainsight Employee ⭐️
    March 14, 2018
    Hi Seth,

    Yes, you could load the required data in the Custom Fields in CTA or Account and use that for mapping.

    Improving on giving more options to map tokens at playbook level is already in roadmap, just that there are other things thats keeping the team busy. 

    Regards,
    Hitesh
    pele
    pele
    Helper ⭐️⭐️⭐️
    May 31, 2018
    Was just thinking similarly today. It would be great if you could update email tokens from rules engine– just as you would use tokens in comments. That would kinda solve for a lot of the use cases here. 
    anthonysabato
    anthonysabato
    Helper ⭐️
    April 3, 2019
    I found myself in this scenario where I need a simple variable or a field to use in tokens for email assist but can't do it since only those select objects are available. I would love to take a URL for example and append a number to each for uniqueness.

    Anyone have an update if/when this will be available?

      cmultanen
      cmultanen
      Helper ⭐️
      June 18, 2019
      +1, would love more flexibility in what objects we can use for email tokens. We can do so much with Programs but are very limited with CTAs and email assist.

      billrlarseniii
      Contributor ⭐️⭐️⭐️
      April 14, 2023

      I agree, I think it would be great if we could tokenize from any object.  This community post also makes me think of the same need: 

       

      We have a slightly different use case where our CSMs create an “Implementation Request” CTA with a linked object for our implementation log. They create a record with all the relevant details of the upcoming implementation, but that info can’t be tokenized back into the request email sent to our Implementation Managers.  It would be great if you could tokenize fields for any linked objects on the CTA.

      Terms & ConditionsAccessibility statement