Hi @georgedude ,
That’s an interesting idea.
There is a hidden debug tool that does make it easier to access and use token data in certain actions. When you’re selecting tokens to include in an action, right-click the token group heading (see https://cln.sh/l7rbFNBc), and you’ll see an option to add all tokens in the group to the action. You can even add labels and token ideas. This adds everything possible in one step.
It doesn’t create a default mapping, but maybe it would help you more quickly organize tokens and make sure you don’t miss anything. For something like an email this is useful, but if you’re using something like an action to send data via webhook, where you have to add each field manually, this will be less useful.
Maybe that helps a bit though? If you do have a specific action in mind, let us know what you’re using.
Hi @uncannyautomator,
the debug tool does allow to speed up the process somewhat as I can cut/paste from the dump. The challenge is that it’s a single dump, I want the same but create all tokens as separate items.
What I was thinking about would have two slightly different implementations:
- Create tokens for all fields available and walk hierarchy as needed. For example, we are trying to automate LearnDash quiz completion for all quizzes under the same course. What I would like to get is the full data set containing quiz/lesson/course. Knowing just the quiz is not enough without doing some extra work to find out the lesson and course. If you dump everything available under LD schema, that’d be a good start (expanding objects like lesson/course instead of their ids would be a bonus, of course).
- Have an option to “include everything”. A good example is WPForms where we’re trying to accept submissions “as is” and deal with them later. When a field is added/removed, we have to deal with it in three places: form itself, receiving automation endpoint and Automator. By adding “include everything” option, you remove Automator from the dependencies.As marketing people keep fiddling with the forms all the time, submitting all key/value pairs available makes a lot of sense.
Hope it helps,
George
Hi @georgedude ,
Thanks for the feedback!
#1 is a good idea and we can consider something like that for the future. It does get more complex with LearnDash Shared Course Steps, as handling a variety of mappings would be complex. Still, we can probably do more here.
For now we will generally have to consider these as feature requests, as they’re big changes, not just to token availability (and keeping things manageable for most users), but to the UI and other elements as well.
I will tentatively mark this as closed, since we have captured the requests, but I’m afraid we aren’t able to offer a simplified or more complete solution right now.
