Hi there @Colm,
I have moved your reply to a new topic. I hope you don’t mind!
Whenever you see those {{...}} curly braces around entries in the Data In of an action, this means that there is a field mapped there in the Zap Editor, but when the Zap ran live this data was not sent from a previous step.
Since the sample data is different from the Zap run’s data. I would recommend utilizing the custom pill mapping workaround. You can learn more about the workaround here:
Kindly give it a try and let me know how it goes? I'll keep an eye out for your response!
Thanks for the response Ken - I’ve just gone the custom pill mapping doc and I’ve implemented as instructed.
Would you mind taking a quick look at this video?
Can you let me know if you think I’ve gone wrong anywhere? Any thoughts or comments are very welcome!
Thanks!
Colm
Hi @Colm,
Thanks for the detailed loom video!
It looks like your custom pills are set up correctly. However, you'll need to republish the Zap to save the changes that were made. After publishing the Zap, please try triggering it again and check the Zap History to ensure that the data is being sent correctly.
I'll be keeping an eye out for your response!
Thanks Ken - I’ve saved the changes - and the zap is on - I don’t seem to have the option to republish.
Would you mind taking another quick look at this video?
https://www.loom.com/share/0a7f26dfb95a43c3af7d60db1197bb0d