I’ve looked at the webhook and can’t figure out why the “type” is important for a transfer.
I use the hint value, for example, for a price. Wouldn’t it make sense to pass all fields that could have a variable value to the webhook?
The field type is included mainly for convenience. For example, if you have two fields with the same label, the type helps tell them apart more easily.
Regarding your point — all fields with variable values are indeed passed to the webhook:
The only thing I’m not quite sure about is the part with the hint. Since it’s a static value that can’t be changed by users, so I didn’t quite get how it’s related to your suggestion. Could you clarify a bit more what you had in mind?
You’re right, of course. The Hint field value cannot be changed by the user. I think I’ve mixed something up. Sorry. Then I have to display the price on the recipient side—as in my case. To ensure the correct value and price match on the recipient side, I have to assign the ID to both. Right? So even if the name changes, the ID always stays the same?
However, that’s confusing me with the email message. I’ve set it up in a table for each individual value, and there are a large number of different values.
I’ll see what I can do with the webhook. It’s new territory for me, too.